Scheduling Planned Maintenance

Planned maintenance is different from incidents - it’s scheduled work you know about in advance. Announcing it beforehand helps set user expectations and reduce support requests.

Maintenance vs Incidents

When to Schedule Maintenance

Common reasons for scheduled maintenance:

• Database upgrades
• Security updates
• Server migrations
• Infrastructure changes
• Performance optimizations
• Certificate renewals

If users might notice any impact, it’s worth scheduling maintenance.

Creating a Maintenance Window

1. Go to Maintenances in the left menu
2. Click Schedule Maintenance
3. Fill in the details:

4. Click Schedule

Setting the Time Window

Be realistic about your maintenance window:

• Add buffer time - Things often take longer than expected
• Consider time zones - Choose times with least user impact
• Update if needed - Extend the window if work takes longer

The maintenance will automatically start and end at the scheduled times on your status page.

For affected components, monitor checks are paused during the active maintenance window. When the window ends, only monitors paused by that maintenance window are resumed automatically; monitors disabled manually (or for other reasons) remain disabled.

Affected Components

Select the components that will be impacted:

• Their status automatically changes to “Under Maintenance”
• They return to normal status when maintenance ends
• Users can see exactly what’s affected

Affected components are highlighted on your status page, so users know what to expect during the maintenance window:

In this example, the apac-se-sg component is affected by the maintenance. You’ll notice that the component’s status is automatically updated to “Under Maintenance” (gray pulsating circle) during the scheduled window, and it will return to normal status once the maintenance is complete. This helps users understand which services are impacted and when they can expect them to be back to normal.

Notifying Subscribers

When you create a scheduled maintenance:

1. Subscribers can be automatically notified
2. They receive advance notice before maintenance begins
3. Updates are sent when maintenance starts and ends

Configure notification settings in your status page settings or subscriber settings.

If you use per-component subscriber notifications, note that scheduled and completed maintenance emails are still sent page-wide. Component selection on the maintenance record changes what visitors see on the page, but it does not currently narrow maintenance email delivery.

Subscriber updates follow the maintenance timeline: scheduled notice (if enabled), in-progress visibility at start, and completion visibility at end (or when completed manually earlier).

During Maintenance

While maintenance is in progress:

• Your status page shows the maintenance banner
• Affected components show maintenance status
• Users see the expected end time

If you need to post updates during maintenance, you can add them to the maintenance record.

Completing Maintenance

Maintenance ends automatically at the scheduled end time. If you finish early:

1. Open the maintenance record
2. Click Complete Maintenance or mark it as finished
3. Components return to normal status

If you need more time, you can extend the maintenance window.

Completing early updates runtime maintenance state immediately and affected monitor checks can resume right away (subject to the safety rule above: only maintenance-paused monitors are auto-resumed).

Maintenance Best Practices

Viewing Maintenance History

To see past maintenance:

1. Go to Maintenances in the left menu
2. View completed, ongoing, and scheduled maintenance
3. Click any entry to see details

What’s Next?

• Create and manage incidents
• Set up subscriber notifications
• Understand per-component subscriber delivery
• Configure status page settings
• Notification Channels Overview