BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
The Anchor Question: What Actually Backs Mistral Compute's 200 MW and 1 GW Forward Commitments|Tideo Administration: The Contact Handle That Outlived Its Network|Mistral Compute's Other Layers: An AS With One Peering Port, and a Grid Line Still in the Ground|Allianz's Cloud Story Lives in One Thai Subsidiary, Not the Group|Novacloud's AS209874: A Routing Footprint the Mirrors Can't Agree On|AI Brazil's Record Two Weeks Later: One Unmoved /22, a Ledger That Reaches Further Back, and the Same Judicial-Recovery Footnote|When the Routes Stop But the Registry Keeps Moving: The AS142207 Timeline After July 2026|NovaCloud-Hosting's paperwork does not match its storefront: the commercial-legal trace BTW had not yet examined|AS151194 and AS203837: the registry record contradicts the directory association|NovaCloud-Hosting's own surfaces contradict themselves: an InStock storefront, a closed-review Trustpilot page and two disagreeing status pages|IRTF’s proposed Net4AI group opens a research lane beyond protocols|Volantis’s $88m round funds the test behind its photonic inference claims
  1. An amber priority seal enters a dark network junction and branches toward a gateway queue, a switchboard, a proxy rack and an endpoint, each applying a different local mechanism.

    History

    The Priority Label Named a Policy. It Did Not Choose the Treatment: RFC 3487

    RFC 3487 designed emergency SIP priority as a reference to local policy, not a remote control that could order every gateway, proxy and endpoint to perform the same act.

  2. Two different symbol streams pass through mapping, normalization, rejection and direction stages, emerging equal while separate identity objects remain unconnected.

    History

    The Strings Matched. The Identity Was Still Unproven: RFC 3454

    Stringprep gave Internet protocols a disciplined way to make internationalized strings comparable. Its four ordered stages could erase, transform, normalize or reject code points until two inputs became character-for-character equal. That equality was valuable, but narrow: it did not prove that two spellings, displays, accounts or people were the same.

  3. A cyan notification arc bypasses a broken middle hop and ends in a receipt ripple while the lower data path remains dim.

    History

    The Alarm Skipped the Failed Hop. The Ack Proved Only Receipt: RFC 3473

    RSVP-TE gained a fast route for telling a distant node about failure, but the acknowledgement at the end of that route was only a receipt for the message—not proof that the network had recovered.

Member Access

Your daily intelligence edge starts here

Strategic Circle turns infrastructure moves, policy shifts and market signals into a concise briefing in your chosen language—plus the research library and member forum—for USD 20/month.

  • 01Daily intelligence brief
  • 02Governance + market + RIR
  • 03Preference control anytime
Explore Strategic CircleSign In

BTW Media on Air

Selected briefings, interviews, and live sessions from the BTW intelligence team, focused on internet infrastructure, governance, and market signals.

View All

The Network Was Fine. The App Still Failed.

More Investment, Later Delivery

Approved—but Not Under Construction

In Orbit, But Not Live Yet

“Ringing” Doesn’t Mean Their Phone Rang

885 MW Planned—Only 175 MW Leased

$42.253B Loaded—Purchases Grew 1.3%

One ISP Brand, Several Operators

Your Key Can Block Native Replication

One File, Multiple Storage Charges

Zero Egress Isn’t a Free Exit

150ms Faster—But No Backup

Signed Update, Incompatible Device

A Valid Number Doesn’t Prove the Caller

Two Safe Budgets, One Overspend

Two mirrored LDP operation ledgers reconnect across a broken TCP span while acknowledged entries, replay items and a three-step quiescence ring remain distinct.

Governance

The TCP Session Died. The Operation Ledger Had to Reconcile: RFC 3479

RFC 3479 made LDP fault recovery a problem of comparing two durable operation histories after the TCP transcript broke, not a promise that the missing interval had somehow vanished.

Adrian Farrel before an abstract network where a luminous computed route fades before a darker device layer.

Market

Adrian Farrel and the Path That Exists Only on the Controller

A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.

An unbranded data-centre construction hall and substation are separate from an open tract and inactive modular mining containers at blue hour.

Market / Trends

CleanSpark Has a 175 MW Lease, Not an 885 MW Delivered AI Campus

CleanSpark’s June 2026 quarterly filing contains three adjacent but materially different facts. On 10 July it signed a 20-year triple-net infrastructure lease for 175 MW of critical IT load at Sandersville, Georgia. The same counterparty also signed an LOI and exclusivity arrangement over a Texas portfolio of 718 acres with up to 885 MW of secured and planned power capacity. And CleanSpark intends to move the Sandersville site from bitcoin mining to an AI campus, with full mining decommissioning expected during fiscal 2028. The first is a definitive lease. The second is not described as one. The third is a future operating transition. Combining them would replace an execution ledger with a headline number.

Conceptual diagram of Cloudflare R2 object storage, an outward file-transfer route and a separate workspace for inspecting replacement application components.

Market / Companies

Cloudflare R2’s zero-egress price is not a zero-cost exit

Cloudflare lists no charge for outbound transfer from R2 and documents a way to copy objects out. The remaining economic question is what customers must spend—and successfully operate—to turn that export into a working replacement.

Two evidence paths, prior participation and equivalent operational proof, converge on the same event-host readiness standard.

Governance / NOGS

AfNOG’s Host Call Strongly Prefers Prior Workshop Familiarity Without Publishing an Equivalent Path

