Downtime alerts that escalate until someone acts.

Uptimia pages your team on 12 channels — Slack, SMS, WhatsApp, PagerDuty and more. If nobody reacts, the ladder pages the next person; one click stops it.

Start free trial → View pricing
30-day free trial · 50 team seats No credit card 12 alert channels included
Alert channels
12
Clicks to stop it
1
Checkpoints
171+
Countries covered
70+

From failed check to fixed outage

How a downtime alert finds the person who can fix it — at 2 p.m. or 3 a.m.

14:32:18 Step 1 — the team channelConfirmed from three regions → #ops-alerts and team email, instantly step 3: waiting
14:37 Step 2 — a real phoneNo acknowledgement in five minutes, so the ladder climbs: SMS and WhatsApp step 3: waiting
14:38 One tap: "I've got it"Sara taps the signed link — no login; the ladder freezes · MTTA 6 min step 3: waiting
15:03 Recovered — loop closedThe all-clear goes only to the people who were paged step 3: never fired
6 minmean time to acknowledge
Nobody was over-paged.15:03
The ladder climbed exactly as far as it had to — two steps — and froze the moment someone owned it. Step 3 exists for the night nobody answers; today it stayed quiet.
climbs until someone acknowledgesone acknowledgement freezes itall-clear to those paged12 channels · reusable ladders
And without a ladder? One alert, one channel, and hope somebody's looking at it. The 3 a.m. version of that story is an outage that waits, unclaimed, until morning. unclaimed

Every channel your team uses

Email and SMS are built in — Slack, Teams, WhatsApp, PagerDuty and the rest connect in a couple of clicks.

Slack & Microsoft TeamsPosted into the right channel
Discord, Telegram & MattermostGroup chats covered too
WhatsAppA message where you'll see it
PagerDutyStraight into the on-call rotation
1 incident routed to every channel you pick
Email, SMS & TwilioBuilt in — no setup at all
Webhooks & StatuspageAutomation and public status
Escalation ladder steps can page whole teams, individual teammates or any single contact — and every step can use a different mix of channels. per-step mix
Browse the full integrations directory →

Ladders, acknowledgment and noise control

Escalation ladders

Build the ladder once, attach it anywhere

A reusable ladder of up to 10 steps: who gets paged, and how long before the next step. Attach it to one monitor or a hundred — any type.

  • Waits from 5 minutes to 2 hours per step — step 1 always fires instantly
  • Bounded repeat rounds — re-page every N minutes, up to a limit you set
  • Never silent — a deleted or emptied policy falls back to everyone at once
How escalation policies work →
step 1 #ops-alerts + team emailfires immediately Slack · Email
+5 min Sara — on-call phoneif nobody acknowledges yet SMS · WhatsApp
+15 min Engineering lead + PagerDutyif still not acknowledged SMS · PagerDuty
↻ Re-page the last stepevery 30 min · max 3 rounds bounded
Recovery cancels every pending step — and an emptied policy never goes silent, it falls back to everyone at once. 1 policy · 24 monitors
Acknowledgment & MTTA

One tap, no login

Every alert carries a signed acknowledgment link. Tap it from SMS, Slack or email and the escalation freezes — no password at 3 a.m., ever.

  • Scanner-proof links — only the confirm-page button acknowledges, so email scanners can't silence an alert
  • Safety net — optionally resume the ladder if the site is still down N minutes after an acknowledgement
  • MTTA on every incident — who acknowledged, when, and how many minutes it took
Acknowledgment docs →
SMScarries the signed link
Slackcarries the signed link
Emailcarries the signed link
Acknowledge this incident?
Down — checkout.caldmont.com, since 14:32. One tap freezes the escalation — no password, ever. Only the confirm button acknowledges, so email scanners can't silence it.
✋ I've got itacknowledged by Sara · MTTA 6 m
Recovered 15:03 — all-clear to everyone paged. Optionally resume the ladder if it's still down N minutes after the acknowledgement. MTTA logged
Noise control

Only alerts worth waking up for

