Methodology
This page explains what Plain Tools status routes are intended to measure, how canonical status pages differ from query-like entry pages, and how to interpret live results without overstating what a single probe can prove.
Plain Tools treats `/status/{domain}` as the canonical route for ongoing status checks. Query-like routes can exist for user demand, but they should consolidate into the canonical domain page for linking, sharing, and sitemap inclusion.
A live result shows whether the latest probe could obtain a usable response. It does not automatically prove a global outage. Resolver failures, regional routing, firewalls, and other local conditions can still affect some users while the service remains reachable elsewhere.
Outage-history pages summarise aggregated check history and expose recent incidents as a user-facing timeline. They are meant to support investigation, not to replace an official provider incident report.
Status pages work best when users understand what the tool measured, what the page inferred, and what follow-up checks are sensible. That is why these pages are linked from the main status hubs and trust pages.
If a service looks down, compare the canonical status route with DNS lookup results, latency tests, and region-aware checks where available. This is the fastest way to separate platform-wide incidents from local network conditions.