Exclude Socket Timeouts from Uptime monitoring

Some sites are reporting as being down, but we can’t verify it and our hosting company (SiteGround) says they’re not going down at all. All of these potential false negatives are recorded in WPMUDEV as “Socket timeout”.

I found out that this error means that my site could be very slow responding in the reported time.

The problem is that the downtime is showing in the reports we send to the clients, but we and our hosting company nor our client nor anyone can confirm they’re down.

How can these socket timeouts be represented differently in reports and notifications?

  • Adam
    • Support Gorilla

    Hi Kevin

    I hope you’re well today and thank you for your question!

    There might indeed be some cases when the site is reported as being down while it’s not really down, just slow. Our Uptime monitoring sets “limit” to 30 seconds (if I’m not mistaken) so if the site doesn’t respond with expected HTTP headers, it is considered as “down”.

    Due to stability and performance (and results reliability) we had to arbitrary set such “timeout threshold” so all these “connection timeouts” are reflected in the Uptime report and currently there is no way to change that other than just disabling Uptime section in a report entirely.

    I do, however, see the point and agree that it would be handy to be able to “customize” the report – for example make it include only down times over e.g. 5 minutes or 1 hour long, so others would be ignored.

    Having said that, I’ve passed the idea to our managers for further consideration as I believe it would make a nice feature.

    Kind regards,

    Adam