What a status check can tell you
A recorded check is a sample, not an uptime guarantee.
What we record
The monitor records when it attempted a check of downdetector.com and whether the result met its configured rule. Where available, it also records an HTTP response code and latency.
History’s successful-check percentage is calculated from stored samples in the selected window. Missing samples are not counted as successful visits.
What we do not know
We cannot see what happened between checks. One request also cannot establish whether every page, account flow, visitor or region worked.
A failed check does not identify the cause. The problem could be on the target path, at this monitor or between them. A response from Cloudflare is not an official statement about the application behind it.
Choose the right follow-up
For your own access, try the site on your own network. For an official service announcement, consult the service’s own communications.
If you operate the affected application, investigate its logs and user-facing transactions. This monitor can provide a timestamp to compare, but it cannot do that investigation for you.