Why this happened,
with the evidence.
The incident page shows the likely cause with its confidence and the evidence behind it, or says unknown. Changes to DNS, the certificate, the final redirect and the search signals are marked when an incident follows within the hour, and a note for your team or client is drafted in three lengths.
- On every plan
- Unknown when it is unknown
- A note in three lengths
How it works
The proof is collected before anything goes wrong.
Changes are recorded
DNS records, the certificate, the final redirect address and the search signals go on the site’s What changed timeline as they change.
An incident opens when two regions agree
The incident page lists the stored checks of each region, oldest first, and the rule that opened it.
The likely cause, or unknown
With its confidence and the evidence, what was ruled out and what could not be checked, and a note you can forward.
What you get
Evidence for every check
For a web page: the status code, the redirects, the certificate, the DNS answer, the address connected to and the timings.
Changes marked in minutes
A change shortly before an incident is marked with how many minutes before it started.
A note in three lengths
A short, a medium and a long version of what happened, ready to send to your team or your client.
Your client sees only what you choose
A status page shows only the confirmed incident and the summary you wrote, never regions, addresses or evidence.
Which plans include it
Why this happened is on every plan, Free included.
- FreeIncluded
- SoloIncluded
- TeamIncluded
- AgencyIncluded
- Agency PlusIncluded
Questions about why this happened
How sure is the likely cause?
It comes with its confidence and the evidence it rests on, and it can be wrong. A likely cause is a ranked reading of stored evidence, not a diagnosis, and no AI model decides it. When the evidence does not point anywhere, the page says unknown instead of guessing.
What counts as a change?
A new DNS answer, a different certificate, a changed final redirect and a search-visibility signal. Signals that are not tracked yet are named on the timeline.
What does my client see?
Only the confirmed incident on the status page, with the public summary you wrote, never the evidence of the checks.
Related guides
- Website down: a first-15-minutes triage checklistA step-by-step triage for a site-down alert: confirm it, find the broken layer and decide what to tell the client.
- Incident communication to clients: templatesHow to tell a client about an outage: timing, tone, what to include and templates for the first message, updates and wrap-up.
Know why, with the evidence.
Add your sites: checking starts as soon as you do.
No card for the Free plan.