Incident management and maintenance windows.
When your site goes down, Sitedown opens an incident on its own. You get a timeline of what happened and a way to tell your customers.
Every outage becomes an incident.
You do not open a ticket by hand. Sitedown detects the outage, records it, and closes it when the site is back.
Automatic detection
Sitedown checks your site on a schedule. The moment a check fails, it opens an incident. No manual step.
Status code timeline
We record each check with its HTTP status code and the exact time. Every code gets a plain explanation, so you know what happened and when.
Response and screenshot
On the first failure we save the server response and a screenshot. You see what your visitors saw, not just a code.
Internal notes
Add a private note for your team. It stays inside your account and never shows to visitors.
Public notes
Add a public note. It shows on your status page, so customers read one clear update instead of asking you.
Automatic close
When your site recovers, Sitedown closes the incident and marks the recovery time. The record stays for your history.
A timeline you can read.
Each incident is a list of checks in order, newest last. You see the status code at every step, a plain explanation of that code, and the moment the site came back. No log files to dig through.
Schedule maintenance ahead of time.
Planned downtime should not count against your uptime, and your customers should know it is coming.
Pick a window
Set a start and end time and choose which monitors it covers. Leave it empty to cover the whole workspace.
Uptime stays clean
During the window, a failed check does not open an incident and does not count against your uptime. It was planned.
Shown on your status page
The window shows on your status page as scheduled maintenance, with the times and a public note, so visitors are not surprised.
The incident lifecycle, from detect to review.
An incident moves through the same stages every time. Sitedown detects the outage from multiple regions and opens the incident on its own. It alerts your team on the channels you pick, and the phone website monitor app rings until someone acknowledges it. From that point the incident holds one clear record: the status code at each check, the first response, a screenshot, and any note you add.
While the incident is open, you post updates as you work. Internal notes stay private to your team. Public notes show on your branded status page, so customers read one clear update instead of opening tickets. When the site recovers, Sitedown closes the incident, marks the recovery time, and keeps the full timeline in your history.
That record is what you review after the outage. You see how long the site was down, which checks failed first, and how fast it came back. Because every incident starts from the same uptime monitoring checks, the numbers stay honest and you can spot a pattern across incidents instead of guessing.
Frequently asked questions
Know about downtime before your customers do.
Add your first monitor and let Sitedown handle the incidents. Free to start.