Uptime monitoring that earns the alert
Checked every minute, confirmed before anyone is woken, and correlated across the sites that share a server. Start with a check right now — no account needed.
The free run checks that the URL answers, and how fast. Continuous checks start when the site is monitored.
What an uptime check actually proves
A 200 response is not the same as a working site. A monitor that only pings the front page reports health while checkout is broken, and pages you for a single dropped packet. This one asserts on what came back, and confirms a failure before it calls it an outage.
- Reachability
DNS, connection, TLS handshake and status code, timed separately.
- Content assertion
A page can return 200 and still be an error page. We check what it contained.
- Confirmation before alerting
A bad check is retried immediately and must fail repeatedly to count.
- Shared-server correlation
Six sites on one origin failing together is one incident, not six alerts.
- Response time
Degradation is reported before it becomes downtime.
What a result looks like
Two incidents, both outside business hours.
Detected in 60s, confirmed and alerted in 90s.
Up from 240ms since the release on the 14th.
Each incident keeps what it saw: the status code, the response body, the failure mode and the timeline from detection to recovery. There is no single availability figure to argue about, because the evidence sits underneath it.
A check tells you about today. Monitoring tells you at 04:00.
Outages do not schedule themselves for working hours, and the expensive ones are quiet: a certificate that expired overnight, an origin that started refusing connections while the cached homepage kept serving. Continuous checks catch those in the minute they happen and say which region saw it first.
Common questions
- Is this the same engine as the paid monitoring?
- Yes — the same checks, run the same way. The difference is that monitoring repeats them on a schedule and keeps the history, which is what turns a number into a trend and a trend into an alert.
- Does testing my site slow it down or change anything?
- No. Everything is read from the outside, the way a visitor arrives — no agent, no script on your pages, nothing written. Our requests identify themselves so you can recognise them in your own logs.
- How is this different from a ping monitor?
- A ping proves a machine answered. We assert on what it answered with, confirm the failure before calling it one, and correlate across your estate — if six of your sites sit behind the same server, one server problem arrives as one incident rather than six alerts at 04:00.
- Will it wake me for a blip?
- Not by default. A failed check is retried immediately and has to keep failing before anything is raised. Quiet hours, maintenance windows and a 72-hour learning period on new sites suppress the rest — and everything suppressed is listed with the reason it was held, so the quiet is auditable.
Related tests
A free test is a snapshot. Monitoring is the product.