Greg Cardoni retweeted
I’ve created a helpful headline template for all media organizations this month.
Jenson is open to a return as CEO.
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
10
Check out this @vulfpeck concert, “Live at The Greek”.
They crowdsourced footage from fans, synced it to the board's HQ audio, and edited it into an 80-minute video. Very clever idea. youtu.be/BFVrY_kU2Ws?si=0bcc…
This is currently the most detailed root cause analysis of last week's MSFT outage.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
52
Free, open-source, white-label DocuSign, courtesy of Kevin Rose!
DocuSign wants $8,100/yr from a 15-person team just to sign PDFs. So I built SignuDoc: open source, one-click deploy to your own @vercel account, $0 per seat.
White-label branding, full audit trails, tamper-evident seals and your documents never leave your cloud.
1
2
129
There’s a THIRD Culkin brother named Rory?! en.wikipedia.org/wiki/Rory_C…
46
I'm curious what the betting markets are pricing the chances of Jensen returning as CEO within the next week at.
@grok, can you check Kalshi, Polymarket, etc., and report back?
2
81
So nice to see Britney Spears doing well. 😬🫣 instagram.com/reel/Dfvyyo7Bm…
51
Buying a used BMW touring bike and taking a few months off to ride around the United States is still a bucket-list item for me. What a fun adventure.
I'm traveling across US on motorcycle, to explore a country I love and to meet people from all walks of life, especially in rural America, and learn about their life story, philosophy, and just celebrate their humanity. I'm about 1,000 miles in.
I know my mom will surely kill me when she reads this. So, mom, please don't worry, everything will be great 🙏❤️
Btw, I still need to publish videos on my trip through China, where I hitchhiked about 3,000km across rural China, also interviewed some of the top AI & robotics folks there. I'll do that soon.
I'm just slow with the editing thing & bad at the filming thing. I'll try to get better. Mostly, when I travel, I focus on taking it all in and being present with the people in front of me, learning from them, while allocating no thought to the camera. The camera is a side thing I bring along sometimes because it's nice to relive those moments & to share with others.
Anyway, I'll probably take breaks from the road on occassion (to do podcasts, etc). But the goal is to eventually crisscross the country. Who knows how far I'll actually get.
And to friends who will surely write me "wtf are you doing you idiot", please don't worry, while it's true that I'm kind of an idiot, I will also make sure to be safe. Exploring the country on a motorcycle is unlike anything else, it's freedom. It makes me love this country even more: its beautiful nature and all the variety of characters who make up America. And of course, I'm trying to stay off of the interstate, taking as many backroads as I can.
I'll post video if/when I get to it. Sorry to be slow.
Love you all ❤️
2
391


















