• Resolved Will Stocks

    (@willstockstech)


    Hi guys,

    I accidentally took my site down today – I have uptime robot setup to notify me when my site goes down, but as a backup I also have Jetpack.

    On this occassion (and a couple of others previously), Jetpack took around 27 minutes from the point of failure to detect and notify me that my site was down, vs uptime robot’s less than 5 minutes.

    Obviously this is less than ideal – is there anything I can do to improve this detection timeline? If I were relying on my site for sales and had Jetpack notifying me of outage (and nothing else), 30 minutes is a pretty significant amount of time for a site to be down before I’m aware and start diagnosis/resolution

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support darnelldibbles

    (@darnelldibbles)

    Hi there,

    Is your site willstocks.co.uk? I ran the site through debug and everything looks good there. Jetpack Monitor checks for downtime every 5 minutes, so you should, in theory, be receiving emails sooner than ~ 30 minutes.

    I checked our system to see what time we sent out our email notifications, just to make sure that our emails aren’t getting hung up. I see that we sent two emails 3 hours ago notifying you that your site was down and then shortly after that another email notifying you that it was back up. Can you provide the exact time you received those emails from us?

    Monitor pings might also be taking longer to realize your site is down, but again, it shouldn’t be taking ~ 30 minutes. However, I want to look to see if there is any discrepancy in times between sending and receiving the emails first and then go from there.

    Let me know if you have any questions. Thanks!

    Thread Starter Will Stocks

    (@willstockstech)

    Hi @darnelldibbles

    It is indeed!

    I received an email at 13:08 (down) and then another at 13:17 once I had resolved the issue. What time are you seeing the first email firing?

    My site actually went down between 12:40 and 12:45 (I got my first Uptime Robot through at about 12:49/12:50)

    So it was a little under half an hour between the actual outage and the first notification (give or take the 5 minute allowance for the checks – I believe my Uptime Robot plan is about the same check frequency)

    Plugin Support darnelldibbles

    (@darnelldibbles)

    We shot off the emails at 13:03 and another one at 13:08, so there was a little delay there, but even with that delay there is still a ~15-20 minute discrepancy, even when you factor in the 5 minute allowance.

    Have you tried doing a completely fresh install of Jetpack to see if that made any difference?

    • From the wp-admin dashboard of your site, please go to Jetpack > Dashboard > Connections > Manage site connection from your left-hand menu.
    • Click the “Disconnect” button.
    • Deactivate your Jetpack plugin by heading to Plugins > Installed Plugins and finding “Jetpack by WordPress.com.”
    • Completely uninstall Jetpack.
    • Reinstall the newest version of Jetpack.
    • Deactivate all of your plugins.
    • Activate only Jetpack.
    • Back in Jetpack > Dashboard > Connections > Manage site connection, Click the “Set up Jetpack” button and continue through the approval process.

    With a fresh install, I want to see if that makes any difference in the monitor pings. Ideally, you will never find out because your site won’t ever have downtime again, but realistically speaking, if/when it goes down, hopefully disconnecting/reconnecting will make the difference.

    Thanks,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Monitor – Pretty significant delay in detection to downtime’ is closed to new replies.