Planned Downtime Notification Template (+ 7 Ready-to-Copy Examples)

Why Your Downtime Notification Matters as Much as the Fix

Planned maintenance is a fact of life for any online service. Servers need patching, databases need migrations, and infrastructure needs upgrading. But the difference between a maintenance window that damages trust and one that actually builds it comes down to one thing: communication.

A professional, well-timed downtime notification tells users you're on top of things — that the outage is expected, controlled, and time-limited. Poor communication (or no communication) makes users think something is catastrophically wrong.

In this guide, you'll find 7 copy-paste templates for every channel and scenario, plus guidance on timing and tone.

The Anatomy of a Good Downtime Notification

Before the templates, understand the five elements every downtime notification needs:

1. What: Briefly describe the service affected (be specific — "the API" not "our systems")
2. When: Start time and expected end time, always with timezone
3. Why: One sentence on the reason (users want context, not excuses)
4. Impact: What users can and cannot do during the window
5. Where: Link to your status page for live updates

Keep it under 150 words. Users don't read long maintenance emails — they skim for the times and impact.

Template 1: Advance Email Notification (48–72 hours before)

Use this 2–3 days before a significant planned outage:

Subject: Scheduled Maintenance — [Service Name] | [Date] [Start Time] – [End Time] [Timezone]

Hi [Name / Team],

We're writing to let you know that [Service Name] will be undergoing scheduled maintenance on [Day, Date] from [Start Time] to [End Time] [Timezone].

What's happening: [Brief description — e.g., "database migration to improve query performance"]
Impact: [e.g., "The dashboard and API will be unavailable during this window. All monitoring data will be retained."
What to do: [e.g., "No action is required from your side. If you have time-sensitive jobs scheduled, please reschedule them before [Time]."]

We'll post live updates at: [status page URL]

Questions? Reply to this email or contact [[email protected]].

Thanks for your patience,
[Team Name]

Template 2: Same-Day Reminder Email (Morning of maintenance)

Subject: Reminder: [Service Name] Maintenance Tonight at [Time] [Timezone]

Quick reminder: [Service Name] maintenance is scheduled for tonight at [Start Time] [Timezone] and will last approximately [duration].

During this time: [one-line impact summary]

Live status: [status page URL]

— [Team Name]

Template 3: Slack / Teams Channel Message

:hammer_and_wrench: Scheduled Maintenance Notice

Service: [Service Name]
When: [Date] [Start Time] – [End Time] [Timezone]
Duration: ~[X] hours
Impact: [Brief impact — e.g., "API unavailable, dashboard read-only"]
Reason: [One line — e.g., "Infrastructure upgrade to improve reliability"]

Live updates: [status page URL]
Questions: ping @[oncall-handle]

Template 4: Status Page Maintenance Banner

Post this on your status page 24–48 hours in advance:

Scheduled Maintenance — [Date], [Start Time]–[End Time] [Timezone]

[Service Name] will be offline for scheduled maintenance on [Date] from [Start Time] to [End Time] [Timezone] ([X] hours).

Affected: [List services/components]
Expected impact: [Brief description]

We will post updates here throughout the maintenance window. Historical data and settings are unaffected.

Template 5: Maintenance Start Notification

Post this the moment maintenance begins:

Subject: [Service Name] Maintenance Has Started — Expected Until [End Time] [Timezone]

Maintenance on [Service Name] has begun as scheduled. We expect to complete by [End Time] [Timezone].

Current status: [brief update]
Live updates: [status page URL]

— [Team Name]

Template 6: Maintenance Complete Notification

Subject: [Service Name] Maintenance Complete — All Systems Operational

Maintenance on [Service Name] is complete. All services are fully operational as of [End Time] [Timezone].

What was done: [Brief summary — e.g., "Database migration completed successfully. Query performance improved by ~30%."]

Thank you for your patience. If you experience any issues, please contact [support link].

— [Team Name]

Template 7: Emergency Unplanned Outage (Not Maintenance)

For unexpected incidents — speed matters over polish:

Subject: [Service Name] Service Disruption — We're Investigating

We're currently experiencing issues with [Service Name]. Our team has been alerted and is investigating.

Impact: [What is affected]
Started: [Approximate time]

We'll update this page every 30 minutes: [status page URL]

— [Team Name]

Timing Checklist for Planned Maintenance

• 72 hours before: Send advance email notification
• 24 hours before: Post maintenance banner on status page
• Morning of: Send same-day reminder (Slack/email)
• At start: Post maintenance-started update on status page
• During (if extended): Post progress updates every 30–60 minutes
• On completion: Send "all clear" email + resolve status page incident

Automate Downtime Alerts with AlertSleep

Templates handle planned maintenance well. But what about unplanned outages at 3am? AlertSleep monitors your website, API, and services 24/7 and sends instant alerts via SMS, email, phone call, or Slack the moment something goes down — so you're never the last to know.

AlertSleep also includes a public status page where you can post maintenance windows and incident updates — automatically updated when your monitors detect downtime. Your users can subscribe to email alerts for real-time status changes.

Start monitoring free (no credit card required) — 5 monitors, email alerts, and a status page included on the free plan.