Operator guide

Report an incident, clearly.

A useful status page separates technical diagnosis from communication. isdown.website detects the anomaly, keeps its timeline, and makes it readable on the domain’s public page.

Check a domain Read the guide

01

Detect and confirm

  1. Open the domain’s public page. Use /status/domain-name to view the live state and regional probes.
  2. Compare the observations. An incident is more credible when it appears from multiple regions with a consistent HTTP status or error.
  3. Let aggregation confirm the incident. Consecutive failures prevent a single measurement from becoming a public outage.
Keep in mindThe public page shows observed state. It does not replace infrastructure verification or your escalation procedure.

02

Follow the incident

  • Check the confirmed-incident banner and its start time.
  • Use the timeline to distinguish suspicion, confirmation, recovery, and resolution.
  • Compare latency, HTTP status, and regions before communicating a global impact.

03

Resolve cleanly

When checks return to an operational state according to the configured recovery threshold, the incident moves through recovery and is marked resolved. The history remains visible so users can understand the full sequence.

Member areaThresholds, alerts, and acknowledgements are configured in the member area linked to your account.
Back to documentation