Quick answer: Emergency maintenance is unplanned work that cannot wait — failing hardware, critical security patches, urgent network fixes. It proceeds with as much notice as the situation allows, sometimes none, because acting fast protects customers better than waiting for a convenient window. Details of how such events are handled are governed by the Terms of Service.
Overview
Not every risk announces itself two weeks ahead. When a switch line card starts throwing errors or a critical vulnerability lands, the correct engineering decision is immediate action. Emergency maintenance is rare precisely because planned maintenance keeps most problems from ever becoming urgent.
Before you start
- Accept the premise: an emergency fix now beats a bigger outage later.
- Keep contacts current — even emergencies get communicated as soon as practical, before or during the work.
- Build your stack to tolerate brief interruptions: retries, health checks, automatic reconnects.
Step-by-step guide
What happens during an emergency event and your part in it:
- Trigger: monitoring or vendor advisories reveal an imminent risk (hardware degradation, security flaw, network instability).
- Action: engineers intervene immediately; scope is kept as narrow as possible.
- Communication: notice goes out as soon as practical — sometimes during the work — with status updates until resolution.
- Your side: if your service is affected, hold off on invasive troubleshooting until the event is declared over, then verify your stack.
- Post-event: where warranted, follow-up planned work is scheduled properly to finish the job.
Common issues
- No advance notice: by definition — the notice you get may arrive mid-event; that is the policy working, not failing.
- Confusing emergency work with an incident: both look like interruptions; the announcement (even retrospective) is the differentiator.
- Repeated "emergencies": genuinely should be rare — if you believe they are not, raise it via ticket for an explanation.
When to contact support
Contact support if your service does not recover after an emergency event concludes, or if you need an incident summary for your own customers or compliance records.
Frequently asked questions
Why did I get no advance notice for emergency maintenance?
Because the risk demanded immediate action, such as failing hardware or a critical vulnerability. Notice is sent as soon as practical, sometimes while the work is already underway.
How is emergency maintenance different from an outage?
Both interrupt service, but emergency maintenance is deliberate engineering action with communication before or during it, taken to prevent a larger uncontrolled incident.
What should I do while emergency work is in progress?
Wait for the all-clear before restarting or reconfiguring your stack, then verify services recovered. Report anything still broken afterwards via ticket.
Related articles
Need a hand? Contact Cloud2Y support →
