Incidents & maintenance
A failing check opens an incident on its own. What gets written on it, and which of that your customers see, stays yours to decide.
One incident, not forty alerts
Repeated failures against the same server or check roll up into a single incident with its subjects attached, so the alert channel gets one thread to follow.
- Opened automatically when checks confirm a failure
- Closed automatically on recovery, with the duration recorded
- Or opened by hand when you want to get ahead of something
- Public updates reach your status page and its subscribers; internal notes stay in the console
Incident #114
09:143 regions confirmed api.acme.com failing
09:16Posted to status.acme.com · 41 subscribers
09:52Recovered · duration 38m
EmailWebhookSlackDiscordTelegram
Say it before it happens
Schedule a maintenance window and it publishes itself to your status page in advance for everything it covers — no separate announcement to remember, and no ticket asking whether the outage was deliberate.
- Scoped to specific servers and checks, or to the whole project
- Shown in advance, then marked in progress while it runs
- Drops off the page on its own when the window closes
status.acme.com
Degraded · 1 of 4 services affected
WebsiteOperational
APIDegraded
DashboardOperational
Background jobsOperational
Start monitoring in about a minute.
Twenty checks and one server, free and with no card. Upgrade only when you outgrow it.