Methodology
How status is calculated, what we measure, and what we do not claim.
Official sources
When a provider publishes a verified status API, RSS/Atom feed, or status page, that signal is treated as a strong official input. Source outages are tracked separately from service outages. If a status page is unreachable, we say the official source is temporarily unavailable rather than declaring the product down.
Independent checks
HTTP probes measure reachability and latency from our monitoring location. A single failed request is treated as a possible transient failure, not a global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
User reports
Anonymous reports can support other evidence. They are rate-limited and never stored with raw IP addresses.
Confidence model
Status is a rule-based combination of official signals, consecutive probe results, and supporting user reports. When evidence conflicts or is weak, we prefer "status uncertain" over a false major outage.
Limitations
V1 monitoring is from a single probe region. We do not claim perfect global availability detection. Timestamps reflect the last completed check, not a simulated live clock.