Loading Reachability Record
The requested page will appear when its current record is ready.
Short answers about accounts, alerts, and how we mark a site up or down.
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.
Any HTTP response under 500 counts as reachable. A Cloudflare 403 means the target answered, even if the check was blocked.
The live status panel raises a freshness warning when checks fall behind. While a warning is up, we may still show the last known up or down until checks recover. Integrators can read trust and freshness details in the API reference.
Use the contact form for support, privacy, or legal questions.
Reachability Record checks one target and does not offer service search. Visitors cannot submit an outage report or add crowd evidence. Contact reaches the product operator for account, product, privacy, and legal support; it does not alter the live verdict.
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 [email protected].
Hasher Technologies LLCAutomated account emails may come from [email protected], but replies to that address are not monitored.