Skip to content

Incidents and maintenance ​

Tell visitors what is going on. Incidents are for things that go wrong, maintenance is for work you plan ahead. Both show on the status page with a timeline of updates and the services they affect.

Incidents ​

Post one under Incidents → New incident: a title, the affected services, a severity and a first update.

SeverityMeaning
MinorSomething small, most people won't notice
MajorA clear problem for many people
CriticalA service is unusable. Its days turn red and count as downtime

Each update has a status, which moves the incident along:

StatusMeaning
InvestigatingWe are looking into it
IdentifiedWe know the cause
MonitoringA fix is out, we are watching
ResolvedEverything is back to normal

Real start and end times ​

An incident keeps the time it really started and ended, not the time you typed it in:

  • Fill in Ended at to add an incident that is already over.
  • Date an update back to when it happened. Updates dated back send no notifications.
  • Move the end afterwards when it turns out to be wrong.

Maintenance ​

Plan maintenance under Maintenance → Schedule maintenance with a start, an end and the affected services. Visitors see it coming on the status page.

StatusMeaning
ScheduledPlanned, not started yet
In progressWork is happening now
CompletedWork is done, ends it now
CancelledNot going ahead

Cancelled maintenance can be brought back.

Notifications ​

Posting, updating and resolving incidents, and maintenance that is planned, starts, ends or is cancelled, can go to Discord, email and the bell. Link previews of an incident or maintenance page show its live status when you share it.

Who can post, edit or delete incidents and maintenance is set with roles.

Released under the MIT License.