- Started
- 8/26/2026, 10:25:43 AM
- Ended
- 8/26/2026, 10:31:13 AM
- Notes
- —
- Opened after
- 3 failed checks in a row
Loading Reachability Record
Checking the latest saved view
The requested page will appear when its current record is ready.
Loading Reachability Record
The requested page will appear when its current record is ready.
Latest automated check for downdetector.com: No — It Is Up. Last check 8/28/2026, 9:00:07 AM.
No warning on this strip means the snapshot reflects the latest completed check. The live status panel raises a freshness warning when checks fall behind.
Current open record first, then recent stored records from automated checks.
Last 24 hours has 97 periods up, 0 down, and 0 without enough samples (15-minute periods).
| Period start | Result | Up | Down |
|---|---|---|---|
| 8/28/2026, 9:00:00 AM | Up | 1 | 0 |
| 8/28/2026, 8:45:00 AM | Up | 30 | 0 |
| 8/28/2026, 8:30:00 AM | Up | 30 | 0 |
| 8/28/2026, 8:15:00 AM | Up | 30 | 0 |
| 8/28/2026, 8:00:00 AM | Up | 30 | 0 |
| 8/28/2026, 7:45:00 AM | Up | 30 | 0 |
| 8/28/2026, 7:30:00 AM | Up | 30 | 0 |
| 8/28/2026, 7:15:00 AM | Up | 30 | 0 |
| 8/28/2026, 7:00:00 AM | Up | 30 | 0 |
| 8/28/2026, 6:45:00 AM | Up | 30 | 0 |
| 8/28/2026, 6:30:00 AM | Up | 30 | 0 |
| 8/28/2026, 6:15:00 AM | Up | 30 | 0 |
An up result includes 403 responses from Cloudflare, which still indicate the target is reachable.
Period rule: down when down samples are greater than zero and at least equal to up samples; otherwise up. A period with no samples is unknown.
Live check — The live answer strip at the top summarizes the latest automated HTTP check of downdetector.com. The newest answer always lives on the homepage live status panel; a freshness warning there means checks are still catching up.
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.
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.