Uptimia confirms every outage from multiple regions before paging anyone, and merges related failures into one incident instead of ten.

  • Alert grouping — monitors on the same ladder failing together become one digest, one escalation, one all-clear
  • Quiet hours per person — nights and weekends hold pages until morning
  • Maintenance windows & pause — planned work never pages anyone; pausing a monitor cancels its queued alerts
Alert grouping docs →
www.caldmont.comon the Payments ladderdown
api.caldmont.comon the Payments ladderdown
checkout.caldmont.comon the Payments ladderdown
1 grouped incident#ops-alerts · 14:32
Three monitors on the same ladder failed together — one digest, one escalation, one all-clear. One acknowledgement covers all three.
not 3 pages× every channel× every step
Quiet hours hold pages till morning, and maintenance windows skip checks — planned work never pages anyone. per person
Team roles

Everyone on the team — nobody over-permissioned

Invite your team by email and give each person the access they need — five roles, from full admin down to a viewer who can only acknowledge.

  • Viewers can acknowledge — they just can't change anything
  • A free billing seat — your accountant sees invoices, never your monitors
  • Team audit trail — every invite, role change and removal is logged
Roles & permissions docs →
Ownereverything, incl. billingfull
Adminall but billing
Editormonitors — not the team
Viewerread-only, but can acknowledgecan acknowledge
Billinginvoices only — never your monitorsfree seat
Roles that actually holdevery request
Five roles, checked on every request — a viewer can't change a monitor even by trying. Invite by email; up to 100 seats.
invite by email100 seats
Every invite, role change and removal is logged — a full team audit trail. audit trail

Downtime should page you.Not a customer.

Ladders, acknowledgment and team seats are part of the plan price — never billed per seat, never a paid add-on.

Start your free 30-day trial →
30 days free no credit card cancel anytime

How alert escalation works

Three setup steps — then the chasing is Uptimia's job.

Step 12 minutes

Connect channels & teammates

Add the channels your team already uses, invite people by email, give each a role.

Alert channels
EmailSlackSMSWhatsApp+ 8 more
Invite teammate
sara@caldmont.com
role: editor · invitation email sent
Step 21 minute

Build a ladder once

Who gets paged first, who's next, how long to wait. Attach the policy to any monitors you like.

Step 1 · immediately
#ops-alerts · Slack + Email
Step 2 · after 5 min
On-call phone · SMS
Step 3 · after 15 min
Eng lead · SMS + PagerDuty
CancelAttach to 24 monitors →
Step 3automatic

Uptimia does the chasing

Confirmed outages climb the ladder until someone acknowledges. Recovery closes the loop with an all-clear.

#ops-alerts
Uptimia 14:32
⚠ Down — checkout.caldmont.com
HTTP 503confirmed 3 regionsacknowledge with one click ↓
Escalates in 5 min unless acknowledged

Also included

Full REST API

Manage monitors, contacts and team members from CI or scripts — v1 and v2 APIs, per-user keys.

POST /api/v2/users → 201 · role: editor · invite sent

Recovery notices

The all-clear goes to everyone who was paged — with the outage duration.

✓ recovered · down 31 min · sent to 4

Incident history

Every incident kept with its timeline — who was paged, who acknowledged, when it recovered.

#4128 · acknowledged 6 min · resolved

Public status pages

Tell customers what's happening — before they ask support.

status.yourdomain.com · live

Scheduled reports

Uptime and incident summaries by email, branded with your logo.

weekly · Monday 08:00 · PDF

One contact list for every monitor type

Uptime, SSL, heartbeat, DNS, API and transaction monitors all page the same contacts, ladders and teams — set up once.

www.caldmont.comUPTIME api.caldmont.comSSL db-backup · nightlyHEARTBEAT

What is an alert escalation policy?

An alert escalation policy is a rule that decides who is notified about an incident, in which order, and how long to wait for a response before alerting the next person. Alerts start small — a team channel, then the on-call phone, then a manager — and stop climbing the moment someone acknowledges.

Without a policy

All-at-once alerting

Incident
confirmed outage
one blast · instantly
Everyone
all recipients · all channels

