[00:02]
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, Coast and stayed dead for roughly 36
[00:14]
hours, dragging Copilot, SharePoint, and about a dozen other Microsoft 365 services into the grave with it. And now legally, they're forced to rename it Microsoft 364. The down detector saw reports from 74 countries in about an
[00:26]
hour. Traders on Wall Street went back to phones and fax machines. And it all out of Nvidia. >> Don't let Outlook control what you do >> What are the chances of that? In fact, he got to be CEO for a whole extra day
[00:40]
with Outlook. But then on Friday the Federal Aviation Administration grounded every departing flight in the declared all these events were connected. In today's video, we'll find
[00:54]
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. It is November 16th, 2026, and you're watching the code report. The dominoes began to fall at
[01:07]
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 Americas, which was accurate in the sense that the Americas are part of the
[01:20]
an elevated load, but possibly from 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
[01:32]
unexpectedly unavailable. To understand the root of the issue, we first need to load balancer constantly pings every server fails, it gets pulled out of the rotation, which is great when one server
[01:45]
once, all their traffic lands on the survivors who get overloaded and then get pulled out too, just like a bunch of dominoes toppling each other over. And Microsoft describe. The servers were failing automated health checks and the
[02:00]
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.
[02:12]
words, the servers can become unresponsive again once they receive traffic because every single male client on planet Earth was standing outside announced they had an alternative health check method, which is just a BS way of
[02:25]
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 their admin tools to find out why the admin tools were down. And when NBC News
[02:39]
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
[02:52]
because it was already Friday there. The only downside, though, is Microsoft Teams somehow kept working like an invincible apocalyptic cockroach. But then on Friday afternoon, all hell broke loose when the FAA halted all departures
[03:04]
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
[03:16]
systems dying within 24 hours looks very suspicious, especially right after Nvidia's Wong just got laid off. Now, although I wish this was a catastrophic for views on this channel. It appears the two events are not related. The
[03:28]
Homeland Security Secretary said, quote, "There is no connection between this and Microsoft." Microsoft said it has no indication they're related. And the of switches and routers that got overloaded with data and then came out
[03:41]
later and blamed it on the L3 Harris defense contractor who swapped out a 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
[03:54]
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 the network overwhelms a box that everything depends on. And that brings
[04:07]
still waiting on the full post-mortem, but we know they started rolling back a on Friday, they said they were deeply sorry and that the incident was introduced by an issue during an earlier network capacity upgrade. Apparently,
[04:21]
latent bug in the system that sets up secure connections and that caused point where all the servers ran out of processing power, which is kind of supposed to add capacity is the thing that removed all of the capacity. But
[04:36]
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 definitely had nothing to do with this. that part at least they're 100% certain
[04:50]
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
[05:02]
build more data centers to run more AI agents to replace even more humans. But even though this outage wasn't caused by AI agents, it caused roughly $7 billion hurt by this, you may be entitled to compensation. You just have to reach out
[05:17]
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. It gives you a single API to access over 600 different models and can
[05:29]
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
[05:41]
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 or starts rate limiting, it automatically routes your traffic somewhere else. So far, the new router is delivering about 20% faster time to
[06:06]
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. Try it This has been the code report. Thanks for watching and I will see you in the
[06:19]
for watching and I will see you in the next one.