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.
Public status pages
Let your users answer “is it down?” without asking you.
Is it down? Your users answer it themselves.
When something breaks, the same question arrives from every direction at once: is it down, or is it me? A status page answers it once, for everyone, so the replies you'd be typing get read off a page instead.
It shows the monitors you choose, each with ninety days of history and the incidents that made the marks. Green when you're up, honest when you're not, without you in the loop to say so.
A status page isn't a second thing to keep true. It reads from the same monitors you already have, so what it shows is what actually happened, down to the check.
Pick which monitors are public and which stay internal. An outage on a public one appears on the page as it appears on your dashboard, because it's the same event.
Put it on your own domain
Serve the page from a hostname you own, status.yourcompany.com, instead of an UptimeX subdomain, so it reads as yours and not as a third party's. Point a CNAME at it and the certificate is handled for you.
Choose the monitors, set the title, and share the link. There's nothing to host and nothing to keep running.
The rest of the platform.
Every outage, written down as it happens.
A confirmed failure opens an incident and keeps the timeline, detected to resolved. The first half of the post-mortem writes 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.