Maintenance windows
Mute planned work on sites, devices or links, once or repeating, so incidents are recorded but nobody is paged.
Updated 10 November 2026
A maintenance window covers work you know about: replacing a backhaul, a firmware upgrade, a generator test. Inside it, incidents on the work are recorded but not sent, and the map shows the window. Owners, admins and technicians can plan them.
Plan a window
In Maintenance, fill in Schedule maintenance:
| Field | What it does |
|---|---|
| Title | What the work is, e.g. Replace TWR-A backhaul. Shown on the map and in the incident. |
| Starts / Ends | In your organisation's time zone. At most 7 days long. |
| Repeats | Doesn't repeat, every day, every week or every month. |
| Repeat until | Optional last date for a repeating window. |
| Sites, devices, links | What the work touches. Pick any mix. |
| Also everything behind these | On by default: towers behind the site you're working on are muted too, since they'll drop with it. |
A repeating window can't be longer than its repeat: under 23 hours for a daily one, under 6 days for a weekly one.
The Maintenance page lists windows that are active now, upcoming, and from the last 14 days.
Mute a device quickly
On any device's page, Working on this device? mutes it and everything behind it from now, for 1, 2 or 4 hours. End now finishes a window early.
When it ends
If something is still broken when the window ends, its incident starts alerting as if it had just opened: you hear about work that didn't go to plan. Incidents that opened and resolved inside the window stay in the history, without messages.