Uptime Monitoring

We monitor the uptime of all WordPress sites on our platform, checking your site every 3 minutes. If our monitoring detects that a site isn’t loading, our engineers respond quickly to get service restored to the site.

Additionally, when WordPress site monitoring notifications are enabled in MyKinsta (User Settings > Notifications), if we detect one of the errors below in 3 consecutive checks on your WordPress site, we’ll send you an email to let you know your site needs critical attention:

  • Site Errors – We utilize a custom-built tool for monitoring our infrastructure. If we detect errors or issues on your site, we’ll send you an email notification to let you know.
  • DNS Errors A correct DNS configuration is of critical importance for your WordPress site. If we detect that your site’s DNS isn’t pointed correctly to Kinsta, we’ll send you a notification right away.
  • SSL Errors – If there’s a configuration issue with your domain and the SSL certificate expires, we’ll notify you.
  • Domain Expiration – If we detect an expired domain assigned to your Kinsta site, we’ll send you an alert.
Example of a monitoring notification email
Example of a monitoring notification email

Maintenance period

Kinsta’s maintenance window occurs daily, Monday through Sunday, from 2 am to 5 am local time, aligned with the time zone of the respective data center hosting each application or site. While maintenance isn’t necessarily conducted every day, if it does occur, it will take place within this timeframe. Typically, there is no downtime in this duration, resulting in little to no impact on your websites, applications, and databases. If you want to view information about specific maintenance or find out if there are any disruptions to our website, control panel, or hosting platform, refer to the Kinsta Status page.

We do not send monitoring notifications if maintenance is performed during this time. For more information, refer to Kinsta’s Service Level Agreement.  

WordPress site monitoring notes

Some scenarios that may interfere with our uptime monitoring include:

  • Password protection (basic authentication). If this is enabled, your site will return a 401 error to our monitor.
  • A site in maintenance mode (which can happen when running updates or if a maintenance mode plugin is enabled) may return a 503 response, which prevents monitoring.
  • We can’t monitor non-WordPress sites.
  • Bot blocking service or plugin. If you block all bots or if you’ve blocked our kinsta-bot user agent, our monitor will receive a 406 response code and won’t be able to monitor the site.
  • If either our uptime monitor’s IP address(es) or origin country (geo-blocking) is blocked, this will prevent monitoring. If you activate these features on Kinsta’s servers, we can add exceptions so our monitor won’t be blocked.
  • Custom caching rules and configurations at CDN, proxy, or security services may cause issues. Caching everything, including Kinsta’s query string HEAD request, will interfere with our monitoring.
  • Sites with reverse proxy setups where the primary domain isn’t redirecting to the target URL can’t be monitored.
  • If the primary domain doesn’t resolve to the install where it’s added, or it has a redirect to another domain (listed in the same site’s domain list).
Was this article helpful?