Transparency
History
Recent snapshots and incident timeline for our checks of downdetector.com.
Current Status
Checking…
Updates every 30 seconds from the monitoring worker.
Visual-only heatmap. Summary: up=0, down=0, empty=0 bins.
“Up” means the target returned an HTTP status code under 500. This includes 403 responses (Cloudflare bot protection) which still indicate the site infrastructure is reachable.
Recent incidents
| State | Started | Ended | Flags | Trigger |
|---|
What “up” means here
Every ~30 seconds we make a simple HTTP request to https://downdetector.com.
We classify the result as up when the response HTTP status code is < 500. This intentionally treats 403 as “up” because Cloudflare/bot protection can block automated checks even when the site is operational.
Incidents are detected using a consecutive-failure heuristic to avoid flapping. This is a single-region check today, so it can produce false positives during routing issues between our server and the target.