Owning the servers does not make a hybrid system independent of the gateway that connects them.
What happened
From 20:30 UTC on 30 September to 02:15 UTC on 1 October 2026, Azure networking management operations failed intermittently across multiple regions. Resumed updates flooded a shared regional control plane already slowed by an earlier change.
Some ExpressRoute gateways were marked healthy before routing configuration returned. Updates then advanced to redundant instances, leaving neither ready and interrupting connectivity to on-premises networks.
The boundary
The 5-hour-45-minute window describes the overall incident, not every customer’s connection loss. Affected gateways recovered using locally stored configurations after approximately 30 minutes of unsuccessful retrieval attempts. Microsoft rolled back the performance regression and planned stronger rollout and health checks.
Microsoft says customers could not prevent or minimize this specific service incident. That does not establish that every hybrid workload stopped, or that a second cloud would automatically have kept an application running.
The point
Redundant paths need recovery controls that do not fail together.
For a hybrid workload, make the dependency explicit:
- Which local functions continue when the cloud connection disappears?
- Do alternate paths share configuration, identity or update machinery?
- Can operators recover connectivity without reaching the failed management service?
These are architecture review questions, not a claimed workaround for this incident. Record and exercise the answers in the exit-readiness checklist.
The calculator below sizes a possible workload cluster. It does not price an ExpressRoute replacement or establish network independence.
Sources
More incident dossiers
- Your spare zone needs room for your failure — Google Cloud
- A cloud told 495 customers: restore from your own backups — IDC Frontier (IDCF Cloud)
- One failed AI request became 48 more — Microsoft Azure
- One suspended account cut off three clouds — Google Cloud / Railway
- Multi-AZ did not survive the region — AWS
- Cloudflare went down, too — Cloudflare
- Azure’s global front door closed — Microsoft Azure
- One empty DNS record reached across AWS — AWS
All cloud outage evidence → · Test your cloud exit readiness →