Maintenance
Maintenance windows and incident updates
Statuscode lets you communicate scheduled work, active incidents, and follow-up updates without forcing customers to guess what is happening.
Scheduling maintenance
1
Open the maintenance manager in the editor.
2
Choose all systems or specific monitors.
3
Set the title, date, time, duration, and optional markdown description.
4
Save the maintenance window, then publish when you want customers to see it live.
Incident updates
Annotations and incident entries can be attached to monitors so the public page shows context, not only a raw outage state.
New updates gain publish timestamps when they first enter the live public snapshot.
Markdown is supported in maintenance descriptions and related update content.
What customers see
Active maintenance can change the banner state and highlight affected systems.
Incident history reflects the published updates, not hidden draft notes.
Partial maintenance and partial outages remain visually distinct from full healthy status.
Best practice
Before work
Schedule the window early and publish it.
During work
Keep updates short, timestamped, and honest.
After work
Close the incident or maintenance entry and republish final state if needed.
Was this helpful?
Quick feedback helps improve the docs.