Skip to content
Morning Briefing · Thursday, July 9, 2026

Agentic NetOps Gets Bold — an AI That Joins the BGP Control Plane

network-automationnetworkingai-mldatacenterscience
Listen to the episode
Agentic NetOps Gets Bold — an AI That Joins the BGP Control Plane
20 min · 117 turns
Plate Ileaf · spine
Schematic leaf-spine fabric — explicit-path traffic flows across the spine plane, pods at the edges.
Top Highlights
№ 01·Top Highlights

Top 3 Highlights

1. NetClaw's Wild Claim: An AI Agent That Joins Your Network as a Live BGP Peer

TL;DR: A solo-maintainer open source project called NetClaw wires a Claude-based agent into full network operations — ITSM-gated changes, source-of-truth reconciliation, and, most strikingly, live participation in BGP, OSPF, and GRE as an actual protocol speaker via scapy — betting on a maximalist tool surface that's the exact opposite of the narrow-tool philosophy behind yesterday's Cisco ThousandEyes writeup.

Key Points:

  • 111 claimed MCP server integrations and 189 "skills," built by a single maintainer (John Capobianco, a known NetDevOps community figure) on Claude plus the OpenClaw framework
  • Changes route through ITSM (ServiceNow) change requests with a baseline → apply → verify → auto-rollback-on-failure cycle
  • Source-of-truth reconciliation cross-references live device state against NetBox and Nautobot, flagging 7 categories of drift with severity scoring
  • The headline claim: the agent can act as a live BGP, OSPF, and GRE protocol speaker via scapy — not just reading tables, but participating in the control plane
  • A companion project, GAIT, provides an immutable per-operation audit trail aimed at SOC 2, PCI-DSS, and HIPAA
  • 598 GitHub stars, 167 forks — real community traction for a one-person project, but zero enterprise validation

So What? Whether or not you trust NetClaw's scale claims — and a single-maintainer project claiming this much should earn real skepticism — the baseline/apply/verify/rollback discipline and severity-scored drift detection are worth stealing for any agent you're piloting against your own NetBox or Nautobot instance. Steal the gate, question the claims.

SourcesGitHub — automateyournetwork/netclaw, arXiv 2607.06786


2. Cloudflare Kills Its Own Leader on Purpose — Telstra Didn't Know It Had One

TL;DR: Cloudflare tested Meerkat, a leaderless consensus system built on the academic QuePaxa algorithm, across more than 330 data centers — and it kept working even when the team repeatedly killed whichever node happened to be "in charge" — the same week a Telstra outage revealed emergency calls, trains, and payment terminals were all silently depending on the same centralized time-keeping tier.

Key Points:

  • Meerkat has no fixed leader and is timeout-free; multiple simultaneous proposals cooperate instead of corrupting each other
  • Cloudflare claims roughly 10x the throughput of Raft-style consensus under adverse network conditions, tested with 50 replicas globally
  • Cloudflare is refreshingly candid that global reads and writes are still "quite poor" from pure consensus overhead — a rare admission most vendor blogs would bury
  • Telstra's 12-hour outage was traced to a "software defect" in time-keeping servers in Sydney and Melbourne — no cyberattack, per Telstra
  • Down simultaneously: Triple Zero emergency calls, Victoria's V/Line train network, and Tyro payment terminals for roughly 80,000 businesses
  • Telstra's own CFO said backup systems "worked as they should" — implying the primary time-sync path failed in a way redundancy never caught

So What? This week, map what silently depends on your time source — NTP, PTP, whatever it is. Telstra's outage is the textbook case of a dependency so boring it never made it onto a redundancy diagram, until it took down three unrelated systems at once.

A distributed system built to survive you killing its own leader on purpose is the opposite of one that goes dark because of a dependency nobody ever diagrammed.

SourcesCloudflare Blog, The Register


3. Same Week, Two Verdicts on AI-Written Work: A Full Rewrite Ships, a PR-Description Ban Lands

TL;DR: NVIDIA and LangChain showed that one piece of "harness" middleware took an open model's file-handling pass rate from 0/3 to 3/3 — evidence that tool and prompt-surface design beats raw model choice — the same week Bun's creator used agentic engineering to rewrite over a million lines of code from Zig to Rust, and Cloudflare/Cap'n Proto engineer Kenton Varda banned AI-written PR descriptions on his team as "worse than useless."

