Docs → Guides & how-tos

Maintenance windows & planned work

Why planned maintenance happens, how you hear about it first, and what to do if something misbehaves afterward.

Last updated: August 2026

At a glance

Why maintenance happens

Patches, updates, and hardware refreshes are how systems stay secure and boring. Skipping maintenance does not avoid disruption — it defers it to the worst possible moment and adds an attacker to the meeting.

How a window unfolds

1
You hear first
What is changing, when, and what — if anything — users will notice. No surprises is the standard we hold ourselves to.

2
During the window
Brief slowdowns or restarts of the named systems are normal. Anything outside what was announced is not — report it.

3
Afterward
Systems verified, window closed. If something misbehaves later, mention the timing — “after last night’s maintenance” narrows the search enormously.

Note: emergencies trump schedules. When active exploitation is in play, patching fast beats patching politely — and you hear about it as it happens, not after.

Common questions

Can we ask you to avoid certain times?+

Yes. Tell us your blackout periods — payroll runs, seasonal crunch, big demos — and we plan around them.

Do critical security patches wait for a window?+

Not always. When active exploitation is in play, patching fast beats patching politely — we tell you when that trade is being made.

Something broke right after maintenance. Coincidence?+

Maybe, maybe not — tell us either way and mention the timing. Recency is one of the most useful diagnostic facts there is.

Related docs

Incident response
When something is wrong outside any window.

Support escalation
How to push when something feels stuck.

Backup & restore
The safety net under every change we make.

Have blackout dates we should know about?
Tell us once and they go on the calendar for every future window.