Monitoring is only as good as the alert. An email that lands in a filtered folder at night is no better than no monitoring at all. Uptimecheck sends incident notices to the channels your team actually watches, and only when the failure is real.
Supported channels
- Email: alerts and recoveries to any address.
- Slack: the Add to Slack app posts to the channel you pick, with an Acknowledge button on outage alerts. An incoming webhook works too.
- Microsoft Teams, Discord, Google Chat and Mattermost: alerts to the channel or space your team works in.
- Telegram: tap Open Telegram, or Add to a group, press Start, and the chat is linked.
- PagerDuty: opens an incident when a monitor goes down and resolves it when it recovers.
- ntfy and Pushover: alerts to the phone apps many developers already use.
- Push notifications: lock-screen alerts on iPhone, Android and computers at no cost, to chosen people or whoever is on call.
- Webhooks: JSON to any URL, signed so the receiver can verify it came from us.
SMS alerts use credits: Professional includes 50 a month and Business 200, and any plan can buy more (100 for €12 or 500 for €50, excl. VAT; bought credits never expire). One credit is one text, so a typical outage uses two per number: one when it goes down and one when it recovers. SMS goes to mobile numbers in the EU/EEA, the UK and Switzerland. Every other channel is included on every plan, from Start to Business. Compare the other limits in the feature comparison.
What an alert contains
Enough to act on without logging in: the monitor name, the address, the status code or error and when it started. When the check passes again, a recovery notice follows with the total downtime.
- 03:12: checkout.northwind.shop is down. HTTP 503, confirmed by a second check.
- 03:19: resolved. checkout.northwind.shop is back up after 7 minutes.
The same channels get slow alerts, certificate and domain reminders, DNS record changes and new problems found by domain and site health checks.
Fewer false alarms
One failed check is not an outage. Uptimecheck checks from Stockholm, Sweden, and confirms every failure with a second check before an incident opens. Teams stop ignoring alerts when alerts stop crying wolf.
Escalation and on-call
Not every alert needs to wake someone. “When to alert” on a channel delays it: post to Slack right away, and send a push notification to whoever is on call only if the outage lasts 10 minutes. If the monitor recovers or someone acknowledges the incident first, the delayed alert is never sent. On-call schedules decide who that is this week, and the incident timeline shows who was alerted and when.
Know when an alert channel breaks
A channel can stop working without anyone noticing: a Slack webhook is removed, a mailbox fills up, a token expires. Uptimecheck retries a failed alert five times over about 40 minutes, and if it still does not arrive, the channel is marked Not delivering with the reason. The overview, every monitor that uses the channel and the weekly report say so too, so it is fixed before the next outage. When a test gets through again, the warning goes.
If a site recovers before its outage alert got through, the late alert is not sent, so nobody is paged for something that is over. The recovery notice still goes, with how long the site was down. When an incident closes because a maintenance window starts or a monitor is paused or deleted, the channels that heard about the outage get a notice saying so, and PagerDuty resolves its incident.
Route alerts per monitor
Default channels are added to every new monitor, and you can pick channels per monitor. Send the checkout monitor to push and Slack, the marketing site to email, and the staging API to a Discord channel. Agencies can route each client’s monitors to the right team, grouped by project.
Set up alerting in a few minutes
- Add your channels: an email address, Slack with Add to Slack, Telegram with one tap, push on your phone, or a webhook URL.
- Use Send test to see exactly how an alert looks there.
- Choose which channels each monitor uses, and which ones wait before they alert.
Keep the number of people who get on-call messages small and the Slack channel focused. Alerts work when they are rare, specific and clearly owned. Review your routing after every incident: if an alert reached someone who could not act on it, move it.
Webhooks for everything else
If your team uses a tool that is not on the list, a webhook covers it. Uptimecheck posts JSON to your URL when a monitor goes down and again when it recovers, with a signature your code can check, and your own code can forward it to a ticket system or a dashboard on the office wall.
Alerts for your team, a status page for your customers
Alerts tell your team. A status page tells your customers. Use both, and support does not have to answer the same question a hundred times. Alerts cover every monitor type: uptime, flows, cron jobs, servers, domains, DNS and third-party services.
Plans start at €9 per month billed yearly or €12 billed monthly, excl. VAT, with 25 alert channels on Start, 75 on Professional and 250 on Business. See the pricing page, or start a 14-day free trial without a card.