Alerts on the change, not every minute.
Once when it breaks, once when it recovers, to Slack, Discord, a webhook, email, or your phone. A confirmation streak holds back the blips.
Incident tracking
Every outage written down as it happens, on its own timeline.
The outage writes itself down as it happens.
When a check fails past its confirmation streak, UptimeX opens an incident on its own. No one has to notice first and start a doc; the record exists from the moment the outage does.
From there it keeps a timeline, detected, identified, monitoring, resolved, stamped with the times and what each check saw. When the service recovers, the incident closes itself and the duration is already there. The first half of the post-mortem is written before anyone opens their laptop.
The page you get and the incident that opens are the same thing seen twice, so they never disagree. The alert links straight to the timeline, and the timeline is what your status page reads from.
That means one source of truth for an outage: what paged you, what your users saw, and what goes in the review are all the same record.
Decide what opens one
An incident opens on a confirmed failure, not a single blip, because the same confirmation streak that holds back a noisy alert holds back a noisy incident. Recovery has to hold too: a service that flaps up for one check and back down doesn't close the incident and reopen a new one.
Nothing here needs configuring to start. Create a monitor and its incidents are already being kept.
The rest of the platform.
A status page your users can read.
Every monitor can back a public status page with ninety days of history, on your own domain, so the question answers itself.
Planned downtime that pages no one.
Schedule a window and the monitors it covers stop being checked, so nothing alerts, no incident opens, and the time is left out of your uptime.
Seven kinds of check, one app.
HTTP / Website, Keyword, API, Heartbeat, Scheduler, DNS, and Port. Every one reports up, slow, or down, on the same interval, into the same alerts.
Tune it when the defaults aren't right.
Interval, slow threshold, timeout, failure streak, redirects, SSL and domain expiry. Every knob the create form has, with a sane default on each.
Everything the dashboard does, the API does.
Create, test, mute, and delete monitors over the REST API with a project key, or let your agents do the same over MCP.