AfNOG’s dated host call strongly prefers hosts familiar with its workshop requirements through prior participation. The reviewed page does not publish an equivalent proof route for a first-time host.

Editorial position

Why BTW Media exists

  • Reality over advocacy
  • Evidence over sentiment
  • Systems over noise

Internet governance is too often described as theory, consensus, or institutional comfort while operators live with the consequences of structure, scarcity, jurisdiction, and incentives.

BTW shows how the system works when assumptions are tested: clear, uncomfortable, evidence-led reporting that keeps attention on structure rather than drama. Public reporting is published to travel: it may be indexed, quoted, translated, used in search and AI answers, and used to train models so the evidence can shape how infrastructure questions are understood.

Core Architecture

Governance, market, and membership branches operating in one integrated intelligence model.

Governance

  1. The Compression Marker Traveled Hop by Hop, Not End to End: RFC 3486
  2. RFC 3476 Reserved the Numbers, Not the Optical Service
  3. The Field Name Was Standardized. The Payment Was Not Secured: RFC 3505
  4. One Call Release Meant Many Connection Teardowns: RFC 3475
  5. The Voucher Was a Right in a Valid Set, Not a File: RFC 3506
  6. The Route Policy Can Change While Its SR-Algorithm Number Stays the Same
  7. A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
  8. A Registry-Lock Quorum Counts Approvals, Not Independent Authority
  9. The Address Was Borrowed. The Route Was Never Included: RFC 2008
  10. The State Table Was Also a Kill Switch: RFC 2012
View Governance

Market

  1. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  2. Vint Cerf and the Deadline Behind the TCP/IP Cutover
  3. Jason Speers and the Hidden Handoffs Inside a Digital-First ISP
  4. Nurani Nimpuno and the Accountability Layer Behind Number Governance
  5. Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
  6. Daniel Fett and the Issuer Field That Named the Server, Not the Token
  7. Nick McKeown and the Barrier Reply That Never Saw a Packet
  8. Lattice’s US$925m AMI draw is not its US$1bn cash purchase price
  9. William B. Norton and the Metric That Could Not Price a Peer
  10. Kodiak’s 76 MW deal names the load, not its credit
View Market

Membership

  1. Enough Symbols Rebuilt the Object. The Sender Still Did Not Know Who Finished: RFC 3450
  2. The Human Explanation and Machine Report Shared an Envelope: RFC 3462
  3. The Conforming Implementation Would Not Interoperate: RFC 3494
  4. The Optional Part Vanished. Delivery Could Still Succeed: RFC 3459
  5. The 32-Bit Sequence Counted 1.485 Gbps. It Did Not Control Congestion: RFC 3497
  6. The Backup Path Existed. Recovery Was Still a Cycle: RFC 3469
  7. The First Message Borrowed a Dictionary That Could Never Change: RFC 3485
  8. The MIB Remembered the Last Command. It Did Not Prove the Switch Was Still in Effect: RFC 3498
  9. The RFC Listed 100 Numbers. It Did Not Make Them One System: RFC 3499
  10. The Report Went Silent. The Counter Did Not Stop: RFC 3483
View Membership

Number Resource Society

Reporting on address stewardship, representation, and the institutions shaping number-resource governance.

View Number Resource Society
  1. A Trust Anchor Rollover Needs an Acceptance Ledger
  2. A Member Logo Is Not a Live Power of Attorney
  3. A Country Field Is Not an RIR Mandate
  4. An ASN Transfer Needs a Routing-Identity Handover Ledger
  5. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  6. An Unanswered Profile Needs a Reply-State Ledger
  7. The FAQ Answer Needs a Version Date
  8. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  9. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  10. When One Corporate Group Casts Twenty Registry Votes

RIR Watchdog

Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.

Network Operator Group (NOGs)

Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.

View Network Operator Groups

History of the Internet

One Bind Could Own Two Protocol Families: RFC 3493

The inventory said “IPv6 listener.” The kernel could still deliver an IPv4 peer to it, and the difference lived in one option whose effective value was easier to assume than to observe.

Cyan and amber conduits share one listener when an iris is open, then separate into two listeners when it closes.

One Bind Could Own Two Protocol Families: RFC 3493

The inventory said “IPv6 listener.” The kernel could still deliver an IPv4 peer to it, and the difference lived in one option whose effective value was easier to assume than to observe.

  1. The ACK Count Changed. The Byte Count Held the Window Honest: RFC 3465
  2. ToUnicode Never Failed. That Did Not Make the Name Valid: RFC 3490
  3. The Black Hole Exposed the Fault. Flooding Would Have Hidden It: RFC 3488
Open History Session

Leadership Alliance

DHCP Chose the Kerberos Realm Before Kerberos Could Judge It: RFC 3495

In PacketCable provisioning, the first authority to name the Kerberos realm was not Kerberos. It was a DHCP reply.

An amber DHCP stream splits toward cyan provisioning and violet Kerberos realms before separate certificate, ticket and service checkpoints.

DHCP Chose the Kerberos Realm Before Kerberos Could Judge It: RFC 3495

In PacketCable provisioning, the first authority to name the Kerberos realm was not Kerberos. It was a DHCP reply.

  1. The ASCII Tail Encoded Position, Not Meaning: RFC 3492
  2. The NAT Type Was a Snapshot. The Peer Needed a Path: RFC 3489
  3. The Label Left the Packet and Entered the Physical World: RFC 3471
Open Alliance Session