Searchable transcript of The $7 billion bug hiding inside Microsoft’s network... — Fireship (06:22). Search for a phrase, then click its timestamp to jump straight to that moment in the video.
Captions sourced from the original video on YouTube, published by Fireship. The video, its captions and all related intellectual property remain the property of their respective owners; AINotes claims no ownership. Provided for research, accessibility and search — see the Transcript Notice and Copyright Policy.
00:00 Last Thursday, Microsoft unintentionally boosted global productivity and made the world a better place by breaking Outlook email for most of the planet. Exchange Online, the back end behind it, flatlined right before lunch on the East Coast and stayed dead for roughly 36 hours, dragging Copilot, SharePoint, and about a dozen other Microsoft 365 services into the grave with it.
00:18 And now legally, they're forced to rename it Microsoft 364. The down detector saw reports from 74 countries in about an hour. Traders on Wall Street went back to phones and fax machines. And it all happened the same day Jensen Wong pulled out of Nvidia. >> Don't let Outlook control what you do every day. >> What are the chances of that? In fact, he got to be CEO for a whole extra day because he was fired via an email sent with Outlook.
00:42 But then on Friday afternoon, things got apocalyptic when the Federal Aviation Administration grounded every departing flight in the United States and every tech influencer declared all these events were connected. In today's video, we'll find out what actually broke inside Microsoft. Why turning it on and off again didn't work and whether or not Jensen's Wong is the true cause of this catastrophic outage.
01:00 It is November 16th, 2026, and you're watching the code report. The dominoes began to fall at exactly 11:17 Thursday morning, Eastern time, when Exchange Online mailboxes stopped opening. And then just a mere 90 minutes later, Microsoft posted that it was investigating an issue in the Americas, which was accurate in the sense that the Americas are part of the globe.
01:20 Now, Microsoft's first theory was an elevated load, but possibly from everyone emailing each other about Jensen's Wong. But then they quickly clarified that it wasn't more traffic. It was fewer servers because a large number of them had become quote unexpectedly unavailable. To understand the root of the issue, we first need to understand how load balancing works.
01:36 A load balancer constantly pings every server with a health check. And if a server fails, it gets pulled out of the rotation, which is great when one server is sick. But if a lot of them fail at once, all their traffic lands on the survivors who get overloaded and then fail their own health checks. So they get pulled out too, just like a bunch of dominoes toppling each other over.
01:53 And that's what the status updates from Microsoft describe. The servers were failing automated health checks and the process responsible for establishing secure connections got so overwhelmed that the server stopped responding. So Microsoft tried the classic solution that works 99% of the time. They unplug them and then plug them back in again. But this didn't work because in their words, the servers can become unresponsive again once they receive traffic because every single male client on planet Earth was standing
02:18 outside waiting to reconnect. At one point, they announced they had an alternative health check method, which is just a BS way of saying we're bypassing the health check to see if the servers work despite them being unhealthy. And to make matters worse, the outage also took out the 365 admin center is so admins couldn't use their admin tools to find out why the admin tools were down.
02:36 And when NBC News emailed Microsoft's PR firm for a comment, the email bounced. Meanwhile, back in the real world, things were in total chaos. Government agencies had to go back to paper records, a jail in Colorado had to take bond payments in person, and the entire country of Australia got a free long weekend because it was already Friday there. The only downside, though, is Microsoft Teams somehow kept working like an invincible apocalyptic cockroach.
02:58 But then on Friday afternoon, all hell broke loose when the FAA halted all departures nationwide for roughly 5 hours. And that's only the second time that's happened since 9/11. It resulted in more than 9,000 flight cancellations on Friday alone. And officials said it was not a cyber attack. And two giant systems dying within 24 hours looks very suspicious, especially right after Nvidia's Wong just got laid off.
03:20 Now, although I wish this was a catastrophic cyber attack because that would be great for views on this channel. It appears the two events are not related. The Homeland Security Secretary said, quote, "There is no connection between this and Microsoft." Microsoft said it has no indication they're related. And the transportation secretary blamed a bunch of switches and routers that got overloaded with data and then came out later and blamed it on the L3 Harris defense contractor who swapped out a router at a remote FAA
03:45 site which then flooded all the other routers with about a thousand login attempts every four or 5 seconds. Other sources have put the blame on old Cisco routers. But as of right now, the FAA hasn't released an official root cause. But even though the Outlook outage and the FAA problems aren't directly related, they share the same underlying issue where a change to the network overwhelms a box that everything depends on.
04:05 And that brings us back to the Microsoft outage. We're still waiting on the full post-mortem, but we know they started rolling back a recent network configuration change. And on Friday, they said they were deeply sorry and that the incident was introduced by an issue during an earlier network capacity upgrade. Apparently, routine network maintenance exposed a latent bug in the system that sets up secure connections and that caused connection requests to pile up to the point where all the servers ran out of processing
04:29 power, which is kind of ironic because the thing that was supposed to add capacity is the thing that removed all of the capacity. But the most important thing that both Microsoft and the FAA have said is that these issues were definitely not caused by AI and shitification of software. It was definitely you stupid humans that caused the issue and AI agents definitely had nothing to do with this.
04:48 that part at least they're 100% certain about already. And it's very important for Microsoft to say that because less than 3 weeks ago they offered voluntary exit packages which are definitely not layoffs to about 60,000 employees, roughly a quarter of the company. And that of course is so they can afford to build more data centers to run more AI agents to replace even more humans.
05:05 But even though this outage wasn't caused by AI agents, it caused roughly $7 billion in lost productivity. And if you've been hurt by this, you may be entitled to compensation. You just have to reach out to Microsoft support for a service credit. Although I wouldn't recommend doing that by email. A much better use of your time though would be to check out Open Router, the sponsor of today's video.
05:25 It gives you a single API to access over 600 different models and can automatically pick the best one for each request based on intelligence, speed, and cost. But the problem is that many of these models are served by multiple providers who are all competing to show the cheapest price per token, which is a very gameable metric. So, Open Router just rebuilt their entire routing algorithm to score every provider on what a successful response actually costs you, including the real price after caching, how fast tokens come
05:53 back, and how reliably the requests succeed. Those scores refresh every few minutes. So, when a provider slows down or starts rate limiting, it automatically routes your traffic somewhere else. So far, the new router is delivering about 20% faster time to first token and 60% fewer rate limit errors with no code changes, which has made a noticeable difference in my weekly rewrites of Horse Tinder.
06:12 Try it out for free today at the link below. This has been the code report. Thanks for watching and I will see you in the next one.