Staging environment · payments run in test mode only · content marked “pending” awaits business information

Service

Website & API health checks

Your homepage answering isn’t the same as your application working. Website & API checks request the exact URL you choose, such as a health endpoint, a public API or a key page, and check that the response is correct, not just that the server answered.

What each check verifies

  • HTTP status: a code or range such as 200, 200,204 or 200-299
  • Response time: fail when the answer takes longer than your limit, for example 2000 ms
  • Page text: a stable phrase that must appear in the response
  • JSON value: a field and its expected value, e.g. /status = "ok" or /services/0/healthy = true
  • Trusted certificate: optional per check; certificate problems are always reported by SSL monitoring

Example

URLGET https://example.com/api/health
Expected status200
Response limit2000 ms
JSON field/status = "ok"

This check passes when HTTP 200 arrives within two seconds and the response contains {"status":"ok"}. Add as many endpoints per domain as your plan allows; each has its own status, history and alerts.

What the statuses mean

Healthy
The status, text, JSON and speed assertions all passed.
Degraded
The server answered, but something was wrong: unexpected status, missing text, a different JSON value, too slow, or the body could not be read. This is reported separately from being unreachable.
Down
No usable HTTP response: DNS failure, connection refused, timeout or TLS handshake failure.
Unknown
No result for three check intervals. Missing measurements are never reported as healthy or as downtime.

Schedules, history and alerts

Checks run as often as every 10 seconds (up to once an hour) on our servers, so they continue while you are signed out. Results are kept for your plan’s retention period, with a successful-check rate. When a check goes Down or Degraded you are alerted immediately, with reminders 5 minutes, 15 minutes, 5 hours and 24 hours later until it passes again, then one recovery alert.

Safe by design

Checks are anonymous GET or HEAD requests: no cookies, credentials or POST requests, so they never change your data. Redirects are followed only if you enable it, and every destination is validated again. Up to 256 KiB of a response is inspected and never stored. Only public websites on ports 80 and 443 can be checked, after you verify ownership of the domain; private and internal addresses are always blocked. Don’t put passwords or tokens in a check URL.

See plans Create an account