features · alerting
Downtime alerts that reach the person who can actually fix it
Downtime alerts are messages sent the moment your site fails a check. AlertPing sends them by SMS, email, Slack and webhook in under 10 seconds after a 3-region confirmation. SMS is included in every plan, no credit packs.
alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app 03:42
● DOWN api.acme-store.com: HTTP timeout confirmed from 3/3 regions (FRA, IAD, SIN). Incident #4812 opened.
sms · on-call: marcus
AlertPing: api.acme-store.com DOWN. Confirmed 3/3 regions 03:42. First fail: Frankfurt.
resolution alert · 03:43
● UP api.acme-store.com recovered after 94 s. Incident #4812 closed automatically.
escalation chains
If the first person sleeps through it, the second one won't
On Team plans and up, alerts follow a chain you define. Each step waits for an acknowledgement; no ack, next step fires. On-call hours decide who is step one at 3pm versus 3am, so the whole team is never paged for one incident.
t+0 s
Outage confirmed 3/3
FRA, IAD and SIN all agree. The chain starts.
step 1 · t+10 s
On-call engineer
SMS + Slack. On-call hours pick the right person for the time of day.
step 2 · no ack in 5 min
Backup contact
SMS + email to the secondary. The first engineer is re-paged too.
step 3 · no ack in 15 min
Whole team + webhook
Team Slack channel, engineering lead by SMS, webhook to your tooling. Voice calls on Enterprise.
the details
Every channel, and a record of every page
Alerts fire only after 3-of-3 regional confirmation, the same pipeline explained in how uptime monitoring works. That is why an AlertPing page is worth waking up for. And when the incident is over, your public status page already told customers, so nobody is waiting on you to tweet.
SMS in every plan
No credit packs, no per-message fees, from Starter at $19/mo up. Slack messages get missed at 3am; a text does not.
Email, Slack, webhook
Formatted Slack messages with the incident number, plain email, and a JSON webhook to drive your own runbooks.
On-call hours
Define who is first by hour and day. Weekend rotation, night shift, or one founder who takes everything: your call.
Resolution alerts
Three green probes in a row close the incident and notify everyone who was paged, with total downtime attached.
Alert log
Every page ever sent: channel, recipient, timestamp, acknowledgement. When someone asks "why did nobody get paged", the answer is one search away. Heartbeat misses from cron job monitoring land in the same log.
alerting questions
Asked before every switch
Is SMS really included, even on the cheapest plan?
Yes. Every plan from Starter up includes SMS alerts with no credit packs and no per-message fees, alongside email, Slack and webhooks.
How do escalation chains work?
You define ordered steps with wait times. Step one is paged first; if nobody acknowledges within the wait time, the next step fires. On-call hours decide who fills step one at any given time. Available on Team plans and up.
Will I get paged for a 5-second blip?
No. A single failed probe triggers instant re-checks from all three regions. An alert only fires when Frankfurt, Virginia and Singapore all confirm the failure, and a resolution alert follows as soon as three probes pass.
Get the alert that actually wakes you
SMS, email, Slack and webhook in under 10 seconds after 3-region confirmation. Escalation chains included on Team and up.