Hyperping documentation
Monitor services, route alerts, and keep customers informed.
Quickstart guide
Create your first monitor and start collecting uptime data in a few minutes.
Monitor an endpointCreate an HTTP monitor through the API and start collecting uptime data.
cURLcurl -X POST https://api.hyperping.io/v1/monitors \
-H "Authorization: Bearer ${API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"name": "Website",
"url": "https://example.com"
}'Browse the docs
Choose the part of Hyperping you want to configure.
MonitoringUptime, browser checks, cron jobs, SSL, DNS, and response times.Server monitoringInstall the agent and inspect CPU, memory, disk, and network metrics.Incident responseConfigure alerts, notification channels, and escalation policies.Status pagesPublish service health, incidents, and planned maintenance.API referenceAutomate monitors, incidents, maintenance windows, and reports.IntegrationsConnect Slack, Teams, PagerDuty, webhooks, Terraform, MCP, and other tools.
Choose the right monitor
Start with the signal that best describes failure.
- You need to check a public website or API from multiple regions.
- Status codes, response time, SSL, or response content tell you whether it is healthy.
Best for: Websites, public APIs, and externally reachable services.
Read the guide