Uptime Monitoring, Status Pages & On-Call | Hyperping

Showing 25 of 26 from the live probe.

• List monitors

  Paginated monitors in the project. Optional status filter (up/down/paused/ssl_expiring).

• Get monitor

  Fetch a single monitor by its UUID.

• Create monitor

  Create a new monitor. Requires name+url; add "port" for port checks, "dns_*" for DNS checks.

• Update monitor

  Patch a monitor. Pass only fields you want to change; others are preserved.

• Pause monitor

  Pause a monitor — no checks run and no alerts fire. Same as update_monitor with paused=true.

• Resume monitor

  Resume a paused monitor. Same as update_monitor with paused=false.

• Search monitors by name

  Case-insensitive substring search across monitor names and URLs.

• Status summary

  Up/down/paused counts plus a list of currently down monitors with the timestamp they went down.

• List outages

  Paginated list of outages in the project. Filter by status, type, or search term.

• Get outage

  Fetch a single outage by UUID, including acknowledgements, description, and root cause.

• Get outage timeline

  Full activity timeline for an outage: detection, cross-region verification, alert dispatches, acknowledgement, resolution.

• Get outages for a monitor

  Paginated list of outages scoped to one monitor. Convenience wrapper around list_outages.

• List recent alerts

  Alert notifications (up/down transitions) over a date range. Defaults to last 30 days.

• Get uptime (SLA) stats

  Uptime percentage over a date window, aggregated and optionally per day/hour/week/month.

• Get response time

  Response time latency trend over a date window.

• Get MTTR per monitor

  Mean time to resolve (MTTR) per monitor over a date window, in seconds.

• Get MTTA per monitor

  Mean time to acknowledge (MTTA) per monitor over a date window, in seconds.

• Get monitor anomalies

  Anomaly-detection output for a single monitor (flapping, latency spikes, etc.).

• Get monitor HTTP logs

  Recent HTTP probe logs for a monitor, paginated. Useful to diagnose recent check failures.

• List on-call schedules

  All on-call schedules in the project. Each entry typically includes rotation config and current on-call.

• Get on-call schedule

  One schedule by UUID with full rotation detail and the linked escalation policies.

• List escalation policies

  All escalation policies in the project. Use to find which monitors route alerts where.

• Get escalation policy

  One policy by UUID. Reveals step sequence, linked schedules, and contact channels.

• List team members

  Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

• List integrations

  All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).