Schedule a window
Open Maintenance, or Settings → Maintenance if available for your role. Create a maintenance window and enter a name or reason, optional description, start time, and end time. Select the endpoints affected by the work and save.
Use a name that will make sense during response, such as “Production database upgrade”. Review the scope before saving so unrelated services remain covered by normal alerting. The end time must be after the start time.
Repeating maintenance
The form supports one-time windows and repeating schedules: daily, weekly, monthly on a specific day, monthly on the Nth weekday, and yearly on a specific date. Select Repeat every and, if needed, an end date for the recurrence. Review the first occurrence and timezone before saving, especially for work spanning midnight or daylight-saving changes.
During and after the window
Maintenance suppresses alerts for affected services during planned work. It does not establish that those services are healthy. Review monitoring evidence during the work and verify fresh successful checks after it ends.
If the work finishes early or moves, edit or remove the window so future alert behavior matches the actual plan. Pausing a monitor is a separate operation; do not assume an expired window resumes a monitor that you manually paused.
Automate planned work
The Management API can create a one-time maintenance window using a name, ISO timestamps, and monitor IDs. Its create schema does not expose recurring-rule fields; configure recurring schedules through the app. See API reference.