How It Works
A short summary of how the monitor checks the target, records incidents, and exposes the public status feed.
1. Check the target
The monitor makes recurring HTTP requests to downdetector.com and stores the latest status, timestamp, HTTP result, and latency.
2. Publish incidents
Incidents open after repeated failed checks and close after repeated recoveries. Admins can also publish or correct incidents manually when review is needed.
3. Expose the feed
The homepage, history page, and /api/v1/* endpoints all read from the same status and incident data.
Notes
A response under HTTP 500 still counts as reachable. That includes Cloudflare 403 responses, because the target infrastructure is still answering.
Use the API reference for raw payloads, or history for the public timeline.