Methodology
How WebsiteDown.org Checks Website Status
WebsiteDown.org separates live reachability evidence from provider status pages, user symptoms, and local troubleshooting so outage decisions are easier to verify.
The goal is fast incident triage, not a perfect model of every private workflow behind a service.
Probe logic
Each live check is designed to answer whether a public domain is reachable now from more than one network path.
- Checks run against the submitted domain or the default domain for a service page.
- WebsiteDown.org records reachability, final URL, response timing, and region-level success or failure where available.
- Verdicts are interpreted as Up, Down, or Mixed based on whether regional probes agree.
- Mixed results usually mean the next question is routing, DNS, TLS, CDN, regional blocking, or provider-side partial degradation.
Region coverage
The visible region list helps users separate global outages from route-specific or geography-specific symptoms.
- US East (IAD)
- US West (SFO)
- Europe West (CDG)
- Europe Central (FRA)
- Asia South (Singapore)
- Asia East (Tokyo)
- Oceania (Sydney)
- South America (Sao Paulo)
Timestamp policy
Live evidence and editorial review dates describe different things.
- Live checked time appears in the result panel and describes the current probe result.
- Latest status history uses recent public checks for the same service page when available.
- Last reviewed, service profile updated, and official sources reviewed describe the curated registry content behind each service page.
- Sitemap lastmod dates describe when generated pages were rebuilt, not when a provider had an incident.
Service profile data
Service pages are generated from curated registry fields rather than free-form copied template text.
- Each profile includes service name, domain, category, company group, checked surfaces, common failure modes, local next steps, related hosts, official sources, internal links, and limitations.
- Official sources are shown separately from WebsiteDown.org results so users can compare independent reachability evidence with provider-controlled status or support information.
- Related checks are curated to help compare parent, child, sibling, or category-level incidents without blending unrelated services into the primary verdict.
Limitations
A public reachability check is useful evidence, but it is not the same thing as full product observability.
- A successful check does not prove authenticated dashboards, account state, checkout, playback, APIs, or private tenant workflows are healthy.
- A failed automated probe can be affected by bot filtering, firewall policy, DNS differences, rate limits, or temporary route issues.
- Provider status pages and social profiles may confirm incidents, but they can lag behind real user symptoms.
- WebsiteDown.org is independent and is not affiliated with the services listed on diagnostic pages unless explicitly stated.
Data retention and privacy
WebsiteDown.org keeps public check history focused on operational diagnostics.
- Recent public checks may be displayed as aggregate or page-level status history.
- Private account credentials are never required for website status checks.
- Operational logs may be used for abuse prevention, reliability, debugging, metering, and product improvement.
- Privacy and legal request details are maintained on the Privacy and Contact pages.
Review process
Generated service pages are only accepted when registry data and visible HTML pass the landing quality validator.
- Every indexable service page must have a complete registry entry.
- The validator checks required sections, official sources, internal links, canonical/sitemap consistency, structured-data limits, and duplicate-risk patterns.
- When service profiles or source lists are updated, the generated page shows review dates in its data notes section.