How to Use Maintenance Windows to Prevent False Alerts

You're about to deploy a database migration. Or rotate SSL certificates. Or update your server infrastructure. You know the site will be briefly unavailable.

The last thing you need is your monitoring tool flooding your team with "SITE DOWN" alerts for planned downtime. That's what maintenance windows are for.

What Is a Maintenance Window?

A maintenance window is a scheduled period during which monitoring alerts are suppressed for selected monitors. The monitoring continues — checks still run, response times are still recorded — but no downtime notifications are sent.

Your status page also reflects the maintenance state, showing "Scheduled Maintenance" instead of an outage. Users who check your status page see planned downtime, not an unexpected incident.

Why Maintenance Windows Matter

Prevent Alert Fatigue

If your team gets alerted every time you deploy, they start ignoring alerts. When a real outage happens at 3 AM, the alert gets treated like another deploy notification. Alert fatigue is one of the most common causes of slow incident response.

Maintenance windows keep your alerts meaningful. Every alert that fires is a real problem worth investigating.

Keep Your Status Page Honest

Without maintenance windows, a planned deploy looks identical to an outage on your status page. Your users see red dots and "Monitor Down" indicators. Some will file support tickets. Others will worry about your reliability.

With a maintenance window, the status page shows a clear "Maintenance" state with your scheduled time. Users know the downtime is intentional and temporary.

Maintain Clean Incident History

Every unplanned outage should be tracked as an incident. But planned downtime isn't an incident — it's an expected event. Without maintenance windows, your incident history fills up with false incidents that dilute the signal.

Clean incident data helps you measure real uptime and identify actual reliability issues.

How to Schedule a Maintenance Window in Monitoristic

1. Go to your Dashboard → Maintenance
2. Click Schedule Maintenance
3. Set the details:
   • Title — e.g., "Database migration" or "SSL certificate renewal"
   • Start time — when maintenance begins
   • End time — when you expect it to finish
   • Affected monitors — select which monitors to suppress alerts for
4. Save

When the maintenance window starts:

• Alerts are suppressed for the selected monitors
• Your status page shows "Maintenance" for those monitors
• Connected notification channels receive a maintenance start notification

When the window ends:

• Normal alerting resumes
• Your status page returns to normal
• A maintenance completed notification is sent

Best Practices

Schedule Maintenance During Low-Traffic Hours

Check your analytics for the quietest hours. For most B2B SaaS products, late evening or early morning in your primary market's timezone works well. For global services, there's never a perfect time — pick the least bad option and communicate clearly.

Set Realistic Time Windows

Add buffer time. If you think a migration will take 30 minutes, schedule a 60-minute window. It's better to end maintenance early than to extend it. Extending a window mid-maintenance means your alerts were suppressed but now need to fire — and your team may have already moved on.

Communicate in Advance

Your status page will show scheduled maintenance, but proactive communication is better. Consider notifying affected users via email or in-app message before the window opens. "We're performing scheduled maintenance tonight from 10 PM to 11 PM UTC. Some services may be briefly unavailable."

Use Descriptive Titles

"Maintenance" tells users nothing. "Database migration — API may be slow for 15 minutes" tells them exactly what to expect. Good maintenance titles reduce support tickets.

Review After Every Window

After maintenance completes, check your monitors. Did everything come back up cleanly? Are response times normal? A quick post-maintenance review catches issues before your users notice them.

Maintenance Windows vs. Pausing Monitors

Some teams pause their monitors entirely during maintenance. This works, but you lose visibility:

Maintenance windows are better because they maintain visibility. If your maintenance causes an unexpected issue — say, the site doesn't come back up — the checks still run and will detect it once the window closes.

Common Scenarios

Deploy window: Schedule 15-30 minutes around your deployment time. If deploys are frequent (multiple per day), consider increasing your check interval during peak deploy hours instead.

Infrastructure migration: Schedule a longer window (1-4 hours). Include all monitors that could be affected, not just the ones you think will be impacted.

SSL renewal: Usually quick (under 5 minutes of actual downtime), but schedule 15-30 minutes to account for certificate propagation.

Database maintenance: Schedule based on your database provider's maintenance window. Add 15 minutes of buffer on each end.

Available on Every Plan

Maintenance windows are included on all Monitoristic plans — Lite, Pro, and Business. There's no reason to skip them, even on the smallest plan.

Set up your first maintenance window before your next deploy. Your team's alert fatigue will thank you.