We built the monitor
we kept wishing existed
Nodown checks from 14 global regions every minute. A failure requires at least 3 independent regions to confirm it before anyone gets paged. That single rule is the product.
Free forever · No credit card required
- 14
- global monitoring regions
- 1 min
- check interval on all plans
- 3+
- regions must confirm failure
- <60s
- mean time to alert
Alert fatigue is a monitoring failure
Most uptime monitors fire an alert the moment a single check fails from a single location. That sounds right, but in practice it means a transient network blip — a packet dropped in Frankfurt, a DNS hiccup in Tokyo — pages the on-call engineer at 2am for an issue that resolved itself before the phone finished ringing.
Teams respond rationally: they mute the channels. They add delay. They tune thresholds until the noise stops. And then a real incident happens and nobody gets paged.
Nodown takes a different position. A failure is confirmed only when at least 3 of our 14 independently-operated regions report the same problem at the same time. A transient blip in one region does not cross that threshold. An actual outage does, and the alert fires within 60 seconds.
How failure confirmation works
Check cycle 1 — 1 region reports failure
Check cycle 2 — 2 regions report failure
Check cycle 3 — 3 regions confirm
Incident confirmed · Alert sent
Single-region failures never reach the alert threshold.
Three constraints we test every feature against
Each one shapes what we build, how we build it, and what we decide not to ship.
Confirmed failures only
We will not alert your team until multiple independent regions agree. Speed of detection matters. So does accuracy. We optimize for both and will not trade one for the other.
Real global coverage
A monitor that checks from one location misses regional outages. Nodown checks from 14 regions across North America, Europe, Asia Pacific, South America, and the Middle East. Your users are everywhere. So are we.
Built for teams, not one engineer
On-call rotation, escalation policies, and status pages are first-class features. Monitoring that only works for the person who set it up is not production monitoring.
Detection, alerting, and communication in one tool
When something breaks, you need to detect it, reach the right person, and keep your users informed — without switching between separate tools.
-
Monitoring
HTTP, TCP, DNS, SSL, and cron heartbeat checks every minute from 14 regions.
-
Alerting
Slack, email, SMS, PagerDuty, Discord, and webhooks. On-call schedules and escalation policies included.
-
Status pages
Custom-domain pages that update the moment a monitor changes state, no manual post required.
-
Analytics
P50/P95/P99 response times, 90-day uptime history, and SLA reporting per monitor.
Stop worrying about downtime.
Create your first monitors on the free plan, add alert channels, and publish a status page when your team is ready. No credit card required.