Maintenance Windows

Maintenance windows mark planned downtime so scheduled work does not create misleading incidents, notifications, or uptime history. Windows can be one-time or recurring and can apply directly to monitors or indirectly through folders, groups, and tags.

Types

Single

A single maintenance window has a start and end timestamp. Use it for one-off deploys, migrations, outages, or vendor work.

Recurring

A recurring maintenance window uses schedule-style recurrence settings. Use it for routine maintenance such as weekly patching, nightly batch windows, or monthly database work.

Creating a Window

Choose Single or Recurring.
Keep the window active or create it paused.
Set the start/end time or recurring frequency.
Use an auto-generated name based on the schedule, or disable auto-generation and enter a custom name.
Add associations for monitors, groups, folders, or tags.

Associations

A maintenance window can apply to monitors directly, or to every monitor matching a group, folder, or tag association. Monitor forms show both directly selected windows and inherited windows. Inherited windows are read-only from the monitor form and must be changed at the maintenance window or association level.

Calendar Export

The maintenance windows list includes a calendar subscription action. It provides an iCal URL for the organization maintenance schedule and incidents so teams can subscribe from calendar apps.

Managing Windows

The list shows type, name, active/paused status, monitor count, and actions.
Recurring windows can be paused and resumed.
Windows can be deleted when they are no longer needed.
Custom names show the generated schedule description as a tooltip.

Impact

Incidents - Planned downtime is suppressed or marked as maintenance instead of normal outage behavior.
Notifications - Alerts are avoided for expected work.
Status Pages - Status pages can expose maintenance and include it in calendar export.
Uptime - Planned maintenance is separated from unplanned downtime.

Examples

Weekly Database Maintenance

Type: Recurring
Frequency: Weekly, Sunday 02:00-03:00
Association: Database group
Name: Auto-generated

One-Time Deploy

Type: Single
Start: 2026-05-15 21:00
End: 2026-05-15 22:00
Association: tag production-api
Name: API deployment

Best Practices

Create windows before work starts.
Associate by folder, group, or tag when a maintenance event affects many monitors.
Use custom names for business-visible events and auto-generated names for routine recurring windows.
Pause recurring windows when a normal cycle is skipped instead of deleting and recreating them.