Know the second your service goes down
Nodown runs checks every minute from 14 regions worldwide. When at least 3 independent regions confirm a failure, your team is alerted before your users notice.
10 monitors free forever · No credit card required
Incident open · dashboard.yourapp.com · 503 Service Unavailable · 4 regions confirming · 7 min ago
- 14
- global monitoring regions
- 30s
- minimum check interval
- 3+
- regions must confirm failure
- <60s
- mean time to alert
How Nodown monitors your services
A monitor runs continuously, without gaps, with built-in false-positive protection.
Scheduled checks
Every 30 to 60 seconds, Nodown sends an HTTP request, TCP handshake, DNS query, or SSL probe to your endpoint from each active region independently.
Multi-region verification
A single failure is not enough. At least 3 of 14 regions must report the same failure before Nodown considers the endpoint down - eliminating ISP blips and false alerts.
Instant alert
Once the failure threshold is crossed, your configured channels (Slack, SMS, PagerDuty, etc.) are notified within seconds with the endpoint, failure reason, and detection time.
Auto-recovery
When the endpoint returns healthy responses across regions, Nodown sends a recovery notification including the total incident duration for your incident records.
Every type of endpoint, covered
Nodown goes beyond simple HTTP pings - monitor the full stack from app layer to certificate expiry.
HTTP / HTTPS
Check that any URL responds with the expected HTTP status code. Optionally validate response body content, custom headers, or authentication.
- GET /health
- POST /api/ping
- HEAD /
TCP Port
Verify that a TCP port is open and accepting connections. Works for databases, message queues, game servers, or any non-HTTP service.
- db.host:5432
- redis.host:6379
- smtp.host:25
DNS
Check that your domain resolves to the expected IP addresses. Detect DNS misconfigurations, propagation failures, and hijacking attempts.
- yourapp.com → A
- mail → MX
- www → CNAME
SSL Certificate
Track your certificate expiry date and get alerted 30, 14, and 7 days before it expires - before your users see a browser warning.
- Expiry countdown
- Chain validation
- Auto-renewal check
14 regions. True global coverage.
A monitor that only checks from one location can be fooled by regional outages, BGP issues, or ISP-level failures that only affect some of your users. Nodown checks from 14 independent regions so a failure report means a real failure - visible to real users around the world.
Our alert threshold requires 3+ regions to agree before paging anyone. This eliminates nearly all false positives without adding meaningful delay to real incident detection.
- North America (US East, US West, Canada)
- Europe (France, Germany, UK, Netherlands)
- Asia Pacific (Japan, Singapore, Australia)
- South America (Brazil)
- Middle East & Africa (UAE)
Live region status
US East
142ms
US West
198ms
Canada
167ms
France
38ms
Germany
44ms
UK
52ms
Netherlands
41ms
Japan
312ms
Singapore
278ms
Australia
348ms
Brazil
223ms
UAE
188ms
3 regions reporting failure → incident confirmed → alert sent
api.yourapp.com
Response time · last 24 h
142ms avg
↓ 18ms vs last week
99.98%
Uptime (30d)
62ms
P50 response
2
Incidents (30d)
Response time tracking and uptime analytics
Every check result is stored. Nodown builds a complete picture of your endpoint's performance - average response times by region, uptime percentage over 7, 30, and 90 days, and a searchable incident history.
- Response time trends across all 14 regions, updated every check cycle
- Uptime percentage for 7d, 30d, and 90d windows, per monitor
- Incident history with start time, duration, failure reason, and recovery timestamp
- Scheduled maintenance windows that suppress alerts and update your status page automatically
Everything a production monitoring setup needs
1-minute check intervals
Checks fire every minute on all plans, from 14 global regions in parallel. Failures confirmed by 3+ regions trigger an alert within 60 seconds.
Team monitoring
Invite your team, assign monitors to alert channels, and give different team members access to different dashboards with role-based permissions.
Custom request headers
Add Authorization headers, user-agent strings, or API keys to HTTP monitors so Nodown can check authenticated endpoints and APIs that require credentials.
Body content assertion
Check that a keyword is present in the response body - not just that the server returns 200 OK. Catch broken deploys that serve an empty page with a 200 status.
SSL certificate monitoring
Get email or Slack alerts 30, 14, and 7 days before your SSL certificate expires. Never let a forgotten cert renew take down your HTTPS site.
Alert filtering by event type
Choose which events fire to which channels. Some teams want Slack for everything; others want only PagerDuty for downtime and email for SSL warnings.
Maintenance windows
Schedule maintenance windows to suppress alerts during planned deployments. Your status page shows "Under maintenance" automatically to users.
Uptime SLA reporting
Export uptime data for customer SLA reports. Track 99.9% vs 99.99% uptime targets per monitor and share results without giving dashboard access.
Get alerts wherever your team works
All 8 alert channels included on every plan.
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.