The right alert, at the right time, every time
Nodown confirms failures across multiple independent regions before alerting your team. No false positives. No alert fatigue. Just real incidents, delivered to wherever your team already works.
All 8 alert channels · Free on all plans · No credit card required
#incidents
just now
🔴 [DOWN] api.yourapp.com
503 Service Unavailable · 5/14 regions · 14:32 UTC
View monitor →
PagerDuty · Production API
just now
TRIGGER - api.yourapp.com is DOWN
Severity: critical · Service: Production API · Dedup: nodown-abc123
#incidents
8 min later
✅ [RECOVERED] api.yourapp.com
Incident duration: 8m 14s · Resolved at 14:40 UTC
Zero false positives - by design
A 3am alert that turns out to be a transient network blip is worse than no alert at all. It erodes trust in the system and conditions engineers to ignore or silence pages.
Nodown requires at least 3 of 14 independent global regions to confirm the same failure before any alert is sent. One failing check could be a routing blip between the probe and your server. Three independent regions reporting failure means real users are affected.
3+
regions must agree before alerting
<60s
mean time from failure to alert
~0
false positive alerts in production
14
independent global probe locations
How verification works
Threshold reached (3/5 failing) - alert dispatched
8 alert channels. All plans. No upsell.
Every integration is available on the free Starter plan. You can assign multiple channels to the same monitor for redundancy.
Slack
Post alerts to any channel via Incoming Webhook. No bot required.
Set up guide
Discord
Native webhook delivery to any Discord server channel.
Set up guide
PagerDuty
Open, resolve, and deduplicate incidents via Events API v2.
Set up guide
Microsoft Teams
Post formatted cards to any Teams channel via Incoming Webhook.
Set up guide
Telegram
Send alerts to any bot, group, or channel in Telegram.
Set up guide
HTML email alerts to any inbox - team aliases, personal, or ticketing systems.
Set up guide
SMS
Text message alerts for critical monitors. Works without internet.
Set up guide
Webhook
Custom JSON payload to any HTTP endpoint. Works with Zapier, n8n, Make.
Set up guideChoose which events trigger alerts
Not all events deserve the same urgency. Configure each alert channel to fire only for the event types that make sense for that channel - downtime pages PagerDuty, SSL warnings go to email.
-
Monitor down
Triggered when 3+ regions confirm the endpoint is unreachable or returning an error status code. This is the primary incident alert.
-
Monitor recovered
Sent when the monitor returns to healthy. Includes total incident duration so you have a complete record without leaving your channel.
-
SSL certificate expiring
Advance warning at 30, 14, and 7 days before your SSL certificate expires. Enough time to renew before users see a browser warning.
-
Slow response threshold
Alert when response time exceeds a threshold you set (e.g. > 2000ms). Useful for detecting performance degradation before it becomes an outage.
Alert routing example
payments.yourapp.com
api.yourapp.com
yourapp.com SSL
dashboard.yourapp.com
Built for teams that can't afford to miss an incident
Multiple channels per monitor
Assign more than one alert channel to a monitor. Critical services can page PagerDuty, post to Slack, and send SMS simultaneously.
Per-event filtering
Control which event types fire to each channel. Route downtime to PagerDuty, recovery to Slack, SSL warnings to email - all from one monitor.
On-call escalation
Pair Nodown with PagerDuty or OpsGenie to get full on-call rotation support, escalation policies, and acknowledgement tracking on top of our detection layer.
Recovery notifications
Every alert channel receives a recovery message with total incident duration. No manual cleanup - your channel shows the full incident lifecycle.
Alert history
Every alert sent is logged in your dashboard with payload details and delivery status. Review what was sent, when, and to which channels.
Webhook for custom logic
Send a structured JSON payload to any endpoint. Build custom notification pipelines, trigger runbooks, or fan out to tools Nodown doesn't natively support.
Maintenance windows
Schedule planned maintenance to automatically suppress alerts during deployments. No spurious pages when you're the one taking the service down.
Sub-minute alert delivery
From failure detection to alert delivery in under 60 seconds on Pro plans. Our alert pipeline is built for speed, not batch delivery.
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.