Scheduled maintenance

Announce planned work on your status page, run it through the scheduled → in progress → completed lifecycle, and understand what maintenance windows do not suppress.

Last updated August 5, 2026

A maintenance window tells your customers that downtime is intentional. It renders differently from an incident, it appears before the work starts, and it records both what you planned and what actually happened.

Scheduling a window

Open the status page → New Maintenance.
Enter a title and an optional description.
Set the scheduled start and scheduled end. The end must be after the start; the form checks.
Pick the affected services.
Click Schedule.

The window appears on the public page under Upcoming maintenance immediately.

Lifecycle

State	What it means
Scheduled	Created in advance. Listed with its planned start time.
In progress	The work has begun. The actual start time is stamped when you transition.
Completed	Finished. The actual end time is stamped.

An in-progress window takes over the top banner on the page — ahead of any incident. Completed windows move to Past maintenance.

Because both the scheduled and actual times are recorded, the public page can show "planned 02:00–04:00, actually 02:04–03:31". That is a small thing that buys a lot of credibility.

Updates

Maintenance has the same append-only update timeline as an incident. Use it:

"Maintenance has begun" — transitions to In progress.
"Phase 2 complete, starting phase 3" — stays In progress.
"Maintenance complete, all systems normal" — transitions to Completed.

Each window has its own public detail page at {your-page-host}/maintenance/{uuid}, showing scheduled versus actual times and the full update timeline.

Maintenance windows suppress nothing

This is the single most common wrong assumption about maintenance windows, so it is worth being blunt. A maintenance window on a status page is an announcement. It does not:

pause or slow your monitors,
stop automatic incidents opening while the work is in progress,
mute Watch Owl alert rules.

If you are taking a service down and it has automatic incidents enabled, turn on maintenance mode on the monitor itself before you start. That is the only switch that stops a monitor checking. Turn it off when you are done.

Practical sequence for planned downtime

Schedule the window a day or more ahead so customers see it coming.
Immediately before the work, set maintenance mode on the affected monitors.
Post an update transitioning the window to In progress.
Do the work, posting updates at meaningful checkpoints.
Clear maintenance mode on the monitors and confirm they come back green.
Post a final update transitioning the window to Completed.

Audit trail

Creating a window, transitioning it, and posting updates are all written to the audit log, on every plan.

What maintenance windows do not do

They do not notify anyone. There is no subscriber list, so scheduling a window does not email your customers. Scheduled subscriber notifications are on the roadmap.
There are no recurring windows. Each one is created individually.
There are no templates. Write the description each time, or keep your own boilerplate somewhere you can paste from.