uptime monitoring · every 30 seconds
Uptime monitoring that wakes you before your customers notice
AlertPing checks your sites, APIs and ports every 30 seconds and confirms every outage from three regions before it alerts you, by SMS, email, Slack or webhook. No false alarms. No missed downtime.
12,000+ endpoints under watch | 38M checks a day | alerts in under 10 s
alertping ▸ run check
live
▸ type a domain and run a real-feel check
▸ probes from 3 regions · FRA · IAD · SIN
▸ waiting…▌
queued probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (FRA, IAD, SIN). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: Frankfurt.
99.99%
our alert pipeline uptime, last quarter
38M
checks run every day across 3 regions
<10 s
from confirmed outage to your phone
“Our old tool paged me at 3am for blips that fixed themselves in a minute. AlertPing only pages when all three regions agree it's really down. I sleep again.”
SRE lead, payments SaaS
“I run 40 client sites. One dashboard, one status page per client, and SMS that does not cost extra credits. The math was not close.”
Founder, web agency
“We sell a 99.9% SLA. AlertPing's reports are what we attach to the quarterly review. Our biggest customer stopped asking for proof.”
CTO, logistics platform
why teams switch
Downtime you hear about first, alerts you can trust
01 · know first, not last
A check every 30 seconds, not every 5 minutes
Most tools on starter plans check every 1 to 5 minutes. A 5-minute interval means your checkout can be dead for 4 minutes 59 seconds before anyone even looks. Our website monitoring tool probes every 30 seconds on every paid plan.
02 · no false alarms
Only real outages page you
A failed probe triggers instant re-checks from Frankfurt, Virginia and Singapore. You get paged when 3 of 3 agree, not when one route hiccups.
03 · every channel included
SMS is not an add-on
Slack messages get missed at 3am. Every plan includes SMS, email, Slack and webhook downtime alerts, with escalation chains so the right person wakes up.
04 · show customers you're up
A status page that answers support tickets for you
Every plan hosts a branded public status page on your domain, updated automatically from your checks. During an incident, customers check the page instead of filing tickets.
how it works
Three steps between an outage and your phone
No agent to install, nothing to deploy. Add a URL and the first check runs before you finish reading this section. The full lifecycle is on how uptime monitoring works.
-
1
Add your URL, IP or port
HTTP, ping, TCP/UDP port, SSL or cron heartbeat. 20 to unlimited monitors depending on plan.
-
2
We check every 30 seconds from 3 regions
A failure triggers immediate re-probes from Frankfurt, Virginia and Singapore. 3 of 3 must agree.
-
3
The right person is alerted in under 10 seconds
SMS, email, Slack, webhook. Escalation chains and on-call hours decide who wakes up, and your status page updates itself.
anatomy of an incident
What 94 seconds of downtime looks like in AlertPing
A real incident timeline, second by second. This is the trace you review after the fact, and the report your incident communication is built on.
alertping ▸ incident #4812 · api.acme-store.com
resolved · 94 s
03:41:52
First failed probe
Frankfurt gets a connection timeout. No page yet: it could be a blip.
03:41:58
3-region confirmation
Virginia and Singapore re-probe instantly. 3 of 3 agree: it's down.
03:42:04
On-call paged
SMS + Slack fire. Status page flips to "investigating" automatically.
03:43:26
Recovery confirmed
Three green probes in a row. Resolution alert sent, incident log written.
Want to see it live? Check your website status in the interactive demo.
for the team that answers for uptime
Downtime is a line item. Monitoring is a rounding error.
Industry estimates put enterprise downtime at $5,600 per minute. You do not need enterprise numbers for the math to work: for a store doing $200,000 a month, one lost checkout hour costs more than a year of AlertPing. What a CTO actually buys:
- SLA reports for customer contracts. Monthly uptime per endpoint, exportable, ready for the quarterly review.
- Escalation that matches your org. On-call hours, backup contacts, and a chain that stops at the person who can actually fix it.
- Procurement without friction. Invoicing and PO on Enterprise, security review included, DPA on request. See security.
alertping ▸ downtime cost calculator
$200,000
4 h
revenue at risk per year
$1,096
AlertPing Team plan: $564 a year. Catching one incident an hour earlier usually pays for it.
pricing
Flat plans. SMS included. No per-monitor math.
Starter
Side projects and single products
$15 /mo
billed yearly
- 20 monitors · 60s checks
- SMS, email, Slack, webhook
- 1 status page
- 3 team members
Most popular
Team
Product teams that own an SLA
$47 /mo
billed yearly
- 100 monitors · 30s checks
- Escalation chains, on-call hours
- 5 branded status pages
- 15 team members
Business
Agencies and multi-product companies
$151 /mo
billed yearly
- 500 monitors · 30s checks
- SLA reports · full API
- 20 status pages + custom domain
- Unlimited team · priority support
Enterprise
Compliance, scale, procurement
Custom
annual invoicing
- Unlimited monitors · 15s checks
- SSO/SAML · roles & audit log
- 99.99% SLA · voice-call alerts
- Security review · dedicated CSM
Full plan details on the uptime monitoring pricing page. Switching? See how we compare to Pingdom and UptimeRobot.
you might be thinking…
The questions every on-call engineer asks first
More in the full uptime monitoring FAQ, including what counts as downtime and how checks are billed.
Do I need to install an agent?
No. AlertPing checks from the outside, the way your users reach you. Add a URL, IP or port and the first check runs within seconds.
Will I get false alarms at 3am?
A single failed probe never pages you. Frankfurt, Virginia and Singapore must all confirm the failure within seconds of each other before an alert fires.
Is SMS really included?
Yes. Every plan includes SMS alerts with no credit packs and no per-message fees, alongside email, Slack and webhooks.
What happens when a check fails?
The failing region triggers instant re-probes from the other two. On 3-of-3 confirmation we alert your escalation chain and flip your status page, typically in under 10 seconds.
Can I monitor internal ports and services?
Anything reachable from the public internet: HTTPS, ping, SMTP, databases on exposed ports, custom TCP/UDP. Cron heartbeats cover jobs behind your firewall.
How is this different from UptimeRobot or Pingdom?
30-second checks and SMS on every plan, 3-region confirmation before any page, and flat per-plan pricing instead of per-monitor fees. Honest side-by-side tables are on our compare pages.
Know the second your site goes down
Checks every 30 seconds, confirmed from 3 regions, alerts on every channel. Running in under a minute.