Skip to main content
D3DownDetector Monitor

History

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

Live answer snapshot

Latest automated check for downdetector.com: No — It Is Up. Last check 6/13/2026, 3:54:43 AM.

Treat the big answer as current only when there is no freshness warning.

Open live status panel
Range
Grid: one square per 15 minutes of stored checks.
Last 24 hours
Uptime: 100.00%
Samples: 2870
Window: 6/12/2026, 4:00:00 AM → 6/13/2026, 3:55:03 AM
Recent status grid

Last 24 hours has 96 periods up, 0 down, and 0 without enough samples (15-minute periods).

Last 24 hours check periods (15-minute bins)
Period startResultUpDown
6/12/2026, 4:00:00 AMUp300
6/12/2026, 4:15:00 AMUp300
6/12/2026, 4:30:00 AMUp300
6/12/2026, 4:45:00 AMUp300
6/12/2026, 5:00:00 AMUp300
6/12/2026, 5:15:00 AMUp300
6/12/2026, 5:30:00 AMUp300
6/12/2026, 5:45:00 AMUp300
6/12/2026, 6:00:00 AMUp300
6/12/2026, 6:15:00 AMUp300
6/12/2026, 6:30:00 AMUp300
6/12/2026, 6:45:00 AMUp300
6/12/2026, 7:00:00 AMUp300
6/12/2026, 7:15:00 AMUp300
6/12/2026, 7:30:00 AMUp300
6/12/2026, 7:45:00 AMUp300
6/12/2026, 8:00:00 AMUp300
6/12/2026, 8:15:00 AMUp300
6/12/2026, 8:30:00 AMUp300
6/12/2026, 8:45:00 AMUp300
6/12/2026, 9:00:00 AMUp300
6/12/2026, 9:15:00 AMUp300
6/12/2026, 9:30:00 AMUp300
6/12/2026, 9:45:00 AMUp300
6/12/2026, 10:00:00 AMUp300
6/12/2026, 10:15:00 AMUp300
6/12/2026, 10:30:00 AMUp300
6/12/2026, 10:45:00 AMUp300
6/12/2026, 11:00:00 AMUp300
6/12/2026, 11:15:00 AMUp300
6/12/2026, 11:30:00 AMUp300
6/12/2026, 11:45:00 AMUp300
6/12/2026, 12:00:00 PMUp300
6/12/2026, 12:15:00 PMUp300
6/12/2026, 12:30:00 PMUp300
6/12/2026, 12:45:00 PMUp300
6/12/2026, 1:00:00 PMUp300
6/12/2026, 1:15:00 PMUp300
6/12/2026, 1:30:00 PMUp300
6/12/2026, 1:45:00 PMUp300
6/12/2026, 2:00:00 PMUp300
6/12/2026, 2:15:00 PMUp300
6/12/2026, 2:30:00 PMUp300
6/12/2026, 2:45:00 PMUp300
6/12/2026, 3:00:00 PMUp300
6/12/2026, 3:15:00 PMUp300
6/12/2026, 3:30:00 PMUp300
6/12/2026, 3:45:00 PMUp300
6/12/2026, 4:00:00 PMUp300
6/12/2026, 4:15:00 PMUp300
6/12/2026, 4:30:00 PMUp300
6/12/2026, 4:45:00 PMUp300
6/12/2026, 5:00:00 PMUp300
6/12/2026, 5:15:00 PMUp300
6/12/2026, 5:30:00 PMUp300
6/12/2026, 5:45:00 PMUp300
6/12/2026, 6:00:00 PMUp300
6/12/2026, 6:15:00 PMUp300
6/12/2026, 6:30:00 PMUp300
6/12/2026, 6:45:00 PMUp300
6/12/2026, 7:00:00 PMUp300
6/12/2026, 7:15:00 PMUp300
6/12/2026, 7:30:00 PMUp300
6/12/2026, 7:45:00 PMUp300
6/12/2026, 8:00:00 PMUp300
6/12/2026, 8:15:00 PMUp300
6/12/2026, 8:30:00 PMUp300
6/12/2026, 8:45:00 PMUp300
6/12/2026, 9:00:00 PMUp300
6/12/2026, 9:15:00 PMUp300
6/12/2026, 9:30:00 PMUp300
6/12/2026, 9:45:00 PMUp300
6/12/2026, 10:00:00 PMUp300
6/12/2026, 10:15:00 PMUp300
6/12/2026, 10:30:00 PMUp300
6/12/2026, 10:45:00 PMUp300
6/12/2026, 11:00:00 PMUp300
6/12/2026, 11:15:00 PMUp300
6/12/2026, 11:30:00 PMUp300
6/12/2026, 11:45:00 PMUp300
6/13/2026, 12:00:00 AMUp300
6/13/2026, 12:15:00 AMUp300
6/13/2026, 12:30:00 AMUp300
6/13/2026, 12:45:00 AMUp300
6/13/2026, 1:00:00 AMUp300
6/13/2026, 1:15:00 AMUp300
6/13/2026, 1:30:00 AMUp300
6/13/2026, 1:45:00 AMUp300
6/13/2026, 2:00:00 AMUp300
6/13/2026, 2:15:00 AMUp300
6/13/2026, 2:30:00 AMUp300
6/13/2026, 2:45:00 AMUp300
6/13/2026, 3:00:00 AMUp300
6/13/2026, 3:15:00 AMUp300
6/13/2026, 3:30:00 AMUp300
6/13/2026, 3:45:00 AMUp200

An up result includes 403 responses from Cloudflare, which still indicate the target is reachable.

Incident log

Incident records

Current open record first, then recent stored records from automated checks.

JSON
Current incident record
No open incident record.

Recent incident records

Resolved record
Started
3/30/2026, 8:51:06 PM
Ended
3/30/2026, 8:53:36 PM
Notes
—
Opened after
3 failed checks in a row
Resolved record
Started
3/30/2026, 8:46:36 PM
Ended
3/30/2026, 8:49:36 PM
Notes
—
Opened after
3 failed checks in a row
Resolved record
Started
3/30/2026, 6:56:06 PM
Ended
3/30/2026, 6:59:36 PM
Notes
—
Opened after
3 failed checks in a row
Resolved record
Started
3/30/2026, 4:38:06 PM
Ended
3/30/2026, 4:41:36 PM
Notes
—
Opened after
3 failed checks in a row
Trust guide

How to read this page

Live check — The live answer strip at the top summarizes the latest automated HTTP check of downdetector.com. For the current answer, use the homepage live status panel and trust it only when no freshness warning is present.

Status grid — The status grid above groups stored check results into 15-minute periods for the selected range. On small screens the same periods appear as a readable table. It is not crowd-sourced outage reports or a third-party feed.

Incident records — Declared after repeated failed checks. The incident log above summarizes the current open record and recent incident records; incident record detail pages expand timelines and updates.

Reviewed as false alarm means an operator later decided the record should not be treated as a confirmed outage.

How we check

What “up” means here

On the currently configured monitor interval 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 reachable.

Incident records open after repeated failed checks to reduce false alarms. Because this monitor checks from one service, rare routing issues between this monitor and the target can still create false alarms.