What is uptime monitoring? Everything teams ask us

A monitoring service like AlertPing requests your site the way a real visitor would, every 30 seconds, from Frankfurt, Virginia and Singapore. While everything answers correctly it stays silent. The moment your site stops answering, it confirms the failure and alerts your team, so you hear about downtime from a machine in seconds instead of from a customer an hour later. The full lifecycle is on how uptime monitoring works.

No. AlertPing checks from the outside, the way your users reach you. There is nothing to install, no config to maintain, no agent to patch. Add a URL, IP or port and the first check runs within seconds.

HTTP and HTTPS endpoints with keyword and JSON assertions, ping (ICMP), TCP and UDP ports, SSL certificates (expiry and chain, warned 30, 14, 7 and 1 days out), and cron jobs via heartbeats. Websites, APIs, mail servers, databases on exposed ports, scheduled backups.

Anything reachable from the public internet: HTTPS, ping, SMTP, databases on exposed ports, custom TCP/UDP services. For jobs that run entirely behind your firewall, cron heartbeats flip the direction: your job pings us when it runs, and we alert you when it goes quiet.

Every 30 seconds on Team and Business, every 60 seconds on Starter, every 15 seconds on Enterprise. Every check runs from 3 regions: Frankfurt, Virginia and Singapore. Most tools on comparable plans check every 1 to 5 minutes.

A probe fails when the request times out after 30 seconds, returns an HTTP 5xx, misses a keyword or JSON assertion you defined, or presents an invalid SSL certificate. Downtime is declared only when all 3 regions confirm the failure, and it ends when 3 consecutive probes succeed.

A single failed probe never pages you. The failing region triggers instant re-probes from the other two, and an alert fires only when 3 of 3 regions agree within seconds of each other. A hiccup on one route between one network and your server stays a hiccup, not a page.

The failing region triggers instant re-probes from the other two regions. On 3-of-3 confirmation AlertPing alerts your escalation chain by SMS, email, Slack and webhook, and flips your status page to investigating, typically in under 10 seconds. When 3 probes in a row succeed again, everyone gets the recovery notice and the incident log is written.

Yes. Every plan includes SMS alerts with no credit packs and no per-message fees, alongside email, Slack and webhooks. Slack messages get missed at 3am; a text does not. Enterprise adds voice calls. Details on downtime alerts.

Yes. Plans include 3 to unlimited team members, and on Team and up you get escalation chains with on-call hours: the primary on-call gets the SMS first, a backup is paged if nobody acknowledges, and the whole channel sees it in Slack. Alerts route to whoever is on duty, not to one inbox.

Every plan hosts at least one branded status page, updated automatically from your checks: no manual incident posting required. Business and up serve it on your own domain, like status.yourdomain.com, and subscribers get incident updates by email. During an outage, customers check the page instead of filing tickets.

Flat plans: Starter $19 a month, Team $59, Business $189, Enterprise custom, with 20% off billed yearly. The price covers everything: checks, all alert channels including SMS, and status pages. No per-monitor fees, no per-alert fees. Full plan grid on uptime monitoring pricing.

Three things: 30-second checks and SMS alerts on every plan instead of paid add-ons, 3-region confirmation before any page instead of single-location alerts, and flat per-plan pricing instead of per-monitor fees. Honest side-by-side tables: Pingdom alternative and UptimeRobot alternative.

Minutes, not days. There is no agent and no code change: paste in the URLs, IPs and ports you already watch, pick alert channels, and the first checks run immediately. Most teams run AlertPing alongside their old tool for a week, watch it catch the same incidents faster, then switch off the old one.