Operational FAQ

Quick answers to the operational questions our support team hears most often. Regions, false positives, phone numbers, rate limits, and check behavior, all in one place.

From which regions do checks run?

Checks run from 18 regions across 7 global zones: North America, South America, Europe, Asia, Australia, the Middle East, and Africa. See the full list in Datacenter regions.

Each check runs from one region at a time, rotating through the regions you selected for the monitor. The probes run on a mix of hosting providers (AWS, Scaleway, DigitalOcean) for redundancy.

How does Hyperping avoid false positives?

Every failure is double-checked before you hear about it. When a check fails, Hyperping immediately re-runs it from every other region you selected, and only confirmed failures open an outage and trigger alerts.

The probes also run on a mix of hosting providers (AWS, Scaleway, DigitalOcean), so an isolated network blip at one provider never becomes a fake incident.

What phone numbers do alert calls come from?

If you have a European phone number, calls come from +31 970 10 25 72 04. For US and non-EU countries, calls come from (424) 325-7650 (+14243257650).

Save both numbers as a contact named Hyperping so on-call engineers recognize the call and their phone does not silence it. Phone calls are enabled through an escalation policy, see the phone call integration for setup and throttling details.

How often can I ping a healthcheck?

Healthcheck endpoints have two rate limits:

• Per IP: you cannot ping from the same IP more than 300 times per minute.
• Per check: you cannot ping a single check more than 10 times per minute.

Each healthcheck gets a unique endpoint in the format https://hc.hyperping.io/TOKEN_ID. Hit it with a HEAD, GET or POST request at the end of your job. See Healthchecks for schedules and grace periods.

# Ping your healthcheck at the end of a job (HEAD, GET or POST)
curl https://hc.hyperping.io/TOKEN_ID

What SSL errors are detected?

SSL monitoring is enabled by default for all HTTPS monitors, with a reminder 30 days before expiry. Hyperping automatically detects and reports these certificate issues:

• Expired: the certificate expired and is no longer valid.
• Revoked: the certificate was revoked by the issuer and is no longer trusted.
• Self-signed: the certificate is not issued by a trusted authority.
• No Common Name: the certificate is missing a Common Name field.
• Incomplete Chain: intermediates may be missing from the certificate chain.
• Common Name Mismatch: the certificate's Common Name does not match the domain.

Certificates are checked daily, and you can trigger a manual refresh from the monitor's SSL section after renewing. See SSL monitoring.

What are the API rate limits?

By default, every project is limited to 800 API requests per hour, calculated on a rolling window. Each project has its own separate quota, tracked by API token, with a per-IP fallback when no valid token is provided.

When you exceed the limit, the API returns 429 Too Many Requests with a retry-after header, and every response includes a ratelimit header so you can track your usage. Paid plans can request higher limits from support. Full details in API rate limits.

What are the browser check limits?

Each browser check runs a Playwright script in headless Chromium with a 2-minute global timeout per run. Individual tests inherit Playwright's 30-second default timeout, which you can override with test.setTimeout.

Double check is enabled by default: a failed run is immediately retried from a different region before an outage opens. Every run keeps its logs, screenshots, video, and trace indefinitely. Long flows are usually better split into separate checks, one per critical path. See Browser checks.

Next steps