Everybody hears about everything — the default for every monitor, and the fallback if a policy is removed.

With a policy

Escalation alerting

Incident
confirmed outage
no acknowledgement? next step
The ladder
step 1 → 2 → 3 · stops at the first acknowledgement

Alerts climb only while nobody responds — fewer interruptions, no outage left unanswered.

An example

A three-step escalation policy

Most incidents end at step 1; the rest climb until someone says "I've got it" — a bounded repeat keeps long outages from going quiet.

How escalations work in Uptimia →
StepWhenWho is pagedChannels
1immediately#ops-alerts + team emailSlackEmail
2+5 min, not acknowledgedon-call phoneSMSWhatsApp
3+15 min, not acknowledgedengineering leadSMSPagerDuty
↻every 30 min while downlast step repeats · max 3 roundsuntil acknowledged

Downtime alerts FAQ

01How do I get an alert when my website goes down?+
Add a monitor and pick your channels. Uptimia checks your site from 171+ locations, confirms outages from multiple regions, then alerts you on any of 12 channels — email, SMS, Slack, Microsoft Teams, Discord, Mattermost, Telegram, WhatsApp, PagerDuty, Twilio, webhooks and Atlassian Statuspage.
02What is an alert escalation policy?+
A reusable ladder that decides who is alerted, in which order, and how long to wait before paging the next person. A policy holds up to 10 steps. The editor offers waits from 5 minutes to 2 hours per step; through the API a step can wait anywhere from 1 minute to 24 hours. Either way there is an optional bounded repeat, and one policy attaches to any number of monitors, of any type.
03What happens if nobody responds to an alert?+
The ladder keeps climbing: each step waits its configured time, then pages the next person. After the last step an optional bounded repeat re-pages every N minutes, and a deleted or emptied policy falls back to alerting everyone at once.
04How does acknowledging an alert work?+
Every alert carries a signed link — one tap on "I've got it" acknowledges the incident, no login required. The escalation freezes, the incident records who acknowledged and when, and MTTA (mean time to acknowledge) shows on the incident and in its history. Read-only teammates can acknowledge too.
05Can email scanners accidentally acknowledge my alerts?+
No. Opening the link (what scanners do) only renders a confirmation page — only pressing the button on that page acknowledges.
06Does Uptimia make phone calls?+
Not today — there are no voice-call alerts. Uptimia sends SMS worldwide from its built-in pool or your own Twilio account, WhatsApp and Telegram ring like any personal message, and the PagerDuty integration triggers real PagerDuty incidents.
07Do you support on-call rotations?+
Ladders page fixed people and teams in order — they don't rotate by calendar. For shift-based on-call, point a ladder step at the PagerDuty integration and your rotation takes over; for teams without formal rotations, the ladder itself is enough.
08How do you prevent alert fatigue?+
Four mechanisms: outages are confirmed from multiple regions before anyone is paged; related failures merge into one grouped incident; per-person quiet hours hold pages until morning; maintenance windows and pause keep planned work silent.
09How many team members can I add?+
Up to 100 team seats on the largest plan; the 30-day free trial includes 50. Each member gets their own login and a role — admin, editor, read-only viewer, or a free billing-only seat.
10Which plans include escalation ladders?+
Escalation ladders — with incident grouping and one-tap acknowledgment — come with the Professional plan and above, in the plan price: never billed per seat, never a paid add-on. On Basic and the free plan, alerts still fire on your channels — they simply go to everyone at once. And a ladder you already built keeps firing even if your plan later changes; Uptimia never silently drops one.
11Do downtime alerts work for servers too, not just websites?+
Yes. The same contacts, channels and ladders serve every monitor type — ping, TCP-port and DNS checks from outside, and Uptimia Server Monitoring for CPU, memory and disk alerts from inside.

Never chase an outage alone again.

Connect your channels, build one ladder — and the next incident finds the right person by itself.

Set up downtime alerts →
30-day free trial 50 team seats on trial 12 alert channels No credit card
Alerting comes with every Uptimia monitor — channels on every plan, escalation ladders and acknowledgment with Professional and above.