Know where it broke.
And why.
We watch your websites, servers and certificates around the clock. The alert says what failed. A follow-up note gives the likely cause.
Uses your Google account. By continuing you agree to the Terms of Use and Privacy Policy.
Only want to know if it's down right now? .
How it works
One outage, start to finish. Three failures in a row by default, seconds apart, other regions re-checking HTTP, TCP, SSL and UDP checks before the alert goes out, then the email: about a minute after the first failed check.
- Checked
Checked around the clock, from two clouds
Every 5 minutes on the free plan, as often as every 30 seconds on Business and MSP, from two independent clouds in four regions.
- Confirmed
Confirmed in about a minute
A blip is not an outage. A failed check is re-checked within seconds, and from our other regions for HTTP, TCP, SSL and UDP, so you hear about a minute after the first failure and never for a hiccup.
- Triaged
Triaged before you open your laptop
When it is real, the alert says where it broke, and a follow-up note gives the likely cause and what to check first. Then ask questions in the dashboard, or from Cursor and Claude.
How the triage works →
When something goes down, we tell you why.
Legacy monitors stop at “it's down”. Ours reads the error, the history and the related signals, then tells you the likely cause and what to check first.
- Triage that follows the alertA 502 at 3 AM: the alert says where it failed, and a follow-up note gives what changed and the likely cause. A first look, not a verdict, and often straight at the problem.Free: 3 a month, plus 25 starter uses in your first 14 days. Paid plans: a larger monthly allowance.
- An assistant that knows your incidentsAsk about your monitors and incidents in plain words. It can propose changes; nothing changes until you confirm.Free: 5 questions a month, plus the same 25 starter uses. Paid plans: a larger monthly allowance.
- In your IDE: MCP for Cursor and ClaudeConnect Cursor, Claude or any MCP client with an API token. Ask what went down, pause a check during a deploy or add a new one, without leaving the editor.Paid plans: a monthly allowance. Free: 300 calls in your first 14 days.
Why did api.acme.com go down at 3 AM, and what should I check first?What went down this week, and why?Pause the marketing site while we deploy.Add an SSL check for acme.com and warn me a week before it expires.
How the triage works →Connect Cursor or Claude →Compare plans →
Deployed on independent networks
Our checks do not just run from different regions. They run on two entirely independent cloud networks, with separate data centres, backbones and upstream providers. If one provider has an outage, the other keeps your checks and alerts running.
- Two independent cloudsDual-provider isolation: separate data centres, networks and upstream providers on each side, so one provider's bad day cannot silence your alerts.
- Four regions on three continentsChecks run from four regions, each from more than one data centre, so a single site going dark does not blind us.
- Confirmed in about a minuteThree failures in a row by default, seconds apart, with our other regions re-checking HTTP, TCP, SSL and UDP before the alert goes out.
- No credit cardNothing to enter, nothing to cancel.
- Live in about a minuteEmail, password, one address. All 25 free monitors are yours at once; alerts switch on when you confirm your email.
- No data sales, no ad profilingOur own analytics use no cookies, and your information is never sold.
- The free plan stays free25 monitors at 5-minute checks, no trial clock, commercial use allowed.