Nathan retweeted
Russia experienced its largest aerial attack in modern history yesterday with over 1400 Ukrainian drones fired into its territory including hitting the Crimean bridge.
This is the largest attack since WW2.
Nathan retweeted
Republicans are supposed to be China hawks.
They aren't supposed to be the party giving waivers to sell AI chips to China for essentially nothing in return, while excusing their subversion and demanding that a compromised CEO be given his job back.
What are we even doing?
Nathan retweeted
Thomas Jefferson had a copy of the Quran so he could fully understand the fanatical religious beliefs of the Muslims waging jihad against us, particularly the Barbary Pirates, so he could defeat them. Which he did.
I cannot believe this person is going to be a U.S. Senator.
Nathan retweeted
It's funny that Dan McClellan is spending so much time to expose Wes Huff and yet he's a Mormon. Imagine if he used all that time to investigate Joseph Smith.
Nathan retweeted
The Kerch Bridge connecting Russia with temporarily occupied Crimea has been struck. This has been confirmed by local regime authorities. The traffic has been suspended.
Locals report that one of the spans of the bridge was hit.
Nathan 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.
Nathan retweeted
I know there’s a lot of news going on with Nvidia and the midterms and the FAA debacle but this story that 60 mins (miraculously allowed their journalists to cover given Weiss’ deference to Trump) did about the damage to our bases that Hegseth refuses to tell the American people about is huge. There are so many people in this admin who need to face accountability for their incompetence and crimes and I hope Democrats don’t try to play nice and sweep this under the rug and let Hegseth or Trump get away with what’s happened. Our service members deserve better.
After an Iranian drone hit the U.S. command post where Master Sgt. Nicole Amor was stationed, she was still breathing. Soldiers drove her in an SUV to a local hospital in Kuwait, and her husband says, “They were googling hospitals to try to take some of the soldiers to. That's absurd.”
The Pentagon declined to answer whether the 103rd was denied adequate force protection. cbsn.ws/4AsEbh8
Nathan retweeted
And there you have it
The US has lost its measles elimination status
It took 35 years to achieve
Undone by just 2 years of RFK Jr and MAHA
Absolutely pathetic
EXCLUSIVE: The U.S. has lost its measles elimination status.
with @JenCalfas - free link: wsj.com/health/u-s-loses-mea…
Nathan retweeted
Do you understand what the "halal" process is? The slaughterer starts with the usual Allahu Akbar, then severs the animals windpipe, esophagus, and both jugular veins/carotid arteries while hanging upside down so all the blood drains. This is an inhumae process and another reason islam is a satanic religion of violence. You don't hate these demons enough.
Nathan retweeted
Huh. Look at that … a Republican can call out Trump by name. Perhaps someone can show this to DeSantis.
It's too bad that Trump acts like a mob boss and has a cult following so almost no other Republicans will risk saying these things, telling the truth. Or maybe they agree with Trump's appeasement toward evil dictators & protectionist economic policies and that's why they don't address these things. Who knows for sure since they don't say it.
Mike Pence unloaded on both President Trump and Vice President Vance in his first interview since the GOP's midterm shellacking, calling the results not just a rout but "a reckoning."
Pence rips Trump's tariffs, his administration's handling of the Iran war and what Pence describes as an "air of corruption" surrounding the White House, including the First Family's wealth growing by more than $3 billion. He directly disputes Vance's claim that the war alone cost Republicans Congress, arguing the causes were "much more complex" and that voters were frustrated because the administration "stopped short and didn't finish it."
Pence says the party must recommit to the conservative principles that defined the movement for more than 50 years, charging that "the direction the president has taken our party was roundly rejected by the voters."
Full story here foxnews.com/politics/pence-d…
A brand-new survey from the Portland Metro Chamber says Downtown Portland’s vacancy rate has reached its highest level on record, as businesses close or leave and the area loses workers and customers: bit.ly/4t1qGTk

ALT A city street in downtown Portland with a person crossing the road and buildings lining the street. The image contains text stating: "Portland Metro Chamber Survey: Downtown Portland vacancy rate reaches highest level on record. Loss of about 8,000 downtown workers contributes to area’s economic decline."
Nathan retweeted
None of this happened. NONE OF THIS IS REAL. It's all AI slop. And he is posting it on his garbage platform because he's so far gone he thinks it did.
Nathan retweeted
Nearly $1 MILLION for ONE affordable apartment. Who thinks this is acceptable?
According to the Oregon Journalism Project, Oregon’s Housing Stability Council approved another $30 million for a troubled North Portland development, bringing the total to $56.2 million for 57 apartments. That’s $985,513 per apartment.
Oregonians struggling to pay their mortgage or rent deserve to know: How does spending nearly a million dollars per apartment solve our housing crisis?
Even two members of the state’s own housing council questioned the price and abstained. The funding passed anyway.
Every dollar tied up in an excessively expensive project is a dollar unavailable to help another family. Cost matters. Oversight matters. Results matter.
As your state representative, I want housing dollars to help as many people as possible. That means demanding answers when costs spiral, not simply approving another check.
Calling it “affordable housing” does not make the price tag acceptable. Taxpayers deserve accountability. Families waiting for housing deserve better.
oregonjournalismproject.org/…
Nathan retweeted
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them.
Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem.
What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix.
Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited.
The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked.
But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns.
Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it.
I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't.
Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
Things aren't going well for the GOP since the midterms. The Jensen H. Nvidia scandal makes Trump and his administration look awful, then today's FAA problems and the way it's being handled is a debacle. Duffy handled the press conference terribly, people want to know the status but he kept complaining about Congress. As usual, the way these people act makes everything worse.
Nathan retweeted
Republicans and Democrats playing political theater, pretending to be on opposite sides. #uniparty
































