Jetpack’s downtime monitor will keep tabs on your site, and alert you the moment that downtime is detected.
Once activated, one of our servers will start checking your site every five minutes. If it looks like something’s gone awry, we’ll fire off an email notification to the WordPress.com account that Jetpack is connected under.
- Is your site up and running properly, but you’re receiving ‘site down’ notifications?
- How does this work behind the scenes?
If you’d like to add something to your email filters to make sure these notification emails never get sent to spam, they’ll all be coming from
email@example.com, and have one of the following subject lines:
[Jetpack Monitor] jetpack.com is not loading!
[Jetpack Monitor] jetpack.com is still offline.
[Jetpack Monitor] jetpack.com is back up!
The first message will be sent when we first detect your site being down. The second will arrive if it’s still down after about an hour, and the final message will come when it looks like your site is back up again!
Is your site up and running properly, but you’re receiving ‘site down’ notifications?
This can happen for different reasons, and the content of the Notification emails should tell you more.
Your site is responding intermittently, or extremely slowly.
Your site may be loading slowly. If your site can’t be loaded in less than 20 seconds, we consider it as inaccessible. This may happen if you’re on shared hosting, where your bandwidth is shared with many other websites, or if you have a lot of resources loading on your home page; this will slow your site down.
Note that in some cases your site may be slow for a few minutes only. Its loading speed then comes back to normal after your hosting provider has taken measures to isolate other sites on your server that may have used too many resources and slowed everyone else’s site down for a few minutes.
Our requests are being redirected too many times.
If this happens, make sure your site URL is properly set up and that you don’t use any redirection plugins that may cause issues.
Jetpack is blocked.
Make sure your hosting service isn’t blocking our monitoring agent! The user agent that we’re sending along with the HEAD requests should be jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)! If it’s still not going through properly, please contact support.
The server does not respond.
If your theme or one of your plugins create 500 errors, also known as Fatal Errors, on your site, readers won’t be able to access your site and we will send you an email to let you know.
How does this work behind the scenes?
When we check your site, we ping your site’s homepage (via a HTTP HEAD request) every five minutes.
We tentatively mark your site as down if the HTTP response code is 400 or greater, which indicates either a permissions error or a fatal code error is prohibiting your site from appearing to visitors, or we see more than three 300-series redirects, suggesting a redirect loop, or if your site fails to respond within 20 seconds.
Once it is tentatively marked down, we then spin up three separate servers in geographically different locations from a third-party vendor to ensure the problem is not isolated to our network or the location of our primary datacenter.
If all three checks fail, we mark the site as down and notify you.
Note: Jetpack uses the timezone set in your WordPress settings (Settings > General)
This feature is deactivated by default. If you ever need to deactivate this feature, you can click on the Settings link in the Downtime Monitoring section from Jetpack — Dashboard — At a Glance in your dashboard. Once you’re viewing the feature’s settings on WordPress.com, toggle the Monitor your site’s downtime setting found within the Downtime Monitoring section at the top of the page.
Site Owners / Users
Site owner’s local user ID, WordPress.com user ID, email address, WordPress.com-connected blog ID, and the date of the last downtime status change.
Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
Site Owners / Users
We track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.
|Data Synced (Read More)|
Site Owners / Users
We sync options that identify whether or not the feature is activated and how its available settings are configured.