Uptime monitoring.
No false alarms.

Uptime monitoring checks from outside your infrastructure, on a schedule, that your websites, APIs and services answer and answer correctly, and alerts your team when they stop. Its history gives you the uptime percentage you report against an SLA. Hyperping runs these checks every 30 seconds from 17 regions. Read the uptime monitoring guide for the full picture.

A monitor sends a request to your URL, host or port at a fixed interval, from the regions you select in turn, and compares the answer with what you expect: a status code, a piece of text, a DNS record, an open port. When a check fails, Hyperping reruns it at once from your other regions and opens an outage only if they fail too. See create a monitor.

Every 30 seconds on paid plans and every 5 minutes on the Free plan, with shorter intervals on Business. Browser checks run every 5 minutes, and cron jobs are checked against the schedule you give them. See pricing.

Websites and APIs over HTTP, with keyword checks on the response, ping (ICMP) and TCP ports, DNS records, SSL certificates and domain expiry, cron jobs through healthchecks, multi-step flows with Playwright browser checks, and servers with a lightweight agent. See the monitoring docs.

Every failure is rechecked from your other regions before an outage opens, so a network blip between one probe and your server never pages anyone. An alert delay can also ignore blips shorter than the minutes you set, maintenance windows mute planned work, and the expected status code accepts endpoints that legitimately answer 401 or 404. See false positives.

Most production services aim for 99.9%, about 8 hours and 46 minutes of downtime a year. Critical services aim for 99.99%, about 53 minutes a year. Choose the target from your SLA and from what an hour of downtime costs you, then convert it with the SLA calculator.

By email, SMS, phone call, Slack, Microsoft Teams, Google Chat, Discord, Telegram, PagerDuty, Opsgenie or webhooks. Escalation policies and on-call schedules send each alert to whoever is on duty and move it on if nobody acknowledges.

Yes. The Free plan includes 20 monitors checked every 5 minutes, HTTP, port, ping and keyword checks, one server agent and one basic status page, with no credit card required. Paid plans start with a 14-day free trial. See free uptime monitoring.

Yes. Status pages read their state from your monitors, so a confirmed outage shows on the page without anyone updating it, and visitors see the uptime history of each service. Paid plans add custom domains, subscribers and, from Pro, private pages. See status pages.

Uptime monitoring checks from the outside whether a service answers correctly, the way a customer would see it. APM instruments your code to measure latency, errors and database time inside the application. Uptime monitoring tells you that something is down, APM helps explain why, and most teams run both.