How downtime is calculated in Site24x7?

How does Site24x7 calculate downtime of a website?

When a website availability check from its primary monitoring location fails, Site24x7 waits up to 15 seconds to get a response from the website (15 seconds is the default connection timeout period).
If there is no response within 15 seconds, rechecks will be done from the secondary monitoring locations (selected by the user) asynchronously based on the downtime rule selected in the threshold profiles (3 secondary locations, by default). If the website does not respond to any of these down rechecks, Site24x7 declares the website as unavailable and sends out alerts. However, it will also trigger an aggressive polling, until the next poll. In between the aggressive poll, if a status change is identified, an alert will be immediately triggered, though. Also, during the asynchronous check, if at least any one poll returns a UP status, the monitor will be deemed UP and no alert will be triggered until the next recheck is performed and the same validated.

Let's take an example to explain this case. Assume your website is being monitored every 5 minutes (check frequency) with a connection timeout of 30 seconds; you've selected the downtime rules in threshold configuration as "alert if down from 3 monitoring location"; Now,
  • At 10:30:00 AM - Site24x7 polls your website from primary location (e.g.- California). Now assume your site does not respond within 30 seconds.
  • At 10:30:30 AM - Site24x7 does a down recheck from secondary location #1, #2, and #3 asynchronously. If none of these locations receive a UP status, an alert will be triggered immediately followed by aggressive polling until the next poll.
    Note: A monitor check happens only after the data collection ends during the previous poll.
  • At 10:32:00 AM - Aggressive poll detects the status change to UP and instantly triggers an alert. Hence, the total outage duration is detected for 2 minutes. However, if the aggressive poll fails until the next poll, the outage duration is calculated as the total downtime calculated from 10: 30 AM till the start of the next immediate poll.
On the contrary, if any one location recheck returns a UP status, it will fail the downtime rule and no alert will be triggered.

    • Related Articles

    • Response time in Website monitoring

      In website monitoring, response time is calculated as the total time taken to resolve the DNS, complete the TCP hand-shake, negotiate an SSL handshake (for HTTPS) and download the full HTML output from the server. However, it does not include getting ...
    • Why is my website response time too high from China?

      If your website is hosted outside China and you have chosen China as the location for monitoring, then the website response time will be high. This is because of the Great Firewall policy followed by China wherein, all the data coming from outside ...
    • How does the Poll Strategy setting work for website monitors?

      When configuring thresholds for performance metrics, you can set strategies that the website monitor will use to send alerts during a threshold breach. There are four options available: Poll count Poll average Time duration Average time The default ...
    • Possible reasons for website unavailability

      Site24x7 monitors the availability of your website by sending an HTTP request to the webserver and checks the status code of the returned response. A 200 OK success response indicates that the website is available. We will consider a website as ...
    • Escalate my downtime alerts to specific contacts

      Configure your escalation settings to define your escalation policy. Pick an own roster to send the notifications during a breach and specify the exact time before escalation. You can escalate any downtime by updating your Notification Profile. To ...