Uptime · Response time · Multi-region
Every service you run, checked on its own interval, with the last hour of results next to it. A webhook goes out the second one of those rows changes colour.
Per-service intervals — every 5 minutes on Free, from every minute on Pro.
The dashboard
Status, latency, uptime and the regions it was checked from — with the counts across the top, so you can tell at a glance whether today is a normal day.
sample data
The moment a service flips between online, degraded and offline, a webhook goes out with what changed — to Slack, an incident tool, or anything that accepts a POST.
Status and response time are recorded on every run, so the log viewer and per-service analytics answer “when did this start?” instead of “it looks fine now.”
Results are kept per region — us-east, us-west, eu-central, asia-pacific — so a real outage looks different from one region routing badly.
Every service is scoped to the account that created it, sessions expire on their own, and a check will not reach a private address.
How it works
Paste the endpoint, name it, and choose how often it should be checked — anywhere from every minute to once a day.
A background scheduler checks each service on its own interval and writes down the status, the response time and the region.
Only a status change reaches you. Everything else waits in the log and the analytics until you go looking for it.
Pricing
Every plan runs the same checks, keeps the same history and sends the same webhooks. What changes is how many services you can watch, how often, and how far back you can look.
$0/mo
One or two things you would rather not find out about late.
$9/mo
A production stack, checked every minute from four regions.
$29/mo
More services, and a longer record to look back through.
Start free — you can move between plans at any time from Settings → Plan & Billing.
Add a service, set an interval, point the webhook somewhere you actually read.