Incidents and scheduled maintenance
Post incidents and scheduled maintenance to your Servor status page, keep affected components accurate, and notify subscribers automatically.
Your status page is where users go when something feels off. Posting incidents and scheduled maintenance there keeps them informed, sets expectations, and cuts down on support tickets. This page shows you how to do both from a status page and how they connect to the rest of Servor.
Incidents and maintenance both appear on your page's public timeline and notify your subscribers — the difference is timing: an incident is something going wrong now; scheduled maintenance is planned work you announce in advance.
Post an incident
An incident tells users something is broken and tracks it through to resolution.
Start an incident
From your status page, or from Report an incident in Servor, choose to report an incident and select this status page to publish to.
Describe it and set impact
Give it a clear title, a first message, a status (investigating, identified, monitoring, resolved) and an impact (minor, major, critical). See Report an incident for what each value means.
Link affected components
Tick the components that are affected. They inherit the incident's impact automatically, so the top of your status page reflects reality without a second edit — and they return to operational when you resolve the incident.
Publish and keep updating
Publish it. As you learn more, post updates and mark it resolved when it's fixed. Each update appears on the timeline and notifies subscribers.
Let monitors open incidents for you
Servor can open an incident automatically when a linked monitor goes down, so your page reacts even when nobody's watching. See Automatic incidents.
Schedule maintenance
Scheduled maintenance is planned downtime or degraded service you announce ahead of time — a database upgrade, a deploy window, a provider migration. Announcing it stops users from mistaking planned work for an outage.
Create a maintenance window
From your status page (open it from Status pages in Servor), create a scheduled maintenance and pick the start and end times. Subscribers see the window in advance.
Explain what's happening
Write a short note: what you're doing, what users might notice, and how long you expect it to take.
Mark affected components
Link the components that will be impacted so the page shows the maintenance state on the right parts of your service.
Publish
Publish the maintenance. It shows on your page as upcoming, becomes active during the window, and closes automatically when it ends.
Incidents vs maintenance at a glance
| Incident | Scheduled maintenance | |
|---|---|---|
| When | Something is wrong now | Planned, announced in advance |
| Purpose | Communicate and track an outage | Warn users before expected disruption |
| Components | Turn to the incident's impact | Show a maintenance state during the window |
| Timeline | Updated until resolved | Runs from a start to an end time |
| Subscribers | Notified on publish and each update | Notified when scheduled and when it starts |
Keeping the page accurate
The single habit that makes a status page trustworthy is linking incidents and maintenance to the right components. Because linked components follow the incident's impact automatically, you never have to remember to flip a component back — resolving the incident does it for you. Pair that with components linked to monitors and most of your page maintains itself.