Not just uptime monitoring
Three things separate this from a checker that pings a URL: we confirm from two other continents before we wake you, we understand what depends on what, and we stop escalating the moment the problem resolves itself.
Confirmation, not a single observation
One probe failing tells you about one probe, and most single failures are the network in between rather than your site. A failure is only an outage once probes on two other continents agree.
The states we use
Every state carries a shape as well as a colour.
- UP Healthy. Answering as expected.
- CLEAR On no blocklist we check.
- VALID The certificate checks out.
- DOWN Confirmed from two other continents.
- EXPIRING A threshold crossed. Not an outage.
- PAUSED Deliberately not checked.
- NO DATA Our probe is unreachable. We know nothing, and we say so.
NO DATA means the problem was at our end: a probe we could not reach, so nobody looked at your site. We will not guess what we did not see, and we will never wake you for it.
What depends on what
One alert, not thirty
Tell us a site depends on its server. When the server goes down you get one message about the server, not one for every site on it. Suppression and grouping stay separate concepts: a group rolls status up, a dependency stops noise going out.
Escalation that cancels itself
Text yourself immediately, Slack the team after two minutes, email the owner after forty-five. If it recovers before the escalation, the later messages never go out: they are cancelled, not sent and retracted.
What we watch
Your mail server going quiet or your IP landing on a blocklist costs you as much as a down homepage, and usually takes longer to notice.
- HTTPS pages, APIs, keyword matching
- SMTP incoming email, handshake and STARTTLS
- DNS resolution and record changes
- Email blocklists your sending IP and domain
- SSL/TLS certificate expiry
- Ping reachability and packet loss
- TCP port any host and port, keyword matching
- Heartbeat cron jobs that stop
- Domain blocklists pi-hole and AdGuard block your site
- WebSocket the socket opens, keyword matching
Ask an assistant, not a dashboard
Paste one address into Claude, or any assistant that speaks the Model Context Protocol, and ask it what is down and why, or tell it to add a monitor.
Anything our API can do, it can do. It reads your monitors, outages, uptime, maintenance windows and status pages, adds and changes and deletes monitors and groups, schedules and cancels windows, and publishes or unpublishes what a status page shows. It acts as you and never beyond what your role allows: one organisation per connection, chosen when you approve it, and you can disconnect it at any time.
Watch something today
Free for five monitors, for as long as you like, confirmed from another continent like everything else here. No card required.
Create a free account