Key Points:

  • NVIDIA/LangChain's Deep Agents harness profile for Nemotron 3 Ultra moved an eval score from 94/127 to 96/127 by adding a single piece of middleware
  • No named baseline model was used for the "matches frontier intelligence" claim — treat that part as marketing until proven otherwise
  • Bun's Zig-to-Rust rewrite ran roughly 5.9 billion uncached input tokens and about $165,000 in API costs over 11 days of monitored iteration
  • The validation method wasn't manual code review — it was an existing test suite with a million assertions acting as the correctness oracle, plus adversarial review passes
  • The same week, Kenton Varda declared a moratorium on AI-written commit and PR descriptions on his team, calling them too granular on code details while missing the higher-level framing reviewers actually need

So What? If you're piloting an internal agent harness, budget real time for tool and prompt design — it moved the needle further here than a bigger model would have. But don't assume that lesson transfers evenly: a million-line rewrite validated against an existing test oracle and a paragraph summarizing intent for a human reviewer have completely different trust profiles.

SourcesNVIDIA Technical Blog, Simon Willison — Rewriting Bun in Rust, Simon Willison — Quoting Kenton Varda


Networking
№ 02·Networking

Networking & Architecture

Plate IInetworking
Schematic leaf-spine fabric — explicit-path traffic flows across the spine plane, pods at the edges.

United Airlines' IP Exhaustion Fix Is a Hybrid-Cloud Lesson, Not Just an AWS Feature Post

TL;DR: United Airlines hit routable IPv4 exhaustion across more than 1,200 AWS accounts during irregular-operations surges, when every autoscaled Lambda, Glue job, and container task competed for the same shared, finite address pool — solved with Private NAT Gateway translating CGNAT space to routable addresses at the VPC boundary.

Key Points:

  • A single Private NAT Gateway handles up to 100 Gbps and 55,000 simultaneous connections per destination
  • The failure mode is specifically hybrid on-prem-to-cloud address translation, not internet egress — the use case most engineers default to when they hear "NAT Gateway"
  • United deployed the fix in weeks, versus the usual multi-week process of negotiating new routable IP allocations

So What? Audit whether your ephemeral compute — Lambda, containerized batch jobs, autoscaled tasks — is consuming routable address space that should be CGNAT-plus-translation instead. This is the rare vendor blog post with real numbers instead of hand-waving.

SourcesAWS Networking Blog


Automation
Plate IIIautomation
Source-of-truth pipeline — intent → diff → apply → verify, idempotent on every revolution.

Standards Bodies Give the "Propose, Then Let a Human Gate It" Pattern an Official Name

TL;DR: A new arXiv paper reports TM Forum, 3GPP, and ETSI converging on agentic AI as the foundation for 6G network management, then proposes "autogenic" network management — systems that write and evolve their own automation software at runtime, rolled out in stages from human-supervised to autonomous.

Key Points:

  • Self-programming means the system generates new automation logic during operation, not just executes pre-written playbooks
  • The proposed rollout — human-supervised first, autonomous later — formalizes the same crawl-walk-run pattern already showing up in vendor-specific work like vExpertAI's digital-twin gating and the Guard Rail Validation framework covered in past weeks
  • This is a standards-perspective position paper, not a shipped implementation — treat the "autogenic" vocabulary as a proposed destination, not a working system

So What? If a vendor NMS or OSS roadmap starts citing TM Forum or 3GPP alignment on self-programming automation over the next year, read it against this baseline rather than treating it as novel — the standards conversation is already here, the working systems aren't yet.

SourcesarXiv 2607.06786

