History
No — It Is Up
Latest monitor result, refreshed automatically.
An up result means the target returned any HTTP status under 500, including a Cloudflare 403. See support for the current monitor rules.
Last 24 hours contains 96 up bins, 0 down bins, and 0 empty bins at 15-minute resolution.
An up result includes 403 responses from Cloudflare, which still indicate the target is reachable.
Recent incidents
| State | Started | Ended | Notes | Opened after |
|---|---|---|---|---|
| resolved | 3/30/2026, 8:51:06 PM | 3/30/2026, 8:53:36 PM | — | Opened after 3 failed checks in a row |
| resolved | 3/30/2026, 8:46:36 PM | 3/30/2026, 8:49:36 PM | — | Opened after 3 failed checks in a row |
| resolved | 3/30/2026, 6:56:06 PM | 3/30/2026, 6:59:36 PM | — | Opened after 3 failed checks in a row |
| resolved | 3/30/2026, 4:38:06 PM | 3/30/2026, 4:41:36 PM | — | Opened after 3 failed checks in a row |
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 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.