I like this idea. We have the concept of what we call “SLA uptime” which is like uptime, but uptime is only impacted if 2 runs failed in a row, from different locations. Essentially we are trying to take the network between the test location and the target out of the equation. However this is not well exposed in the UI and it not available everywhere. Perhaps that can help address this.Shiva Subramanian shared this idea ·
We do have a way in the app to compute what we call SLA uptime, which specifically only flags downtime if 2 or more failures occur in a row, helping reduce the impact of a bad location.
Reaching out to Melanie with some clarifying questionsShiva Subramanian commented
this is necessary because of the distributed and redundant nature of the internet and the ISPs, a slowdown or failure from one site should not reduce the UPTIME of a website/app that has been available.