Public reads do not need an account
Public status, history, and incident record reads work without login. Accounts are optional for email alerts, API keys, and sign-in security; see the API reference for endpoint behavior.
Support
Short answers about accounts, alerts, and how we mark a site up or down.
Why 403 can still mean up
Any HTTP response under 500 counts as reachable. A Cloudflare 403 means the target answered, even if the check was blocked.
When is the live answer current?
Treat the answer as current only when the live status panel shows no freshness warning. If a warning appears, we may still show the last known up or down while checks recover. Integrators can read trust and freshness details in the API reference.
Need a human reply?
Use the contact form for support, privacy, or legal questions.
Incident labels and timelines
Incident records are monitor-maintained records separate from the live panel verdict. The homepage answer reflects the latest automated check; incident record labels describe how an event was recorded.
Manual review means an operator opened an incident record after checking context that automation alone could not settle.
Reviewed as false alarm means an operator later decided the record should not be treated as a confirmed outage.
Incident record detail pages expand timelines and updates beyond the short summaries on the homepage and history views.
Hasher Technologies LLC handles support, privacy, and legal requests for this site.
Use the contact form or email contact@downdetectordowndetectordowndetector.com.
Hasher Technologies LLC155 Cherokee Place #1109, Cartersville, GA 30121
Automated account emails may come from noreply@downdetectordowndetectordowndetector.com, but replies to that address are not monitored.