Skip to content
All systems operational

Know your endpoints are up before your users do.

Run synthetic checks from multiple regions and get alerted the moment something breaks. Built for teams who treat uptime as a feature.

livenessprobe / checks
8 active
methodendpointlatency
GET/api/health42ms
POST/api/orders118ms
GET/v1/catalog154ms
GET/api/auth67ms
GET/v1/users/me89ms
POST/api/webhooks95ms
99.98% uptime / 30dpolling every 60s

Checks from 7 regions, worldwide.

Every check runs from the regions that matter to your users, so a regional outage never goes unnoticed.

us-ashburn42ms
us-sanjose67ms
eu-frankfurt118ms
sa-vinhedo221ms
af-johannesburg176ms
ap-singapore154ms
ap-sydney188ms

Everything you need to trust your uptime

Synthetic monitoring, alerting, and request control in one place.

Checks from 7 global regions

Probe your endpoints from distributed regions to catch regional outages and CDN issues before users report them.

us-ashburnus-sanjoseeu-frankfurtsa-vinhedoaf-johannesburgap-singaporeap-sydney

Alerts that wake you up

Email and Slack notifications the instant a check fails.

/api/orders is down5xx from eu-frankfurt
2s ago
/v1/catalog degradedlatency > 500ms
1m ago

Full request control

Custom headers, body, and assertions on every request.

assert: status == 200
headers: { Authorization: Bearer *** }

SSL & expiry tracking

Never let a certificate lapse silently again.

api.example.com
29d left
auth.example.com
84d left

Uptime history & trends

Rolling uptime per check, with regional breakdowns so you spot patterns.

99.98%last 90d

Incident timeline

See exactly when a check broke, for how long, and when it recovered.

14:02 /api/orders failed
14:04 alert sent
14:11 recovered (9m)

Webhooks & integrations

Pipe alerts into PagerDuty, Slack, Discord, or any HTTP endpoint.

SlackPagerDutyDiscordEmailWebhook

How it works

From signup to your first resolved incident in five steps.

  1. 01

    Add your endpoint

    Enter the URL and HTTP method. Attach headers, body, and auth so the check reaches the real thing.

  2. 02

    Set assertions

    Define what a healthy response looks like: status code, body match, latency ceiling.

  3. 03

    Choose regions & interval

    Pick which of the 7 regions run the probe and how often, down to every 60 seconds.

  4. 04

    Get alerted instantly

    The moment a check breaks an assertion, an alert lands in email or Slack in under a second.

  5. 05

    Track uptime & resolve

    Watch the uptime trend, follow the incident timeline, and confirm recovery when green returns.

99.98%Average uptime tracked
60sMinimum check interval
7Monitoring regions
<1sAlert delivery
Two minutes to green

Your first check, live before you finish this page.

No credit card, no sales call. Point it at an endpoint, pick your regions, and watch the status dot turn green.

livenessprobe / new-check
1
endpoint:api.example.com/health
2
regions:us-ashburn, eu-frankfurt, ap-singapore
3
interval:60s
200 OK from all regions