uptime monitoring · every 30 seconds
Uptime monitoring for websites, APIs and servers, checked every 30 seconds
AlertPing wakes you before your customers notice. Checks run as often as every 30 seconds and every outage is confirmed from a second region before it alerts you, by SMS, email, Slack or webhook. No false alarms. No missed downtime.
checks every 30 seconds | confirmed from a second region | alerts in under 10 s
alertping ▸ check preview
simulated
▸ type a domain to watch a check and an alert play out
▸ simulation of 3 regions · US East · EU Central · EU East
▸ 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 (US East, EU Central, EU East). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: EU Central.
Simulation, not a measurement of your site: this preview runs entirely in your browser and the latencies are generated from the domain you typed. Real checks on your monitors run from our US East, EU Central and EU East regions.
30 s
between checks, from the Team plan up
3
regions must agree before you are paged
<10 s
from confirmed outage to your phone
how we page you
Three regions have to agree
A single failed probe never wakes anybody. The other regions re-check first, so a hiccup on one route is not a 3am phone call.
what a plan covers
SMS is in the price, not in credits
Email, Slack and webhook alerts are unlimited on every plan, SMS comes with a monthly allowance, and each plan hosts status pages. No credit packs, no per-message fee, no per-monitor math.
how setup works
One URL, no agent to install
Paste the address, choose where alerts go, and the first check runs from all three regions. No agent, no config file, nothing to deploy on your side.
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 the Team plan and up, and every 60 seconds on Starter.
02 · no false alarms
Only real outages page you
A failed probe triggers an instant re-check from the other regions. 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 own domain from Business up, 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 1,500 monitors depending on plan.
-
2
We check every 30 seconds from 3 regions
A failure triggers an immediate re-probe from the other regions. 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 sample 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
EU Central gets a connection timeout. No page yet: it could be a blip.
03:41:58
Second-region confirmation
US East and EU East 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 move? Watch a check and an alert 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. Invoices for every payment, DPA on request. See security.
alertping ▸ downtime cost calculator
$200,000
4 h
revenue at risk per year
$1,096
AlertPing Team plan: $348 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
$24 /mo
billed yearly, save 50%
- 20 monitors · 60s checks
- SMS, email, Slack, webhook
- 1 status page
- 3 team members
Most popular
Team
Product teams that own an SLA
$29 /mo
billed yearly, save 50%
- 100 monitors · 30s checks
- Escalation chains, on-call hours
- 300 SMS alerts a month
- 15 team members
Business
Agencies and multi-product companies
$94 /mo
billed yearly, save 50%
- 500 monitors · 30s checks
- SLA reports · CSV exports
- 1,000 SMS alerts a month
- Unlimited team members
Enterprise
Compliance, scale, procurement
$189 /mo
billed yearly, save 50%
- 1,500 monitors · 15s checks
- SLA reports · on-call escalation
- 3,000 SMS alerts a month
- Unlimited team members
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. US East, EU Central and EU East 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 an instant re-probe from the other regions. 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?
SMS on every plan and 30-second checks (from the Team plan up), second-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 a second region, alerts on every channel.