Planned maintenance is the easiest downtime to handle well, and it still fills support queues. Customers find out when something stops working, not when it was announced. Scheduled maintenance windows in Navy are built to fix that.
1. Announce it early
Create the maintenance window on your status page as soon as the date is set. A week of notice is a good default for anything customers will notice. The window shows up on the page with its start time, end time and affected components.
2. Notify subscribers automatically
Status page subscribers get an email when the maintenance is scheduled, a reminder before it starts and a message when it ends. Customers hear about it three times without anyone on your team sending a thing.
3. Pause alerts during the window
Monitors attached to the affected components are paused for the length of the window. Your on-call engineer is not paged for downtime you planned. If the work runs long, extend the window and alerts stay paused.
4. Keep uptime honest
Maintenance windows are shown separately on the 90-day uptime bars. Customers can see that the service was down by plan, not by failure. If something breaks outside the window, it counts as an outage like any other.
5. Close it on time
When the work is done, end the window and let monitors resume. If checks fail after the window ends, Navy opens a normal incident and alerts as usual. Planned work that causes unplanned problems still gets caught.
| Step | When | Who is notified |
|---|---|---|
| Scheduled | When the window is created | Subscribers |
| Reminder | 1 hour before start | Subscribers |
| Completed | When the window ends | Subscribers |
Scheduled maintenance is available on every plan. Announce it early, let Navy handle the reminders and spend the window on the work instead of the inbox.
