Maintenance Windows
Maintenance windows let you schedule planned downtime without triggering false alerts. During a maintenance window, monitoring continues but alert rules are suppressed for the targeted monitors.
How it works
- Create a window with a start time, end time, and which monitors it applies to.
- During the window, checks continue to run but failed checks do not create incidents or fire alerts.
- On your status page, the maintenance window is displayed so users know the downtime is planned.
- When the window ends, normal alerting resumes automatically.
Configuration
| Setting | Description |
|---|---|
| Title | A short description of the maintenance (e.g., "Database migration"). |
| Description | Optional details about what is being done. |
| Start time | When the maintenance window begins. |
| End time | When the maintenance window ends. |
| Monitors | Apply to all monitors or select specific ones. |
| Show on status page | Whether to display the maintenance on your public status page. |
| Recurring | Optional recurring pattern (e.g., weekly on Sunday 2:00-4:00 AM). |
Window states
| State | Meaning |
|---|---|
| Scheduled | The window is in the future and has not started yet. |
| Active | The window is currently in effect. Alerts are suppressed. |
| Completed | The window has ended. Normal alerting has resumed. |
Plan availability
Maintenance windows require the Starter plan or higher. Free plan users see an upgrade prompt.
Tips
- Create the window before the maintenance starts. If you create it after monitors have already gone down, incidents may have already been created.
- Use recurring windows for regular maintenance schedules (e.g., weekly patching) so you do not have to create a new window each time.
- Target specific monitors rather than all monitors when only a subset of your infrastructure is affected. This way, you still get alerts for unrelated outages during the maintenance period.