James Glenos retweeted
Between the spruces, nothing but blue ridges.
Shot on iPhone at Great Smoky Mountains National Park.
James Glenos retweeted
Some of y'all don't have a networking problem. You have an expectations problem.
Some of you are so hungry for an opportunity that you've forgotten how to recognize another human being.
If the only reason you're building a relationship is because you want something, that means you're not building a relationship. You're building a transaction with a long expiration date.
If you treat every single person like they're an agenda item, don't be shocked if they do the same for you.
Creating the relationship is the goal. Everything else after that becomes a byproduct of the relationship. – at Frisco, TX
James Glenos retweeted
A series of outages across a broad spectrum of companies and sectors has many Americans concerned about cybersecurity and their own personal data — but Cloudflare co-founder and CEO Matthew Prince (@eastdakota) says this isn’t “the first scene in a ‘Terminator’ movie.”
Instead, Prince tells CBS Mornings, a majority of the outages are due to artificial intelligence finding new bugs that are “causing us to have to patch more quickly.”
James Glenos retweeted
🚨 Today, Nov 18, at 06:59:34 we saw the first instance of ARTEX and Java4Shell being used from the same IP address. This indicates threat actors are combining new vulnerabilities to carry out attacks.
James Glenos retweeted
Help build a better Internet. That's the mission of @Cloudflare.
blog.cloudflare.com/java4she…
James Glenos retweeted
Just think of what NVIDIA could do if they invested $150 billion back into their business in America.
NVIDIA could build multiple massive new leading-edge fabs. New jobs. Reindustrialization. End the hardware supply crisis.
But nope, they're buying back shares instead.
As I predicted, $NVDA increases their share buy back massively… which should really be invested into the data center buildout, but cfo CEO’s are gonna do cfo things!
NVIDIA BOARD ANNOUNCES $150B INCREASE TO SHARE BUYBACK
Readers added context they thought people might want to know
NVIDIA board authorized an additional $150 billion for share repurchases on September 28 2026. The November 17 earnings release stated the increase occurred in September with $227.3 billion remaining under the program.
investor.nvidia.com/news/press-rel…
investor.nvidia.com/news/press-rel…
James Glenos retweeted
Artifacts now supports local development. You can clone and push with Git CLI, test Workflows locally without touching production, and use the same bindings in `wrangler dev`.
developers.cloudflare.com/ch…
James Glenos retweeted
The cf cli is the easiest way to 10X your @Cloudflare experience with agents
The entire company had a huge push to make thousands of dashboard features available via CLI for agents (and scripting/automation)
If you use cf cli, you may never need to touch the dashboard at all
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…
James Glenos retweeted
Hackers are now using LLMs to continuously scan software updates, spot newly fixed bugs, and build attacks before teams can apply the fix — all without human involvement. That’s according to the latest report from the Google Threat Intelligence Group.
We're helping defenders counter automated threats with Google AI Threat Defense, which combines Gemini and other frontier models to find and fix flaws before attackers can exploit them.
James Glenos retweeted
🚨NC Duke Energy customers, here's what regulators decided Monday:
• The NC Utilities Commission approved Duke's rate increases, starting Jan. 1, 2027.
• The N&O reports increases over two years of 9.3% for Duke Energy Progress (Eastern NC and Asheville) and 9.5% for Duke Energy Carolinas.
• Based on Duke's earlier estimates, a typical Progress home using 1,000 kWh pays about $9.62 more a month in 2027, plus $5.89 more in 2028. On the Carolinas side, it's $6.53, then $4.66.
• Duke's allowed profit (return on equity) is set at 9.8%, lower than it asked for.
One piece of good news: the Commission rejected the data-center deal Duke cut with Big Tech. Data centers will get their own rates, put up deposits for grid upgrades, and pay a charge so families aren't stuck with the cost of power plants built for them.
Duke still has to file its final numbers. Budget for higher bills now.
How much more can your family absorb?
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
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.
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".




























