Maintenance
Planned work with clear windows
Problem
Surprises erode trust during planned work
Maintenance announced in chat but not on the status page forces customers to guess. Unbounded windows make it hard to know when service expectations return to normal.
Ad-hoc posts
No shared window
Weak handoff
Maintenance windows bind a title, time range, and affected components to the same model as incidents and public status.
Lifecycle
States you can rely on
A window is scheduled until it starts, then in progress until it completes. When it finishes, it is completed. You can cancel only while it is still scheduled. Edits and deletion apply to scheduled windows only.
- Explicit scheduled and end times
- Start and completion timestamps
- Clear rules for cancel
Components
Affected components move with the window
When maintenance starts, affected components take a maintenance state from the window. When maintenance completes, components return to operational when no other active incident still covers them.
ComponentsIncidents
Optional public incident when work starts
If enabled, starting maintenance can create a public incident with the same title and affected components. Completing maintenance can resolve that incident with a clear, public completion message.
Incident managementAutomation
Auto start, auto complete, or operate by hand
Per window you can enable automatic start at the scheduled time and automatic completion at the scheduled end. You can still start or complete manually from the dashboard when you need control outside the clock.
Status page
Subscribers see scheduled and active windows
The public view includes maintenance that is scheduled or already in progress so upcoming work is visible before it starts.
Public status pageComponents · 90-day uptime
Incident · scheduled maintenance Sat 02:00 UTC
Summary
Maintenance that matches how you operate
Time-bounded windows, component state, optional incidents, and public visibility sit on the same platform as monitoring and incidents.
- •Clear lifecycle from scheduled to completed
- •Components and incidents wired when you want them
- •Public page shows what subscribers need to plan around