Agree with this assessment
It’s extremely obvious what is happening, I don’t know why we don’t just say it:
Agents have made every system on earth highly vulnerable overnight, and there are swarms of agents attacking everyone.
Everyone is running agents to defend themselves, creating rapid patching of security vulnerabilities in every system on earth.
Orgs are either choosing to take their networks down during this transition, or the rapid AI-driven patches are sometimes causing mistakes and errors.
They should just say what is happening. This is what every IT team on earth is dealing with.
1
26
James Glenos retweeted
In the past decade, Wake Co property tax collections more than doubled, compared with a rate of population growth plus inflation of 63%.
#ncpol
Wake County freezes most government hiring through June 2027 County leaders project a fiscal year 2028 deficit of $20 million to $60 million. County will brief school board today. (Via Nolan Wilkinson) newsobserver.com/news/local/… #ncpol #nced #wcpss #wakepol
This is great 🔥
The cf cli has reached a 1.0 release candidate!
Introducing cf observability tail, cleaner outputs across the board, and more API consistency.
All the local development and deployment commands are now stable, try them on your wrangler project.
developers.cloudflare.com/ch…
30
James Glenos retweeted
It's still crazy to me how "paste without formatting" is not the default.
Surely I really mean to paste colorful multi-font abomination of a text into email body! Of course, who wouldn't want that!
James Glenos retweeted
Everyone is learning what the infosec dorks and sysadmins have always known - our digital world is fragile and built with little resilience.
Way cool, Vegas, Dec 1-3
come hang with us in vegas. it’s better outside:
cloudflare.com/events/vegas/
2
206
James Glenos retweeted
AWS is scared of @Cloudflare so they kicked us out of Re:Invent. No problem, we’ll just throw a more fun side event in Vegas. Register now: cloudflare.com/events/vegas/
James Glenos 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.
James Glenos retweeted
EmDash 1.5 is here, with collaborative editing.
Your team can now write together in real time. Revisions keep every version you save, new sites stay out of search until launch, and moving from WordPress is smoother.
Here's what's new 🧵

ALT EmDash 1.5 release card. The EmDash logo with "1.5" and "Write together, in real time." sit in a white glow, ringed by rows of grey text lines with a few in collaborators' colors, name flags for Noah, Matt and Maya at line ends, and Ana's cursor just after the tagline. The corners read "New release, November 13, 2026" and "34 community contributors".
James Glenos retweeted
It's hard to describe the massive scale of the waves along the Oregon coast this weekend. The people on the cliff on the left side of the video are standing about 75 feet above the water. Just an incredible thing to witness. Keep watching- the 4th wave is the largest! #orwx
James Glenos retweeted
It’s always a great time chatting with @John_Capobianco. Every conversation feels like a profound lesson, from a friend, who is enormously intelligent and passionate.
Keep teaching and inspiring us John. We need you, and more folks like you.
James Glenos retweeted
Roan got it's first significant snow of the season. I'm glad I didn't skip it.
This platform is nuts. See: this thread
Let’s take this gentleman’s argument at face value that anyone can throw money at rockets and get something like Starship, Falcon or Dragon.
Perhaps he can explain to everyone how SpaceX is able to catch giant starships from orbit with chopsticks and deliver 85% of all Earth payload to orbit with Falcon, while Blue Origin, which started before SpaceX and was funded by the immensely wealthy Jeff Bezos, is not yet able to launch reliably?
Also, why is it that Boeing and Lockheed received several times what SpaceX did from the government for development of their rockets and spacecraft, but the Boeing capsule is still not operational and ULA delivers less than 5% of SpaceX payload to orbit?
I am genuinely curious about these questions.
71
James Glenos retweeted
Don't lose your grip on the dreams of the past. You must fight just to keep them alive!
James Glenos retweeted
No one tells you that parenting is just relearning the world through someone who thinks worms are friends & birds are miracles. It’s the most healing thing I’ve ever done. My daughter looked out the window this morning & said, everything is green & growing. I told her, you too. And something inside me whispered, so are you. Now I’m watching her hold flowers up to the sun while the light bends like it recognizes her. It’s funny, every spring I think I’m teaching my child about the world & every spring she proves she’s the one teaching me how to see it.



































