Scheduled Maintenance

Plan maintenance windows in advance and keep your customers informed about upcoming service interruptions.

Scheduling Maintenance

Navigate to Incidents and click Schedule Maintenance. You'll need to provide:

  • Title - What maintenance is being performed (e.g., "Database upgrade", "Server migration")
  • Scheduled Start - When the maintenance window begins
  • Scheduled End - When you expect maintenance to complete
  • Impact Level - How the maintenance will affect users
  • Maintenance Message - Details about what will happen during maintenance
  • Affected Components - Which services will be impacted

Maintenance Impact Levels

Choose an impact level that accurately reflects how users will be affected:

None

Informational only - no user-facing impact expected (e.g., backend optimisations)

Minor

Some features may be slower or temporarily unavailable

Major

Significant functionality will be unavailable during maintenance

Critical

Complete service unavailability expected

Automation Settings

Status Quo can automatically manage your maintenance windows:

Auto-Start

When enabled, the maintenance will automatically begin at the scheduled start time. Affected components will be set to "Maintenance" status and subscribers will be notified.

Auto-End

When enabled, the maintenance will automatically be marked as resolved at the scheduled end time. Affected components will return to "Operational" status.

💡 Tip

If maintenance runs longer than expected, you can manually extend it by editing the scheduled end time or disabling auto-end.

Maintenance Notifications

Subscribers are notified at key points during the maintenance lifecycle:

  • When scheduled - Initial announcement that maintenance is planned
  • When started - Maintenance has begun (automatic or manual)
  • Updates - Any progress updates you post during maintenance
  • When completed - Maintenance is finished and services are restored

How Maintenance Appears

Scheduled maintenance is displayed prominently on your public status page:

  • Before start - Shown in an "Upcoming Maintenance" section with countdown
  • During maintenance - Displayed as an active incident with "Maintenance" badge
  • After completion - Moved to incident history

Affected components show a blue "Maintenance" status indicator during the maintenance window.

Best Practices

  • Schedule in advance - Give customers at least 24-48 hours notice for planned maintenance
  • Choose low-traffic times - Schedule maintenance during off-peak hours when possible
  • Be specific - Clearly explain what will be unavailable and for how long
  • Pad your estimates - Add buffer time to your scheduled end time
  • Post updates - Keep customers informed of progress during longer maintenance windows