(Automation's flagship story this cycle is NetClaw, above in Top 3 — the framework layer itself was flat: Netmiko, Nornir, and Scrapli all showed zero version movement this cycle, and Scrapli remains stuck on its 2.0.0-rc.15 release candidate three weeks running.)


AI / ML
№ 04·AI / ML

AI & Machine Learning

Plate IVai / ml
Embedding space — clusters carry related concepts; the highlighted query vector pulls its nearest neighbors.

(This domain's main development — the harness-profile/Bun-rewrite/Varda-ban trio — is Top 3 story #3, above. Two minor items are in Quick Takes below.)


Datacenter
№ 05·Datacenter

Datacenter & Infrastructure

Plate Vdatacenter
Datacenter row — per-rack utilization at a glance. Cool colors are slack; warmer fills are pressure.

Omdia: Single AI API Calls Are Swallowing Whole Cloud Layers — and the Billing Model With Them

TL;DR: Omdia's "Global AI Cloud Stack 2026" report argues a single LLM API call now spans four to five traditionally separate cloud-native architecture layers, accelerating a shift from pay-per-layer billing toward pay-per-token pricing.

Key Points:

  • Purely qualitative analyst framing so far — no customer counts, adoption percentages, or dollar figures in the syndicated excerpt
  • Connects directly to this week's recurring thread that AI infrastructure is fundamentally a networking and fabric problem, not just a compute one — see Wednesday's UBEP topology-aware scheduling coverage
  • No major cloud vendor has published a public pay-per-token unified rate card yet — the billing prediction is directional, not confirmed

So What? If architecture and billing really are collapsing to pay-per-token, the fabric moving tokens between what used to be separate cloud layers becomes the entire cost and performance surface — reinforcing that network engineers increasingly own the AI unit-economics curve, not just the app layer.

SourcesData Center Knowledge


Science
Plate VIscience
Field schematic — three-body stability under quasi-equal masses, drawn from the day's central result.

The 1993 Experiment That Detected Life on Earth — Without Defining What Life Is

TL;DR: A Quanta Magazine essay revisits Carl Sagan's 1993 Galileo spacecraft flyby experiment, which correctly concluded Earth is inhabited using only remote-sensing anomalies — and uses it to frame a live, unresolved debate over whether "biological agency" is a real scientific category or an empty one.

Key Points:

  • Sagan's team found three independent anomalies: oxygen and methane coexisting in thermodynamic disequilibrium, narrowband radio emissions inconsistent with natural sources, and a chlorophyll-consistent reflectance edge — none required defining "life" first, just statistically implausible chemistry
  • That same disequilibrium logic underpins how modern exoplanet biosignature searches are designed
  • Researchers remain split on whether organisms are genuine goal-directed "agents" (Kevin Mitchell, Sonia Sultan) or whether that framing just restates known mechanisms in fancier language (James DiFrisco and Richard Gawne's 2025 critique)

So What? Worth a moment of humility for a show that uses the word "agentic" in nearly every episode — biologists can't agree on what agency even means for things that unambiguously have it, and the tech industry is extending the word to LLMs without that debate ever being settled.

SourcesQuanta Magazine


Quick Takes
№ 07·Quick Takes

Quick Takes

  • Ares Management took an undisclosed-size minority stake in Sabey Data Centers via its Secondaries fund — worth noting that "secondaries" money typically buys out existing investors rather than funding new capacity, so treat the accompanying "tripling by 2036" claim as aspirational, not funded.
  • NSF awarded $20 million across five new National Quantum Virtual Laboratory teams — $4 million each over two years — spanning quantum networking, sensing, and fault-tolerant computing. It's a planning-stage funding line, not a power-bill reduction; revisit when any team publishes a real architecture proposal.
  • A rejected 170MW Las Vegas-area data center just pivoted onto adjacent federal land, reusing a Bureau of Land Management environmental review originally written for a solar farm. A 30-day appeal window is running now — full story in today's podcast.
  • NVIDIA published a GPU-accelerated Presto benchmark on GB200 NVL72 hardware, and a Hugging Face post repackaged existing Nemotron datasets as "data for agents" — both are thin on numbers and read as framing exercises rather than new results. Skip unless a stronger version with real baselines surfaces.

SourcesDataCenter Dynamics, Data Center Knowledge, DataCenter Dynamics — Boulder City, NVIDIA Technical Blog, Hugging Face Blog


Watch Today
№ 08·Watch Today

Watch Today

  • The Boulder City → BLM appeal window — if it closes unchallenged, expect this to become a repeatable playbook for developers facing local pushback on data center siting.
  • Scrapli's stalled release candidate — still sitting at 2.0.0-rc.15, three weeks and counting, with no stable cut yet.
  • A real Telstra root-cause analysis — "software defect" in time-keeping infrastructure is not an explanation. Watch for an actual postmortem.
  • NetClaw's real-world track record — single-maintainer claims this large deserve scrutiny before anyone puts them near production control planes.

Automation
№ 09·Automation

Pipeline Stats

Plate VIIautomation
Source-of-truth pipeline — intent → diff → apply → verify, idempotent on every revolution.
  • Domains researched: 6 (network architecture, network automation, AI/ML, security, science, datacenter)
  • RSS digest: thin cycle — 72 articles / 22 feeds, top relevance score 5.2 — heavier reliance on supplemental web search than usual
  • Items published: 8 primary items + 4 quick takes
  • Security: no significant architecture updates this cycle (confirmed via search, not padded)
  • Quality score average: 4.5 / 5
Subscribe

Get the briefing in your inbox.

One email per weekday morning. Same writing, same sources — no audio required.