Hmmmm... Gemini Neon is indeed good. It solved quite a couple lasting bugs tonight and created a fairly entertaining driving simulator game. I am genuinely pleased with it.
1
69
It was a gorgeous afternoon in #Vancouver today.
Ricoh GR IV
28 mm
ISO 200
ƒ16
1/200 s
1
159
Lawrence retweeted
AI downloads broke the usual CDN model
Since this summer, we're running our own CDN at Hugging Face. It's shipping almost 1 exabyte per month, which means, in practice, about 420 GB every second, through 80,000 requests per second.
Why did we need to build our own?
Well, CDNs were designed to ship many small web files to many people. AI downloads are pretty different: it's a few enormous files, a significant part of them pulled by machines.
This changes a lot of design assumptions.
You're not caching small objects close to users in hundreds of cities anymore: these users are for a big part GPU clusters sitting in a handful of cloud regions.
And a cached web page is useful to 1,000 visitors, while a cached 1,000 GB model is useful to far fewer clients, but each one wants all of it, immediately.
So we've built our own CDN, with caches adapted to massive objects, able to handle release-day mega-floods and multiple giant datasets and trending models being pulled at once.
The team made a live map of it at huggingface-cdn-live.static.…
Hard to stop watching it - it's quite mesmerizing
Please don't copy-paste a long wall of AI-generated text into chat rooms meant for human interactions. It's fine one choose to be a meat proxy. It's not fine to throw tasteless slop in others eyes.
1
1
40
Lawrence retweeted
PowerShell7 is going to ship in Windows!!!!
From the outside, something like this seems like it should be a simple decision.
But when you ship software to a billion people, nothing is a simple decision.
The PowerShell team has been working towards this team for a VERY long time.
You would be shocked to understand how much effort was involved.
I keep encouraging with the original spirit of PowerShell v1:
If there is ANY hoop you are unwilling to jump through, you will not succeed.
Jump through the hoop and there will be another.
And another. And another.
And if you jump through enough, you'll succeed.
MAD RESPECT for the team's fortitude is making this happen.
devblogs.microsoft.com/power…
Lawrence retweeted
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
Lawrence retweeted
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.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
Lawrence retweeted
SRE has changed a lot in 10 years. We're kicking off a special 2-part series with the minds behind "Site Reliability Engineering, 2nd Edition"! 📖
Tune into Part 1 (Season 7, Episode 5) now! 🎧
sre.google/prodcast/#season7… google.smh.re/5ikY
Lawrence retweeted
We just shipped AWS Emulator, which gives coding agents a local copy of AWS to test against.
Early in my career, we built test environments like this by hand, one system at a time. Now, agents are writing code far faster than any team can check it in production. Matt Goldberg, a Senior Principal Engineer on our Developer Tools team, wanted to know whether agents could build and test those environments themselves. He gave @kirodotdev a single prompt, and about 15 minutes later it came back with a first version of an SQS emulator. Turing that into a robust solution took much more work
Here’s what I think this means for engineers today: allthingsdistributed.com/202…
Lawrence retweeted
Here's my new #PowerShell module & #dotnet library (not exactly new, but ok) for building cool interfaces in PowerShell/.NET. It can also prettify your ordinary commands such as Format-Table/Format-List/etc with one line 🚀 consolemonster.dev for demos and usage















