Downtime alerts on the channels your team already watches

Which notification channels are available?

Uptime Tracker supports 14 notification channels, and the five most common ones are free on every plan.

Every alert includes the monitor name, a redacted target and the failure reason, such as a timeout, an unexpected status code or an invalid certificate. Recovery messages are sent when the monitor is confirmed up again. Uptime Tracker does not offer voice or phone-call alerts. Setup guides for each channel are on the integrations page.

SMS alerts: coverage and pricing

SMS alerts are available on Starter and Team to verified phone numbers in 231 countries, and they are paid from prepaid credit so you never get a surprise bill. Each number must be verified before it can receive alerts, which prevents typos from sending outage details to a stranger.

How SMS credit works:

• Buy message packages of 50, 100 or 250 messages, or top up a wallet balance.
• The price per message is shown for each destination country before you buy, because carrier costs differ widely between countries.
• Credit is used only when an SMS is actually sent.

SMS is the right channel for a small number of genuinely urgent monitors: checkout, login, the main API. Use routing rules so that only those monitors send texts, and let everything else go to Slack or email. A typical incident sends two messages per recipient, one when the monitor goes down and one when it recovers, plus any repeat reminders you enable.

If you want phone push notifications without per-message cost, Pushover, ntfy and Gotify are included on Starter at no extra charge.

Routing rules and repeat reminders

Routing rules on Starter and Team decide which alerts go to which channels, so urgent problems reach the right people and minor ones do not wake anyone up. Rules can match on:

• Tags, such as production, client-acme or domains.
• Specific monitors, for example only the checkout monitor.
• Event type, such as down, recovered or a domain-expiry warning.
• Day and time windows in the workspace time zone, such as weekdays 09:00 to 18:00.

A common setup sends every production alert to a Slack channel at all times, adds SMS outside business hours for monitors tagged critical, and sends staging alerts to email only during the working day.

Repeat reminders keep notifying until someone acknowledges the incident or the monitor recovers. They prevent the most common failure in small teams: an alert that arrives, gets glanced at, and is forgotten while the outage continues. Acknowledging an incident from the dashboard stops the reminders and records who took ownership.

Throughput limits protect your channels during a large outage: Free delivers up to 60 notifications per minute, Starter 120 and Team 600.

On-call, escalation and PagerDuty on Team

The Team plan adds on-call rotations, escalation policies and PagerDuty, so an alert always reaches a specific person and moves on if they do not respond.

• On-call rotations follow a weekly-style schedule with handoffs at a local time you choose. They handle daylight-saving changes correctly, and each schedule has an iCal feed you can subscribe to in your calendar.
• Escalation policies define sequential steps, for example the on-call engineer first, then the team lead, then the whole team channel. A policy can repeat up to 5 times and stops as soon as someone acknowledges the incident or the monitor recovers.
• PagerDuty integration uses the Events API v2 for US or EU accounts. Incidents are de-duplicated, so a flapping monitor does not create a pile of PagerDuty incidents, and they resolve automatically on recovery.

Team also supports monitor dependencies: if a parent monitor such as your load balancer is down, alerts for child monitors behind it are suppressed, so you get one meaningful alert instead of twenty. Read more in incident management.

Signed webhooks for custom integrations

Webhooks, available on every plan, send a JSON event to any HTTPS endpoint when a monitor goes down or recovers, so you can connect Uptime Tracker to chat tools, ticketing systems or your own automation.

Each delivery is signed with HMAC-SHA256. The signature header has the form t=…,v1=…: t is a timestamp and v1 is the signature. To verify a delivery:

1. Read the timestamp and signature from the header.
2. Recompute the HMAC-SHA256 signature with your webhook secret, following the signing format in the help center.
3. Compare it with v1 using a constant-time comparison.
4. Reject deliveries whose timestamp is outside the replay window.

Failed deliveries are retried with backoff, so a brief outage on your receiving endpoint does not lose events. Exact payload fields and the signing string are documented in the help center. Webhooks are a good way to open a ticket automatically, post to a chat tool that is not natively supported, or trigger a self-healing script.

What's included on each plan

Every plan includes confirmed down and recovery alerts; paid plans add channels and control over who gets notified when.

Free works well for individuals and small teams who watch a chat channel or inbox. Starter is the step up when alerts must reach a phone, through SMS or push, or when different monitors need to reach different people. Team is designed for groups with a formal on-call duty and a need to escalate when nobody responds.

SMS credit is bought separately from the subscription, so the plan price stays fixed regardless of how many texts you send. See the pricing page for all plan limits.