Scheduled maintenance windows

Scheduled maintenance is for changes you control: deploys, database migrations, infrastructure upgrades. Announce them in advance so customers can plan and aren't surprised when you go offline.

To schedule:
1. Status → "Schedule Maintenance"
2. Title (e.g. "Database migration — 5 minute API downtime")
3. Start and end time (in your timezone — auto-converts for subscribers)
4. Affected components
5. Description — what's happening and what users should expect
6. Click "Schedule"

What happens:
• The maintenance window appears on the public page immediately under "Upcoming Maintenance"
• Subscribers get an email announcement right away (so they know in advance)
• 1 hour before the start time, a reminder email goes out
• At the start time, the maintenance auto-publishes — affected components flip to "Maintenance" status
• At the end time, components flip back to "Operational" — or you can manually mark complete earlier if you finish faster
• Resolved maintenance entries stay in the 90-day history

Best practices:
• Schedule with 7+ days of lead time for non-urgent changes — gives customers time to plan
• Pick low-traffic windows (overnight in your customers' timezone) for outage-causing changes
• If you finish early, manually mark resolved instead of waiting for the end time — sends a "completed early" notification to subscribers
• If you need to extend the window, edit the maintenance and the new end time goes out as an update
• Scheduled maintenance does NOT count against your uptime SLA in the public page calculations — that's reserved for unscheduled incidents