#59 · Six days, seven outages: not hacks, changes

Microsoft, the FAA, United, Chase, Apple, Marriott and the NSA all had outages between 12 and 17 Nov 2026. Almost every stated cause was a change. Safe deployment, rollback and blast radius.

1 min readReels · Reel Notes

Ek line yaad rakho: duniya hack se kam, update se zyada girti hai.

The week (12–17 Nov 2026)

DateWhoStated cause
12–14 NovMicrosoft 365A network capacity upgrade after a recent network change
13 NovUS FAAOverloaded switches/routers; linked to a newly installed router
16 NovUnited AirlinesTechnology outage, "no indication" of a cyber issue
16 NovChase and other US banksChase: a software bug affecting hardware systems
17 NovApple"An internal update"
17 NovMarriottSign-in technical issue
—NSAInternal communications degraded during scheduled maintenance

Officials say the incidents were unrelated, with no evidence of a coordinated cyberattack (compiled by The National News Desk, 17 Nov 2026).

The pattern

Google's SRE team: "roughly 70% of outages are due to changes in a live system" (Tenets of SRE). This week fits: upgrades, a new router, an internal update, a bug, maintenance.

The interview answer: safe deployment + blast radius

  • Small changes, staged: canary to a few users or one region, then widen.
  • Detect fast: watch error rates and latency per stage; stop automatically.
  • Roll back in one step: every change must be reversible; feature flags help.
  • Blast radius: split the system into cells or compartments so one bad change only sinks one compartment.

Words to say: change management, canary, progressive rollout, rollback, feature flags, blast radius, cell-based architecture.

Follow-up questions

If changes cause most outages, why not change less? Freezing changes builds up risk: the next release is bigger and scarier. The goal is many small, safe, reversible changes.

What would you add first to a team with no safe-deployment process? Automatic rollback on error-rate spikes, then staged rollouts by region, then cell isolation for the most critical service.

Causes are the companies' own statements; several root causes were still under investigation.

Go deeper

Part of the Reels track (Notes for every @masstdev reel).

Finished reading?

Mark it done to track your progress in Reels.