DDDownDetector Monitor

Transparency

History

Recent snapshots and incident timeline for our checks of downdetector.com.

API Docs
Range
Heatmap uses 15m bins.

Current Status

Checking

Checking…

Updates every 30 seconds from the monitoring worker.

Last Checked
—
Next Check
—
Last 24 hours
Uptime: —
Samples: —
Window: — → —
Snapshot heatmap (15m bins)
No data yet.
up down empty
up=0 down=0 empty=0 bins in this window.

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.

Current incident
Incident log

Recent incidents

JSON
Recent incidents
StateStartedEndedReviewDetected by
How we check

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 open after repeated failed checks to reduce false alarms. Because this monitor observes from one vantage point, rare routing issues between our service and the target can still create false alarms.