Built for real production teams
We’re not a vanity “status page.” We’re early signal, clean routing, and an audit trail of what actually happened.
Security & trust
You’re asking us to watch production. We take that seriously.
- Targets you ask us to monitor (hostnames, ports, URLs, expected strings).
- Per-probe results: latency, HTTP code, socket success/failure.
- Alert routing info: Discord webhook / channel, push subscription, email, escalation contacts.
- We do not resell outage data or publish your incident timeline as “marketing.”
- Alert flow is under your control. You decide who gets paged and how loud it should be.
- All traffic is encrypted in transit and stored in access-controlled systems at rest.
- Role-based access (RBAC) lets you give different visibility to different team members.
Plans & pricing
Start free. Scale to multi-region, multi-team monitoring. Billing only starts after activation.
Why teams switch to us
This is the part the on-call engineer cares about at 02:00.
“LasVegas is DOWN, Canada still UP” means degraded in one region, not global catastrophe. You can say: “Checkout is failing in US West only,” instead of “everything is down everywhere.” That cuts panic.
We include latency, HTTP code / socket failure, and which probe broke first. You can tell if it’s TLS handshake fail, rate-limit, DB timeout, or “network just imploded.” You don’t have to guess.
Per-monitor policy: “page me if any probe dies,” “page me if most are failing,” or “wake me only if all probes are out.” We respect that and route alerts accordingly.
Start time, who got notified, how long it stayed bad, and when it cleared — all timestamped. That’s your postmortem spine and (if you’re public) it’s what compliance is going to ask for.