Hyperping · Rate Limits

Hyperping Rate Limits

The Hyperping REST API is authenticated per project with a Bearer API key. Hyperping does not publish specific numeric request-per-minute limits for the management API in its public documentation; usage capacity is governed primarily by plan quotas (number of monitors, status pages, browser checks, and seats) rather than by a published API throttle. Specific per-endpoint request limits are not reconciled in this artifact.

Hyperping Rate Limits is the machine-readable rate-limit profile for Hyperping on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, monitors, status_pages, and seats.

The profile also includes 3 backoff/retry policies defined and response codes documented for unauthorized, forbidden, and throttled.

Tagged areas include Uptime Monitoring, Status Pages, Incident Management, Observability, and On-Call.

4 Limits Throttle: 429
Uptime MonitoringStatus PagesIncident ManagementObservabilityOn-CallRate LimitingQuotasThrottling

Limits

API Requests project
requests
see provider documentation
No published numeric request-per-minute limit for the management API; confirm with support.
Monitors account
monitors
per plan (20 Free / 50 Essentials / 100 Pro / 1000 Business)
Plan-based capacity quota, not a request throttle.
Status Pages account
status_pages
per plan (1 / 1 / 3 / 10)
Plan-based capacity quota.
Seats account
seats
per plan (1 / 2 / 5 / 15)
Additional Business seats billed at $12/month each.

Policies

Authentication
Every request requires Authorization Bearer with a project API key. Missing or invalid keys return 401; Read-only keys hitting write operations return 403.
Plan-Based Capacity
Usage is bounded by plan quotas on monitors, status pages, browser checks, and seats rather than a published API request throttle.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.

Sources