Alert notifications
Get told the moment something breaks, on the channel you already watch.
Where the news actually lands
An alert nobody sees is the same as no alert. UpCheck sends to the places you already have open, Slack, Discord, a webhook into your own tooling, or email, so the news reaches you where you'll notice it and not in a dashboard you open once a week.
Push to the iPhone, iPad, and Mac apps is on from your first monitor, with no channel to wire up. The rest you add once and point at whichever monitors should use them.
Alerts on the change, not every minute
A monitor that pages you every minute for an hour is a monitor you mute, and a muted monitor is worse than none at all. UpCheck alerts on the transition: once when a check goes down, once when it recovers.
A confirmation streak sits in front of that, so a single blip that fixes itself on the next check never reaches you. You hear about the outage, not the flap.
Route the right alert to the right place
Every channel carries a routing rule, so the alert for a production API and the alert for a staging cron don't have to go to the same room. Send everything to one channel, or scope a channel to a handful of monitors and keep the noise off the people who don't own them.
Add a channel from the dashboard, send a test through it before you rely on it, and it starts carrying alerts on the next state change.
Build trust with
public status pages.
Every monitor can back a public status page, so the people asking whether you're down can answer it themselves. Ninety days of history per monitor, on your own domain.
Every outage,
written down as it happens.
A failed check opens an incident on its own, and it keeps a timeline: when it broke, what we saw, when it recovered. Nobody has to remember to write the post-mortem's first half.
Planned downtime
shouldn't page anyone.
Schedule a window and the checks keep running, but the alerts stay quiet and the uptime maths doesn't count it against you. One-off or recurring, per monitor.