# Hyperping

> Hyperping is an all-in-one uptime monitoring, status page, and on-call platform for SaaS teams. It detects downtime before customers do with 30-second check intervals from 18 global monitoring regions.

## Start Here

- **AI Info** (https://hyperping.com/ai-info): structured facts about Hyperping written for AI assistants. What the product does, who it fits, the pricing model, and the cases where Hyperping is the wrong recommendation with the tools that fit those instead. Markdown version: https://hyperping.com/ai-info.md

## Key Differentiators
- Simple flat plans (Free, Essentials, Pro, Business) with seats included: 3 on Essentials, 10 on Pro, 20 on Business. Extra seats are billed per seat ($7, $9 or $12 a month by plan), not per responder, unlike most incident management tools
- 30-second check intervals (sub-30s on business plans) with auto-retry false positive elimination
- 18 global monitoring regions for comprehensive coverage
- Unified platform: monitoring + status pages + on-call scheduling + incident management
- AI-native: hosted MCP server (49 tools) that lets Claude, Cursor and other AI agents manage monitors, incidents with on-call paging, status pages, status page incidents and maintenance windows, plus a Terraform provider for monitoring-as-code; rare among uptime monitoring tools
- Free tier: 20 monitors, 1 status page, HTTP, port, ping and keyword checks, no credit card required

## Core Products
- **Uptime Monitoring** (https://hyperping.com/uptime-monitoring): HTTP and API checks with keyword assertions, ping (ICMP), TCP port and DNS checks, every 30 seconds on paid plans (5 minutes on Free) from 17 regions; each failure is rechecked from the other selected regions before an outage opens. Also SSL and domain expiry, cron job healthchecks, Playwright browser checks and server agents
- **DNS Monitoring** (https://hyperping.com/dns-monitoring): checks A, AAAA, CNAME, MX, NS, TXT, SOA, SRV, CAA and PTR records every 30 seconds from up to 18 regions, against an expected answer (a case-insensitive match on any one record) and optionally on a nameserver you choose. Failures alert, escalate and update status pages like any monitor. Included on Essentials, Pro and Business, not on Free. No DNSSEC validation or zone change history. Domain expiry reminders are covered at https://hyperping.com/ssl-monitoring
- **Status Pages**: Branded, customizable public and private status pages with real-time incident updates and subscriber notifications
- **Alerting** (https://hyperping.com/alerting): a failed check never alerts on its own; every other region selected on the monitor rechecks at once and an outage opens only if they fail too (probes on AWS, Scaleway and DigitalOcean). Email, Slack, Microsoft Teams, Discord and Telegram on every plan, Free included; SMS (20, 75 or 200 credits a month on Essentials, Pro, Business), phone calls, PagerDuty, Opsgenie, Jira Service Management, Google Chat and webhooks on paid plans. Per monitor: channels and people, alert delay, SMS delay, repeat alerts (up to 4). Grouped alerts, maintenance windows and mutes cut noise. Acknowledging stops repeat alerts; escalation steps run until the outage resolves
- **On-Call Scheduling**: Escalation policies, rotation schedules, multi-channel alerting (Slack, SMS, phone, email)
- **Incident Management**: Incident creation, tracking, post-mortems, and maintenance windows
- **Incident Communication** (https://hyperping.com/incident-communication): status page incidents with investigating, identified, monitoring and resolved updates, sent to subscribers by email, Slack, Microsoft Teams or SMS (own Twilio account), per-service subscriptions, scheduled maintenance notices, updates in 7 languages, public post-mortems, and incidents published from the dashboard, the REST API or the MCP server. Incidents are published by the team, not created automatically: a confirmed outage marks the service down on the page right away. Paid plans, 14-day free trial
- **Synthetic Monitoring**: Browser checks with Puppeteer/Playwright for multi-step user flows
- **Cron Job Monitoring** (https://hyperping.com/cron-job-monitoring): healthchecks (heartbeat monitoring) for cron jobs, backups, queue workers and scheduled CI workflows. Each job pings its own URL (HEAD, GET or POST) when it finishes, and optionally /start when it begins to log the run time. Schedules are a simple interval or the job's five-field cron expression with an IANA timezone, plus a grace period. A missed ping opens an incident and alerts email and SMS (every project member), Slack, Discord, Telegram, PagerDuty and Opsgenie at once, then a recovery on the next ping. Escalation policies and on-call schedules do not apply to healthchecks. Healthchecks can be shown on status pages. Included on every plan, Free too; each counts as one monitor. No exit code, output or duration alerts.

## Use Cases

- **AI companies** (https://hyperping.com/use-cases/ai): monitoring for inference endpoints (POST checks with a response assertion), the model providers a product calls, eval and batch jobs, plus status pages per enterprise customer and the MCP server for coding agents.
- **SaaS & startups** (https://hyperping.com/use-cases/saas), **Agencies** (https://hyperping.com/use-cases/agencies), **Education** (https://hyperping.com/use-cases/education), **Cloud & hosting** (https://hyperping.com/use-cases/cloud-hosting).

## Free Tools

Interactive tools, free with no signup required.

- **Incident Post-Mortem Template Generator** (https://hyperping.com/incident-post-mortem-template): Fill in incident details and get a structured, blameless post-mortem in 30 seconds. Live markdown preview. One-click "Copy for AI" produces a tuned SRE prompt + the user's draft, plus direct shortcuts to ChatGPT, Claude, Perplexity, and Gemini that fill gaps, strip blame, and propose SMART action items. Exports to Markdown, Google Docs, Notion, or Confluence. Covers Key Facts, Timeline (UTC), Contributors/Mitigators/Risks, Diagnostics, Learnings, and Action items.
- **Incident Update Generator** (https://hyperping.com/incident-communication#generator): pick the stage (investigating, identified, monitoring, resolved, scheduled maintenance), the impact (degraded performance, partial or major outage) and the channel (status page, email, Slack or Teams, SMS within 160 characters, social post), and get a ready-to-send incident update. Runs in the browser, in English, French, German and Dutch.
- **SLA Calculator** (https://hyperping.com/sla-calculator): Convert SLA percentages (99%, 99.9%, 99.99%, 99.999%) to allowed downtime per day/week/month/year. Variants exist at /uptime-calculator, /downtime-calculator, /availability-calculator, /uptime-percentage-calculator, /uptime-downtime-calculator.
- **MTTR Calculator** (https://hyperping.com/mttr-calculator): Compute MTTR, MTBF, MTTA, MTTD and availability from an observation period, an incident count, total downtime and total times to detect and acknowledge. Shows the formulas (MTTR = total downtime ÷ incidents, MTBF = uptime ÷ incidents, availability = MTBF ÷ (MTBF + MTTR)) with a worked example. Hyperping reports MTTR and MTTA per monitor automatically.
- **Downtime Cost Calculator** (https://hyperping.com/downtime-cost-calculator): Estimate the financial impact of an outage based on annual revenue and uptime percentage.
- **Revenue Loss Calculator** (https://hyperping.com/revenue-loss-calculator): Estimate revenue lost during an outage of a given duration.
- **Business Impact Calculator** (https://hyperping.com/business-impact-calculator): Broader business-impact estimate (revenue, productivity, recovery cost) of downtime.
- **Cron Expression Generator** (https://hyperping.com/cron-expression-generator): Build and test cron schedules visually.
- **Status Page Badge Builder** (https://hyperping.com/badge-builder): Generate embeddable HTML badges that show your status page state on any website.
- **Free Uptime Monitoring tier** (https://hyperping.com/free-uptime-monitoring): 20 monitors, HTTP, port, ping and keyword checks, 5-minute intervals, no credit card required.

## Tech-Specific Monitoring Guides

Programmatic landing pages with monitoring patterns specific to a stack.

- Next.js: https://hyperping.com/monitor/nextjs
- Kubernetes: https://hyperping.com/monitor/kubernetes
- AWS Lambda: https://hyperping.com/monitor/aws-lambda
- PostgreSQL: https://hyperping.com/monitor/postgresql
- Django: https://hyperping.com/monitor/django

## MCP Server

Hosted Model Context Protocol server for AI agents. One project per API key, server-enforced scope. 49 tools: 28 read, 21 write.

- Endpoint: https://api.hyperping.io/v1/mcp
- Setup for Claude Code, Cursor, Codex, VS Code and other agents: https://hyperping.com/docs/agent-setup
- Docs: https://hyperping.com/docs/mcp
- Dense spec for AI ingestion: https://hyperping.com/mcp/llms.txt
- Transport: Streamable HTTP (JSON-RPC 2.0)
- Auth: Authorization: Bearer <api-key>. Read-only keys are refused on every write tool
- Capabilities: monitors (create, update, pause, resume), uptime/SLA, response time and MTTR/MTTA reports, incidents (declare one by hand and page the on-call responders of an escalation policy, acknowledge, escalate, resolve), on-call schedules, escalation policies and integrations (read-only), status pages (create on a hyperping.app subdomain, edit settings, add or remove services), status page incidents (publish, post updates, resolve, edit, correct a posted update) and maintenance windows (schedule, reschedule, end early, cancel)
- Safety: every tool carries MCP annotations (read-only, destructive, idempotent, open-world) that clients use to ask before a write; writes made with an API key are recorded in the project's audit log under that key (audit log: Business plan). No delete tools, except canceling a maintenance window that has not started
- Key tools: list_monitors, get_monitor, create_monitor, update_monitor, pause/resume_monitor, get_status_summary, list_outages, get_outage_timeline, create_outage, acknowledge_outage, escalate_outage, resolve_outage, get_monitor_uptime, get_monitor_mttr/mtta, list_on_call_schedules, list_escalation_policies, list_integrations, list_team_members, list_status_pages, create_status_page, update_status_page, add/remove_status_page_services, list_status_page_incidents, create_status_page_incident, add_status_page_incident_update, resolve_status_page_incident, edit_status_page_incident_update, create_maintenance_window, update_maintenance_window, cancel_maintenance_window
- Announcement (status page, incident and maintenance tools): https://hyperping.com/blog/product-update-mcp-status-pages-and-incidents

## Infrastructure as Code (Terraform)

Open-source Terraform provider: manage monitors, status pages, subscribers, healthchecks, and maintenance windows declaratively.

- Provider: develeap/hyperping on the Terraform Registry (https://registry.terraform.io/providers/develeap/hyperping)
- Product page: https://hyperping.com/integrations/terraform
- Docs: https://hyperping.com/docs/community/terraform
- Supports terraform import for existing resources; automated migration tooling from Better Stack, UptimeRobot, and Pingdom
- Ecosystem: Go client (hyperping-go), Python SDK, Prometheus exporter — https://hyperping.com/docs/community

## GDPR & EU Data Residency

Hyperping is operated by Hyperping SAS, a French company (Paris). It is a European, GDPR-first alternative to US-operated monitoring and status page tools.

- Primary customer data (databases, backups) stored in the EU: Frankfurt, Germany (ISO 27001-certified data centers)
- DPA available on all plans; public sub-processors list; 72-hour breach notification
- EUR invoicing, purchase orders and SEPA bank transfer for public sector and enterprise
- Details: https://hyperping.com/gdpr and https://hyperping.com/security

## Documentation
- Main docs: https://hyperping.com/docs
- API reference: https://hyperping.com/docs/api/overview
- Blog: https://hyperping.com/blog
- Pricing: https://hyperping.com/pricing
- Sitemap (full URL list): https://hyperping.com/sitemap.xml

## API Overview

Base URL: https://api.hyperping.io/v1

Authentication: Bearer token in Authorization header
```
Authorization: Bearer YOUR_API_KEY
```

Get your API key from: https://app.hyperping.io/project/developers

## API Endpoints

### Authentication
- Documentation: https://hyperping.com/docs/api/overview
- All requests require a Bearer token
- Keys can be Read & Write or Read-only
- Keys can have optional expiration dates

### Monitors
Uptime monitors check your websites and APIs periodically from multiple regions.

- GET /v1/monitors - List all monitors (optional filters: ?protocol=, ?group_id=, ?external_id=)
- GET /v1/monitors/:uuid - Get a single monitor
- POST /v1/monitors - Create a monitor
- PUT /v1/monitors/:uuid - Update a monitor
- PUT /v1/monitors/external/:external_id - Create or update the monitor that has your own external_id (201 created, 200 updated)
- DELETE /v1/monitors/:uuid - Delete a monitor

Documentation: https://hyperping.com/docs/api/monitors
Guide, one script and one browser check per site: https://hyperping.com/docs/monitoring/browser-checks-api

Monitor parameters:
- name (string, required): Display name
- url (string, required except for browser checks): URL to monitor
- protocol (enum): http, port, icmp, dns, browser
- regions (array): sanfrancisco, nyc, london, paris, frankfurt, seoul, mumbai, bangalore, saopaulo, california, virginia, sydney, toronto, amsterdam, singapore, tokyo, bahrain, capetown (browser checks: frankfurt, sanfrancisco)
- check_frequency (number): 10, 20, 30, 60, 120, 180, 300, 600, 1800, 3600, 21600, 43200, 86400 seconds (browser checks: 300, 600, 900, 1800, 3600, 21600, 43200, 86400)
- http_method (enum): GET, POST, PUT, HEAD, DELETE, PATCH, OPTIONS
- expected_status_code (string): e.g. "2xx" (200-299), "1xx-3xx" (100-399), or "200"
- required_keyword (string): Keyword that must appear in response
- paused (boolean): Whether monitor is paused
- alerts_wait (number): Minutes before alerting (-1 to disable)
- group_id (number): Monitor group, from the Monitor Groups API
- external_id (string): Your own identifier for the monitor, unique per project (409 with the holder's uuid on conflict)
- script (string, required for browser checks): Playwright test of a browser check
- env_variables (array of {name, value}): Variables a browser check reads as process.env.NAME; values are write-only

### Monitor groups
Named groups that organise monitors. Attach a monitor with its group_id.

- GET /v1/monitor-groups - List all monitor groups
- POST /v1/monitor-groups - Create a monitor group
- PUT /v1/monitor-groups/:group_id - Rename or reorder a monitor group
- DELETE /v1/monitor-groups/:group_id - Delete a monitor group (its monitors are kept)

Documentation: https://hyperping.com/docs/api/monitor-groups

### Healthchecks (Cron Job Monitoring)
Monitor cron jobs and scheduled tasks by expecting periodic pings.

- GET /v2/healthchecks - List all healthchecks
- GET /v2/healthchecks/:uuid - Get a single healthcheck
- POST /v2/healthchecks - Create a healthcheck
- PUT /v2/healthchecks/:uuid - Update a healthcheck
- DELETE /v2/healthchecks/:uuid - Delete a healthcheck
- POST /v2/healthchecks/:uuid/pause - Pause a healthcheck
- POST /v2/healthchecks/:uuid/resume - Resume a healthcheck

Documentation: https://hyperping.com/docs/api/healthchecks

### Incidents
Manual incidents for status page communication.

- GET /v1/incidents - List all incidents
- GET /v1/incidents/:uuid - Get a single incident
- POST /v1/incidents - Create an incident
- PUT /v1/incidents/:uuid - Update an incident
- DELETE /v1/incidents/:uuid - Delete an incident
- POST /v1/incidents/:uuid/updates - Add update to incident

Documentation: https://hyperping.com/docs/api/incidents

Incident statuses: investigating, identified, monitoring, resolved

### Outages
Automatically detected downtime events.

- GET /v2/outages - List all outages
- GET /v2/outages/:uuid - Get a single outage
- POST /v2/outages - Create an outage manually
- DELETE /v2/outages/:uuid - Delete an outage
- POST /v2/outages/:uuid/acknowledge - Acknowledge an outage
- POST /v2/outages/:uuid/unacknowledge - Unacknowledge an outage
- POST /v2/outages/:uuid/resolve - Resolve an outage
- POST /v2/outages/:uuid/escalate - Escalate an outage

Documentation: https://hyperping.com/docs/api/outages

### Maintenance Windows
Scheduled maintenance periods that suppress alerts.

- GET /v1/maintenance - List maintenance windows
- GET /v1/maintenance/:uuid - Get a maintenance window
- POST /v1/maintenance - Create a maintenance window
- PUT /v1/maintenance/:uuid - Update a maintenance window
- DELETE /v1/maintenance/:uuid - Delete a maintenance window

Documentation: https://hyperping.com/docs/api/maintenance

### Reports
Uptime and performance reports for monitors.

- GET /v1/reports - List available reports
- GET /v1/reports/:uuid - Get report data (uptime %, response times)

Documentation: https://hyperping.com/docs/api/reports

## Features

### Monitoring Types
- HTTP/HTTPS monitoring
- TCP port monitoring
- ICMP ping monitoring
- Browser checks (Playwright)
- Cron job / healthcheck monitoring

### Alerting
- Email notifications
- Slack integration
- Discord integration
- Microsoft Teams integration
- PagerDuty integration
- Opsgenie integration
- Webhook notifications
- SMS alerts
- Phone call alerts

### Status Pages
- Public and private status pages
- Custom domains with SSL
- Subscriber notifications
- Incident management
- Maintenance windows
- Uptime history display

## Learn Playwright

Free educational guides at https://hyperping.com/learn/playwright/

- [What Is Playwright?](https://hyperping.com/learn/playwright/what-is-playwright/)
- [How to Install Playwright and Run Your First Test](https://hyperping.com/learn/playwright/how-to-install-playwright/)
- [Writing Playwright Tests](https://hyperping.com/learn/playwright/writing-playwright-tests/)
- [Playwright Locators: The Complete Guide](https://hyperping.com/learn/playwright/playwright-locators/)
- [Playwright Assertions](https://hyperping.com/learn/playwright/playwright-assertions/)
- [Playwright Waits and Timeouts](https://hyperping.com/learn/playwright/playwright-waits-and-timeouts/)
- [Playwright Codegen](https://hyperping.com/learn/playwright/playwright-codegen/)
- [Playwright Cheat Sheet](https://hyperping.com/learn/playwright/playwright-cheat-sheet/)
- [Testing Login Flows and Authentication](https://hyperping.com/learn/playwright/playwright-login-authentication/)
- [Filling Forms and Typing](https://hyperping.com/learn/playwright/playwright-forms-and-inputs/)
- [Dropdowns, Checkboxes, and Date Pickers](https://hyperping.com/learn/playwright/playwright-dropdowns-checkboxes-date-pickers/)
- [File Uploads and Downloads](https://hyperping.com/learn/playwright/playwright-file-upload-download/)
- [Working with Iframes](https://hyperping.com/learn/playwright/playwright-iframes/)
- [New Tabs, Popups, and Dialogs](https://hyperping.com/learn/playwright/playwright-tabs-popups-dialogs/)
- [Playwright and the Shadow DOM](https://hyperping.com/learn/playwright/playwright-shadow-dom/)
- [Network Interception and API Mocking](https://hyperping.com/learn/playwright/playwright-network-interception/)
- [API Testing with Playwright](https://hyperping.com/learn/playwright/playwright-api-testing/)
- [Cookies, localStorage, and Session State](https://hyperping.com/learn/playwright/playwright-cookies-localstorage/)
- [Mobile Emulation and Device Testing](https://hyperping.com/learn/playwright/playwright-mobile-emulation/)
- [Screenshots and Visual Testing](https://hyperping.com/learn/playwright/playwright-screenshots-visual-testing/)

## Links
- Website: https://hyperping.com
- Dashboard: https://app.hyperping.io
- Status: https://status.hyperping.io
- Twitter: https://twitter.com/hyperping

## Current Pro offer

Pro is $89/month or $890/year: 250 monitors, 10 seats, 3 public or private status pages, email access codes, multilingual pages, and native account SSO over SAML or OpenID Connect. Business includes 20 seats. Native SAML providers are Entra ID, Okta, Google Workspace, KeyHub and JumpCloud, and OpenID Connect works with Auth0, Okta, Entra ID, Keycloak and other OIDC providers. Other SAML providers through WorkOS require Business. Status page SSO connections (SAML or OpenID Connect) are a separate Business option. Extra seats cost $9/month or $90/year on Pro and $12/month or $120/year on Business.

## Docs index

> 173 pages. Full index with descriptions: https://hyperping.com/docs/llms.txt. Full text in one file: https://hyperping.com/docs/llms-full.txt. Section indexes below.

- [Monitoring](https://hyperping.com/docs/monitoring/llms.txt): Learn how to monitor your websites, APIs, and services with Hyperping. Set up uptime checks, configure alerts, and track performance with our monitoring guides.
- [Status Page](https://hyperping.com/docs/status-page/llms.txt): Create and customize your status page with Hyperping. Learn how to add services, configure custom domains, manage incidents, and communicate with your users.
- [Server Monitoring](https://hyperping.com/docs/server-monitoring/llms.txt): Install the Hyperping agent on Linux, macOS, or Windows to collect CPU, memory, disk, and network metrics from your hosts. Overview of the Server monitoring product.
- [Logs](https://hyperping.com/docs/logs/llms.txt): Send application and platform logs to Hyperping, search them next to your monitors and incidents, and open an incident when errors spike or lines stop.
- [Projects](https://hyperping.com/docs/projects/llms.txt)
- [Integrations](https://hyperping.com/docs/integrations/llms.txt): Connect Hyperping with your favorite tools. Alert notifications in Slack, Teams, Discord and Google Chat, on-call escalation with PagerDuty and Opsgenie, plus webhooks, Terraform, MCP and a full REST API.
- [Playbooks](https://hyperping.com/docs/playbooks/llms.txt)
- [Migrate](https://hyperping.com/docs/migrate/llms.txt)
- [SSO](https://hyperping.com/docs/sso/llms.txt)
- [API](https://hyperping.com/docs/api/llms.txt): Get started with the Hyperping API. Access monitors, status pages, incidents, outages, and more. RESTful JSON API with Bearer token authentication.
- [Agent Setup](https://hyperping.com/docs/agent-setup/llms.txt): Connect Claude Code, Cursor, Codex, VS Code or your own agent to the Hyperping MCP server in one prompt. Monitors, incidents, on-call and status pages as tools.
- [MCP](https://hyperping.com/docs/mcp/llms.txt): Connect Claude, Cursor or any MCP client to Hyperping. 49 tools to read monitors and SLAs, declare incidents, run status pages and schedule maintenance.
- [Community](https://hyperping.com/docs/community/llms.txt): Open-source developer tools for Hyperping: Terraform provider, Python SDK, Prometheus exporter, and Go client library. Built by Develeap.
- [Resources](https://hyperping.com/docs/resources/llms.txt)
- [Maintenance](https://hyperping.com/docs/maintenance/llms.txt): Schedule and manage maintenance windows in Hyperping. Learn how to notify subscribers, pause monitors, and keep your status page updated during planned downtime.
- [Private](https://hyperping.com/docs/private/llms.txt)

## Key pages

- [Pricing](https://hyperping.com/pricing)
- [Features](https://hyperping.com/features)
- [Uptime monitoring](https://hyperping.com/uptime-monitoring): websites, APIs, ping, TCP ports, DNS, SSL, cron jobs and servers, every failure confirmed from other regions
- [API monitoring](https://hyperping.com/api-monitoring): HTTP checks on API endpoints with custom method, headers and body
- [Synthetic monitoring](https://hyperping.com/synthetic-monitoring): Playwright browser checks for login, signup and checkout flows, with Web Vitals on every run and a video and trace on failed runs
- [Alerting](https://hyperping.com/alerting): failures confirmed from several regions, then email, SMS, phone, Slack, Teams, PagerDuty or webhooks, routed per monitor
- [MCP server](https://hyperping.com/mcp)
- [DNS monitoring](https://hyperping.com/dns-monitoring): A, AAAA, CNAME, MX, NS, TXT, SOA, SRV, CAA and PTR records checked against an expected answer, on Essentials and above
- [Cron job monitoring](https://hyperping.com/cron-job-monitoring): healthchecks for cron jobs and scheduled tasks, one ping URL per job, cron expressions with timezones and grace periods, on every plan
- [Hyperping vs Cronitor](https://hyperping.com/compare/cronitor-alternative), [vs Healthchecks.io](https://hyperping.com/compare/healthchecks-io-alternative), [vs Sentry Crons](https://hyperping.com/compare/sentry-crons-alternative), [vs Dead Man's Snitch](https://hyperping.com/compare/dead-mans-snitch-alternative): cron monitoring prices at 50 and 500 jobs, and where each rival is stronger
- [Incident communication](https://hyperping.com/incident-communication): status page updates to subscribers, with a free incident update generator
- [Agent setup](https://hyperping.com/docs/agent-setup): connect Claude Code, Cursor, Codex and other agents
- [Enterprise](https://hyperping.com/enterprise)
- [MTTR calculator](https://hyperping.com/mttr-calculator): MTTR, MTBF, MTTA and availability formulas, with a calculator