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.
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.
James Glenos retweeted
IT network guys gonna love this post 👇
My summary attempt at what actually happened:
• The FAA runs its own private telecom network, FTI. It links radar sites, remote radio sites, towers and ATC centers. It's not the internet, though it rides partly on leased carrier fiber.
• L3Harris has operated FTI for 20+ years and is replacing 5,000+ legacy analog circuits. Its site says ~70% of 4,400 sites are done.
• "Copper to fiber" misses the point. The real change is circuit-switched → packet-switched. A remote site used to hang off a dedicated line. Now it gets a router that joins the shared network.
• During one such cutover, that new router began flooding the network: 1,000+ connection attempts every 4–5 seconds.
• Likely mechanism (not yet confirmed): neighboring routers' control planes get overloaded, routing sessions flap and routes churn. Radar and radio feeds riding the network go unstable. Rerouting can't fix it, because rerouting is the part that's broken.
• Nobody could find the source for ~45 min, so the FAA grounded the whole country out of caution. Isolating that one site fixed it.
• No evidence of a cyberattack. Still unknown: a defective router, or a wrong install or configuration?
• It's happened before. In 2009, a misconfigured Harris replacement router disrupted the FAA's flight-plan system.
• ~30% of sites are still to go. The lesson: a single edge device should never be able to destabilize the core. That means control-plane protection, limits on how far one failure can spread, and staged cutovers with a tested rollback.
James Glenos retweeted
Replying to @etscrivner
I joined Microsoft in the 2013–14 timeframe and was immediately struck by the quiet competence that ran through the place. Engineers, security people (including the physical security team), lawyers, developers, and others were simply very good at what they did. In many niche areas, the person sitting in the role was, quite literally, “the” person in the industry for that domain.
Incident and outage calls reflected the same culture. They were calm, quiet, and professional. I still remember jumping onto a Saturday outage bridge and listening to a group of relatively junior engineers work methodically through their runbooks. When they reached the end of the procedures without a resolution, they pivoted without drama into deep technical troubleshooting well beyond the documented steps.
Security incidents were handled the same way. A call might bring 50 people together, yet an L63 or L64 incident manager would run it with clarity—walking through what was known, identifying the gaps, and tasking items across the company.
There were roughly three kinds of people who made this work. Junior college hires were often brilliant, highly motivated, and full of energy. Mid-career people, many with kids and living on the Eastside in places like Sammamish, served as the steady anchors of their teams—engineers, PMs, and others with a decade or more of experience who were simply good at their jobs. Then there were the longer-tenured employees, some with 30 years at the company. Microsoft valued that longevity. These people knew where systems had come from and what was under the hood; they were respected for what they knew, regardless of level, and were regularly pulled into meetings with senior leaders to walk through hard problems.
Even senior leadership operated in the same spirit. I once got a weekend call from a very well-known Microsoft VP. He was direct and courteous: “Is this X? I’m going through this issue and see that you own a document I’d like to read. Can you give me access? Thanks for the help on a weekend—I really appreciate it.”
Around 2020, that culture began to change, and I left not long afterward. I watched the company part ways with many of the people who had solved some of its most significant problems over the previous 20 years. A large number of my former peers and colleagues left as well. It is no longer the company it once was.
James Glenos retweeted
Your whole weekend does NOT need to be productive. You are allowed to just have a damn Saturday.
James Glenos retweeted
Please I'm begging yall switch to DoT or DoH. Stop using plaintext dns (port 53). Your ISP sees every single website (domain) you visit/query
Some network providers block DoT port (853) but DoH is impossible to block.
In terms of providers, you could go with Cloudflare (they claim they wipe their logs every 25 hours) or for better privacy Quad9 (A swiss non-profit) or Mullvad (no logging at all). You gotta trust someone but way better than trusting your ISP
James Glenos retweeted
Test your routing knowledge !
automateyournetwork.com/arca…
@AutomateIP made this as his example game for the upcoming AutoCon6 workshop
It's a blast!
James Glenos retweeted
WOW!
Sky on fire sunrise over Boone, NC with a fresh blanket of snow on the ground!
Frame it!
James Glenos retweeted
.@Cloudflare is the agentic cloud.
They got the primitives right before agents were even a thing:
Workers → execution
Durable Objects → coordination
D1 → persistence
Everyone’s racing to build agents.
Cloudflare already built the ground they’ll run on.
James Glenos retweeted
GREAT post clarifying FAA’s grounding of flights.
Sorry for the long-ass post, I did some OSINT shit.
I pulled live public flight feeds, weather radar status, and space weather data to see what's actually going on during today's nationwide FAA grounding.
TL;DR: radar, GPS, and weather sensors are all working fine. What broke is the long-distance communications network that lets the FAA's 22 regional air traffic control centers talk to high-altitude planes and hand them off to each other.
When people think of air traffic control, they picture the glass tower at an airport. Those towers only handle takeoffs, landings, and nearby airspace. Once a plane climbs out, it's handed off to one of 22 regional Air Route Traffic Control Centers (ARTCCs) — giant facilities that manage high-altitude cruising traffic across whole regions of the country.
Normally, those 22 centers are regionally isolated: if one loses power or a local fiber line, neighboring centers absorb or route traffic around it. Having all 22 degrade at once is virtually unheard of because it means a shared national backbone failed, leaving no healthy neighbor to take over.
That's why the FAA's Command Center used such stark, blanket wording ("Due to extraordinary circumstances and for reasons of safety... all airports are ground stopped until further notice"*) — it's standard protocol when a national-level freeze has to happen immediately before engineers even know how long repairs will take ("safety issue" means "oh shit, stop" in aviation circles, unlike with AI companies).
All 22 centers losing comms at once is, indeed, "extraordinary circumstances".
Here's what the live data shows:
1. US airspace is emptying out fast.
Normally on a Friday evening, thousands of planes are in the air over the US. In live tracking data from OpenSky Network, the number of airborne planes over the lower 48 is steadily draining as flights land and no new commercial departures take off:
• 6:36 PM EST: 1,083 airborne
• 6:42 PM EST: 1,035 airborne
• 6:49 PM EST: 990 airborne
There are zero emergency distress codes broadcasting.
2. Major airports are, predictably, stacked.
Looking within 30 miles of major hubs around 6:37 PM EST (`adsb.lol`), almost nothing is moving:
• NYC/JFK area: 8 in the air vs. 67 on the ground
• LAX: 14 in the air vs. 40 on the ground
• Dallas (DFW): 7 vs. 36
• Denver (DEN): 13 vs. 29
• Atlanta (ATL): 5 vs. 25
• Chicago (ORD): 9 vs. 24
• DC (DCA): 8 vs. 22
A lot of the coastal airports had to stop accepting diverts.
3. The few planes still taking off are enlightening.
Across the entire US at 6:36 PM, only aircraft were taking off (that is: below 10,000 feet and climbing). They fell into two clear buckets:
• 3 international widebody jets (`DAL281` out of Seattle, `DAL156` out of NYC, and `AFR71E` out of Newark), matching the FAA's note that international flights are being handled case-by-case.
• Small private planes and a couple of business jets flying under VFR (visual flight rules) — essentially, staying below 18,000 feet, where pilots don't need en-route air traffic control clearances.
Honorable mention to the 1 Coast Guard/military helicopter climbing near Tampa, out of 29 military aircraft tracked nationwide.
4. Weather radar isn't down, and there's no solar storm or GPS jamming.
A lot of people wondered if today's FAA ground stop, rumors of a National Weather Service outage, and Microsoft's 365 outage were all connected. Checking the raw feeds:
• Weather radar: 199 out of 208 US Doppler radar stations are actively sending fresh scans (within the last 15 minutes). The "NWS outage" rumors were website and caching glitches, not offline radar hardware.
• GPS & Space Weather: NOAA space weather is completely quiet (`Kp = 0`), and aircraft GPS accuracy readings across the Midwest and Northeast look totally normal.
• Local airport radar & towers: Local FAA ground-station radar broadcasts and local airport control towers are still up and transmitting.
So, local sensors and local towers are fine.
The failure is specifically in the long-haul telecommunications backbone connecting the FAA's 22 en-route centers to their remote radio sites — which is why en-route controller frequencies went quiet while local towers, weather radars, and low-altitude visual flights kept running.
Federal officials say there's no sign of a cyberattack, so we're waiting on the FAA's technical post-mortem for what tripped the national network.
That doesn't rule out a cyberattack as the root cause of the comms outage; it's a "we don't know".
Shoutout to adsb.lol for their free API.
James Glenos retweeted
20 of my favorite photos from Great Smoky Mountains National Park, shot on iPhone.
James Glenos retweeted
Meanwhile, that guy running an out-of-life exchange server that hasn't been rebooted for years...























































