How to Set Up Downtime Alerts: Get Notified the Moment Your Site Goes Down

Monitoring without alerting is pointless. You can have the most comprehensive uptime checks in the world, but if no one knows when they fail, downtime continues undetected. Downtime alerts are the bridge between detection and response — the mechanism that converts a failed check into an actionable notification.

This guide covers how to configure downtime alerts that are reliable, reach the right people, and don't generate so much noise they start getting ignored.

Why Alert Configuration Matters

Most website owners who have experienced a significant outage have a story that starts the same way: "We didn't know for [hours/until a customer called/until the next morning]."

The gap between when downtime starts and when you're notified is called detection time — and it's the largest component of your mean time to recovery (MTTR). A well-configured alert setup means detection time is under 2 minutes. Without alerts, detection time can be hours.

Choosing Your Alert Channels

Different alert channels serve different purposes:

Email Alerts

Best for: SSL and domain expiry warnings, weekly uptime reports, lower-urgency notifications

Email is universally available and creates a written record of incidents. However, email is not ideal for immediate downtime notification — especially if:

• You're not checking email constantly
• Alerts go to a shared inbox where they might be missed
• Your phone isn't showing email notifications

Use email for the alerts that don't require immediate action, and supplement it with faster channels.

SMS Alerts

Best for: Immediate production downtime notification

SMS reaches you anywhere — no app required, no connectivity issues, no notification settings to worry about. A text message to your mobile will wake you up at 3am if your site goes down. That's the point.

SMS is non-negotiable for any production website that has paying customers or real-time requirements.

Slack Notifications

Best for: Team visibility, coordination during incidents

Slack notifications work best when:

• You have a team that should all know about downtime simultaneously
• You want to coordinate incident response in a channel
• You need a log of when alerts fired and were acknowledged

A dedicated #monitoring or #alerts channel in Slack provides team-wide visibility without individual notification fatigue.

Webhook Notifications

Best for: Integrating with other tools, custom workflows, PagerDuty

Most monitoring tools support outgoing webhooks that can trigger:

• PagerDuty or OpsGenie on-call alerts
• Custom scripts (post to a status page, create a ticket, restart a service)
• Microsoft Teams notifications
• Any service with a webhook receiver

Push Notifications

Some monitoring tools offer mobile apps with push notifications — useful as an additional channel if you have the app installed, but not as reliable as SMS as a primary alert mechanism.

Configuring Alert Thresholds

Confirmation Count

The most important threshold to configure. A confirmation count of 2-3 means your monitor must fail consecutively this many times before firing an alert.

Why this matters: a single failed check can result from a momentary network blip between the monitoring server and your site — a transient issue that resolves in seconds. Without confirmation, you'd get an alert and by the time you check, the site is fine.

Recommended: 2 consecutive failures before alerting

With a 1-minute check interval and 2-failure confirmation, you'll know about real outages within 2 minutes — while avoiding false alarms from transient blips.

Response Time Threshold

Many monitoring tools let you alert on slow responses, not just complete failures. Configure a threshold like:

• Warning: response time > 3 seconds
• Critical: response time > 10 seconds (or equivalent to likely timeout)

This catches performance degradation before it becomes complete unavailability.

Recovery Alerts

Always enable recovery notifications. These tell you:

• The outage has ended
• The exact duration of the incident (start time to end time)
• A simple confirmation that normal operation has resumed

Without recovery alerts, you'll be checking your monitoring dashboard manually to confirm things are back to normal.

Alert Routing: Getting to the Right Person

For Solo Developers and Small Sites

Route all alerts to your personal email and mobile. Simple is better — the fewer steps between detection and notification, the faster you respond.

For Small Teams

• Immediate downtime: SMS to the on-call person + Slack to team channel
• SSL/domain warnings: Email to the team email and Slack

Use notification contacts to set up multiple recipients so alerts still reach someone if the primary contact is unavailable.

For Larger Teams

Implement a formal on-call rotation. Primary on-call receives all alerts; if unacknowledged within 5 minutes, alerts escalate to secondary on-call. Document this process so everyone knows who is responsible during any given shift.

Maintenance Windows

Nothing causes alert fatigue faster than expected downtime generating alerts. Configure maintenance windows for:

• Scheduled deployments
• Database migrations
• Planned infrastructure maintenance

A maintenance window suppresses alerts during a defined period — so your team isn't flooded with notifications during a planned 20-minute deployment.

Testing Your Alert Setup

After configuring alerts, test them:

1. Temporarily change your monitor to point at a non-existent URL
2. Wait for the downtime alert to arrive on all configured channels
3. Note the time between the URL change and alert receipt
4. Restore the correct URL and confirm recovery alert arrives

This verifies your entire alert chain is working. Many teams discover their routing is broken when they need it most — during a real incident. Test before then.

Avoiding Alert Fatigue

Alert fatigue occurs when too many alerts — especially false positives — cause recipients to start ignoring or filtering notifications. Prevention:

• Use confirmation counts to eliminate transient blips
• Route carefully — not everyone needs every alert
• Use severity levels — SMS only for critical; Slack and email for warnings
• Review false positive rates monthly and adjust thresholds

An alerting setup that cries wolf regularly will eventually go unheard. Tune your configuration until alerts are rare enough to demand attention when they arrive.

Get Started

Domain Monitor supports email, SMS, Slack, and webhook alerts with configurable confirmation counts and recovery notifications. Setting up your full alert configuration takes about 10 minutes once your monitors are in place.

---

Configure downtime alerts at Domain Monitor.

Related Articles

• The 5 Things You Need To Do When Your Website Goes Down
• "Website Down Checker: How to Check If Your Site Is Offline Right Now"
• "How to Check If a Website Is Down: Tools and Methods"