---
title: "Monitoring Documentation"
description: "Learn how to monitor your websites, APIs, and services with Hyperping. Set up uptime checks, configure alerts, and track performance with our monitoring guides."
url: https://hyperping.com/docs/monitoring
---

> Documentation index
> Section index: https://hyperping.com/docs/monitoring/llms.txt
> Full docs index: https://hyperping.com/docs/llms.txt

# What is Hyperping?

Hyperping is an [uptime monitoring](https://hyperping.com/uptime-monitoring) and status page platform. It checks your websites, APIs and servers around the clock from 18 regions worldwide, alerts the right person the moment something breaks, and keeps your users informed through a status page you control.

> **Set up your first monitor in under 2 minutes**
>
> Follow the [getting started guide](https://hyperping.com/docs/monitoring/getting-started) to create a monitor and wire up alerts. Free plan, no credit card required.

![Hyperping dashboard interface](https://hyperping.com/static/dashboard-2026-7545b9e193e40ce1f9443d91a09a801e.webp)

## How a check works

Every monitor runs on a simple loop, built to catch real outages and ignore network noise:

1.  A check runs from your regions
    
    Every 30 seconds by default, your monitor is queued and a server in one of your selected [regions](https://hyperping.com/docs/monitoring/datacenter-regions) runs the check: status code, response time, SSL, and any assertion you configured.
    
2.  Failures are double-checked
    
    If the check fails, Hyperping immediately re-runs it from every other region you selected. A single server having a bad moment never pages you.
    
3.  An outage opens and alerts go out
    
    Confirmed failures open an outage and notify your channels: email, Slack, SMS, phone calls, PagerDuty, webhooks and [more](https://hyperping.com/docs/projects/notification-channels). [Escalation policies](https://hyperping.com/docs/monitoring/escalation-policies) decide who gets paged, in what order.
    
4.  Recovery is confirmed
    
    When your service responds again, the outage resolves and the same channels get the all-clear, with the outage duration and logs kept for review.
    

> **No false positives**
>
> Checks run from a mix of hosting providers (AWS, Scaleway, DigitalOcean) across 18 regions. Multi-region double-checks and provider redundancy mean an isolated network blip never becomes a fake incident. See [false positives](https://hyperping.com/docs/monitoring/false-positives) for the full confirmation flow and the settings you can tune.

## Monitor anything

Uptime is more than a 200 on your homepage. Each check type has its own guide:

[

HTTP & API→

Status codes, redirects, custom headers and request bodies.

](https://hyperping.com/docs/monitoring/create-monitor)[

Keyword monitoring→

Assert the response body contains the content you expect.

](https://hyperping.com/docs/monitoring/keyword-monitoring)[

Ping & port→

ICMP reachability and TCP port checks for any service.

](https://hyperping.com/docs/monitoring/ping-port)[

DNS→

Validate records and catch propagation issues early.

](https://hyperping.com/docs/monitoring/dns)[

SSL certificates→

Expiration alerts and certificate error detection, built in.

](https://hyperping.com/docs/monitoring/ssl)[

Browser checks→

Playwright scripts for logins, checkouts and full user flows.

](https://hyperping.com/docs/monitoring/browser-checks)[

Healthchecks→

Cron jobs and scheduled tasks that must never fail silently.

](https://hyperping.com/docs/monitoring/healthchecks)[

Server monitoring→

CPU, memory, disk and network from a lightweight agent.

](https://hyperping.com/docs/server-monitoring)

## Create your first monitor

Use the dashboard, the REST API, or Terraform. They all create the same monitor:

```bash
curl -X POST https://api.hyperping.io/v1/monitors \
  -H "Authorization: Bearer ${API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Website",
    "url": "https://acme.com",
    "protocol": "http",
    "check_frequency": 30,
    "regions": ["paris", "frankfurt", "amsterdam", "london"]
  }'
```

**Response201 Created**

```json
{
  "name": "Website",
  "url": "https://acme.com",
  "paused": false,
  "regions": ["paris", "frankfurt", "amsterdam", "london"],
  "http_method": "GET",
  "check_frequency": 30,
  "uuid": "mon_3GhAQMYGEQuyUH",
  "status": "up",
  "ssl_expiration": 90,
  "alerts_wait": 0
}
```

Grab an API key from your dashboard settings, then see the [Monitors API](https://hyperping.com/docs/api/monitors) for every available field, or the [Terraform provider](https://hyperping.com/docs/community/terraform) to manage monitoring as code.

## What should you monitor?

Everything your users depend on deserves its own monitor. The usual starting point:

-   **Your main website** - https://acme.com
-   **Your dashboard** - https://app.acme.com
-   **Your API** - https://api.acme.com

These are usually hosted differently, so each one deserves its own monitor. From there, add what would hurt if it silently broke: static assets, third-party dependencies like your payment provider, individual microservices, and scheduled jobs via [healthchecks](https://hyperping.com/docs/monitoring/healthchecks).

## When something breaks

Detection is half the job. Hyperping also handles who gets paged and what your users see:

[

Escalation policies→

Route alerts in order, with delays, until resolved.

](https://hyperping.com/docs/monitoring/escalation-policies)[

On-call schedules→

Page whoever is on shift, across rotations and timezones.

](https://hyperping.com/docs/monitoring/on-call)[

Status pages→

Publish incidents automatically and notify your subscribers.

](https://hyperping.com/docs/status-page/create-status-page)

## Next steps

[

Getting started→

Create your first monitor and wire up alerts in 2 minutes.

](https://hyperping.com/docs/monitoring/getting-started)[

Notification channels→

Connect Slack, Teams, SMS, phone calls, PagerDuty and more.

](https://hyperping.com/docs/projects/notification-channels)[

Create a status page→

A branded status page on your own domain, live in minutes.

](https://hyperping.com/docs/status-page/create-status-page)[

MCP server→

Query your monitoring from Claude, Cursor or any MCP client.

](https://hyperping.com/docs/mcp)

[Getting started →](https://hyperping.com/docs/monitoring/getting-started)

  

[](https://x.com/hyperping)[](https://www.linkedin.com/company/hyperping)

© 2026 Hyperping