International
The Morning Dev

Only the news worth knowing

‹
 

Watch · Fast-paced tech news

Why Microsoft couldn’t fix its own servers for 36 hours...

The Brief

  • Microsoft Exchange Online was down for roughly 36 hours after a routine network capacity upgrade.
  • The video breaks down what failed and why restarting the systems did not fix it.
  • It also addresses whether the outage had any connection to an FAA grounding of flights in America.

Why watch · It shows how a routine network capacity change can cause a long, widespread cloud email outage.

  • Microsoft Exchange Online
  • Network outage
  • Cloud infrastructure

Summarised by Claude from the video’s title and description – no transcript was available, so check the video for the details.

Show the full video description ›

OpenRouter gives you one API for every AI model that routes and governs every request, so your AI is better, faster, and cheaper. Try it free: https://openrouter.ai/?utm_source=fireship&utm_medium=video&utm_campaign=2026-11_dev-sponsorships&utm_content=description Microsoft took down Exchange Online for roughly 36 hours with a routine network capacity upgrade, so let’s break down what actually failed, why turning it off and on again didn’t work, and whether it had anything to do with the FAA grounding every flight in America. Want more Fireship? 🗞️ Newsletter: https://bytes.dev 🧠 Courses: https://fireship.dev