BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
The Indicator Was Defanged. Its Next Consumer Could Still Arm It|The Device Can Last for Years. Its Trust Anchor Cannot Be Treated as a Lifetime Constant|The Space Was Reserved. One Executive Approval Was Still Too Weak: RFC 9812|The IETF Approved Stateful NAT64 as an Internet Standard. The Shared IPv4 Pool Still Needs a Claim Ledger|The Server Never Saw the Password. Its OPRF Seed Still Defined the Blast Radius: RFC 9807|The Registry Closed, but the Packets Still Knock: RFC 9805 and Router Alert's Residual Authority|The CDN Advertised a Ceiling. It Did Not Reserve the Service: RFC 9808|The Certificate Named Four Purposes. The Relying Party Still Had to Separate Them: RFC 9809|The Standard Froze TLS 1.2. The Estate Did Not Disappear: RFC 9851|The Server Set `$istrusted`. The User Still Needed to Know Why: RFC 9979|The Domain Published “Reject.” The Receiver Still Owned the Decision: RFC 9989|The Ping Passed One Tree Instance. The Policy Still Had Other Paths: RFC 9961

Lead Report / Story

An assessment dossier and meeting agenda sit across a blue-to-amber overnight transition, with microphones and a document tray marking the missing public timing record.
AFRINIC’s staff impact assessment for `AFPUB-2026-GEN-002-DRAFT01` is dated 23 June 2026. AFRINIC-37 met on 24 June, with the Policy Compliance Dashboard scheduled for 15:15–16:05 local meeting time. The minutes preserve the PDWG Chair’s concern that providing an assessment only a day before discussion was unfair to the author, but the proposal page preserves no public-posting timestamp. The issue is therefore not whether the assessment was valid or correct. It is whether one exact staff document can be traced from authorship and publication through review, agenda use and the proposal’s next state.

A Date Is Not a Review Window: AFRINIC’s Missing Assessment-to-Agenda Record

AFRINIC’s staff impact assessment for `AFPUB-2026-GEN-002-DRAFT01` is dated 23 June 2026. AFRINIC-37 met on 24 June, with the Policy Compliance Dashboard scheduled for 15:15–16:05 local meeting time. The minutes preserve the PDWG Chair’s concern that providing an assessment only a day before discussion was unfair to the author, but the proposal page preserves no public-posting timestamp. The issue is therefore not whether the assessment was valid or correct. It is whether one exact staff document can be traced from authorship and publication through review, agenda use and the proposal’s next state.

Read Full AnalysisStory Intelligence
  1. A network test bench shows an amber observation path, one red Invalid branch and a cyan recovery loop.

    JPNOG

    The RPKI Trial That Asked How to Fail Safely

    Japan’s 2023 ROV exercise treated recovery as part of the security control, not as an apology after the control went wrong.

  2. An analyst faces three registry clocks beside a separate map of live network routes across Latin America and the Caribbean.

    Story

    LACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network Handover

    A timestamp in a registration record can anchor an investigation, but it cannot substitute for the event the investigator actually needs to prove. LACNIC’s live RDAP data makes that boundary unusually visible: a network object and the entities embedded inside it carry different clocks because each clock belongs to a different object.

  3. Two domain tokens pass through a registrar switchboard and evidence tray, while separate decision paths reach a protected status-change gate.

    ICANN

    The Takedown Notice Did Not Become a Verdict: Petroliam Nasional v. GoDaddy

    The Ninth Circuit did not call every registrar passive or every takedown request futile. It drew a narrower, more useful line: a service provider's ability to maintain and forward a domain name does not create an unwritten ACPA claim that turns notice into adjudicatory authority.

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

Waymo’s Blackout Test: Safe Stops, System Limits

How One Router Took Down Mobile, Internet, Payments & 911

Full Signal. So Why Did the Emergency Alert Never Arrive?

The Phone Had Signal. Why Couldn’t It Call 000?

Same Page. Two Prices. Here’s What Might Be Happening.

1 Tbps Satellite. Why Is Your Internet Still Slow?

The Purge Succeeded. Why Did the Old Price Survive?

Your Domain Still Exists—So Why Is Your Website Down?

Login Alert From Another City? Verify This First

This IP Address Says London. Does That Prove You’re There?

The Cache Was Purged. Why Is the Price Still Wrong?

Delete One Domain, Break Three Websites? RFC 9874 Explained

Same Street, Same Signal — Why Only One Phone Got the UK Emergency Alert

The Fiber Recovered in 12 Minutes. T-Mobile Took 12 Hours.

A 1 Tbps Satellite Is Live. Is Every User Faster?

An unnumbered clock mechanism pauses at a luminous verification gate before the path divides into several independent decision chambers.

Governance

ICANN Wrote a 24-Hour Disclosure Clock. Authentication Decides When It Starts

The most consequential sentence in ICANN's new urgent-disclosure rules is not the one containing “24 hours.” It sits lower on the same policy page, in an implementation note: the obligations become effective when ICANN fully implements a Consensus Policy that establishes requester authentication. Both statements are true. Section 10.7 contains a precise clock for registrars and registry operators, and that clock is not yet an enforceable Section 10.7 clock. The distinction is more than drafting hygiene. It determines when compliance begins, who can start the timer, which request channel counts and what an authentication credential is allowed to prove. ICANN needs an activation receipt that makes the transition visible without turning identity verification into a decision to disclose.

A network engineer checks an isolated router rack linked through a controlled fibre feed-through to production equipment behind glass.

Market / Companies

OVHcloud made anti-DDoS maintenance a BGP-to-OSPF change-control failure

OVHcloud's October 2021 outage began with planned work intended to strengthen anti-DDoS protection, but the public record describes a routing-control failure rather than a successful attack. A command affecting redistribution from BGP into OSPF caused the full Internet routing table to enter the internal routing system, exhausted control-plane resources, broke IPv4 reachability, defeated the attempted rollback, and forced engineers to isolate and power off a router before the network could converge. The incident is a test of whether production change controls govern the routes that actually run, not merely the procedure that was approved.

Two IPv6 packet variants encounter different parser depths along the same network path.

Market / Trends

IPv6 Extension Headers Are Becoming a Path-Compatibility Tax

The address answers. Ping works. Then the transport header moves 64 bytes deeper into an otherwise valid IPv6 packet, and the path goes quiet. Basic reachability survived; optional capability met the smallest parser on the route. It is a compact demonstration of how a protocol feature becomes somebody else’s hardware budget.

Over-the-shoulder view of an anonymous engineer studying abstract finite stack-depth and control-plane constraint graphics on text-free screens.

Market

Jeff Tantsura and the Operational Limits Made Visible by Maximum SID Depth Signaling

Jeff Tantsura's co-authored standards work on Maximum SID Depth shows why path computation needs an accurate record of what a running node can actually impose, carried with enough type and scope to remain useful from the IGP to BGP-LS and PCEP.

A network operations room connects a packet trace, a corroboration record and a separate boardroom decision surface.

Governance / NOGS

The First Packet Is Not the Mandate

An operations archive can show when a crisis first became visible, how competing explanations fared and which repairs appeared to work. What it cannot do, simply by accumulating messages, is turn observation into origin, repetition into consensus or useful advice into institutional command. NANOG's record demonstrates why operational evidence and organisational authority both matter—and why each requires its own chain of proof.

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 Writ Reached ICANN; the Registry Data Stayed Abroad
  2. The Nine Applicants and the Missing Settlement in ARIN Arbitration
  3. ICANN Can Group Two Strings Without Finding Them Similar. What Does the Middle String Control?
  4. After the Silence: What AFRINIC’s 2017 Written Cure Needed to Prove
  5. The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
  6. ARIN’s 28 “Legitimate” Fraud Reports Were Not 28 Findings of Fraud
  7. The Public Query Became a Private Lead Machine: Register.com v. Verio
  8. ICANN Broadened the Project Fund Before Fixing Its Qualification Rule
  9. At LACNIC, the Most Valuable IPv4 Option Is Waiting
  10. LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses
View Governance

Market

  1. Inet Tehno SRL and the cash-flow test behind local network reliability
  2. LymeFiber’s 57-Mile Build Meets Its Real Test at the Pole
  3. EAST STARK-TV LLC and the cash-flow test behind local network reliability
  4. China Telecom's 2010 Route Leak Made Prefix-Volume Claims an Accountability Test
  5. Linode and AS63949: Cloud Convenience Still Needs Operator Discipline
  6. The Denominator Behind the Uptime Promise
  7. TPG's 2024 voice outage turned emergency-call notification into a change-control test
  8. Amaliy Aloqalar Biznesi Ltd. and the cash-flow test behind local network reliability
  9. Microsoft's 2023 WAN outage turned an unqualified router command into two routing waves
  10. AMS-IX's 2023 LACP Leak Made Peering-Fabric Isolation an Accountability Test
View Market

Membership

  1. The 90-Day Emergency Policy That Kept Domain Registration Data Moving
  2. A DDoS Scrubbing Contract Must Say Who Delivers the Clean Gigabit
  3. From 200 Days to 47, TLS Renewal Becomes Runtime State
  4. Telekom Malaysia's 2015 Route Leak Made Upstream Filtering a Transit Accountability Test
  5. The Zero-Egress Invoice Is Not the Cost of Leaving Scaleway
  6. UA Day Built 17 Demonstrations. Production Readiness Needs a Return Visit
  7. When a DNS-Abuse Report Becomes Actionable—and What the Contract Still Does Not Order
  8. C-Root's 2024 Stale Zone Made Publication Freshness a Root-Server Accountability Test
  9. Hostinger Operations UAB as Registrar: Can a Business Recover Its Domain When the Administrator Disappears?
  10. Mauritania's 2018 ACE Cable Cut Made International Path Diversity an Accountability Test
View Membership

Number Resource Society

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

View Number Resource Society
  1. When One Corporate Group Casts Twenty Registry Votes
  2. Digital Identity Requirements at the Registry Gate
  3. A Global South Label Cannot Substitute for a Mandate
  4. A Member Logo Is Not a Live Power of Attorney
  5. A Country Field Is Not an RIR Mandate
  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

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

The internet's hidden roots in military strategy

Structural context for current governance behavior and infrastructure control models.

A central mail receiver chooses between a row of recipient envelopes followed by one body and one body followed by recipient envelopes, then feeds a fixed three-stage rail.

The Receiver That Chose What Came First

Before SMTP, a mail receiver could answer `MRSQ ?` with `215 T Text first, please`. It was asking for the complete message before it learned a single recipient. Another receiver could prefer to collect every address and accept one shared body afterward. This was more than syntax. The choice determined what the receiver had to remember, when a failure became specific to one recipient, and when one reply spoke for a group. SMTP removed that choice from the public dialogue while preserving the economy it was meant to provide.

  1. The Correct Password That Still Needed an Account
  2. The Post That Had to Keep Its Name: How NNTP Bounded a Lost Final Reply
  3. The Missing Page That Was Not Zero: How FTP STRU P Carried Holes Across Hosts
Open History Session

Leadership Alliance

Global AI summit launches as world enters implementation decade

Capital, policy, and institutional leadership alignment in cross-border digital systems.

Zayo Group, LLC and AS6461: What Can a Fiber Backbone Prove About Route Continuity?

A large fiber network can move traffic across long distances, but size alone cannot tell a buyer whether one application, office, data centre or customer circuit will stay online during a failure. Public records around Zayo and AS6461 show why that distinction matters. Registries identify names and number resources. Routing observers show what their collectors could see at particular times. Security records can show whether one route origin was authorised. Company materials describe products, options and operating policies. Each layer is useful, yet none is a substitute for testing the exact service a customer plans to rely on.

  1. CenturyLink's 2018 outage showed how an unused management channel became a national failure path
  2. Sandhills Publishing's AS20005 Control Surface: Routing Records, Dual Data Centers, and Continuity Costs
  3. DENIC's 2026 .de DNSSEC Failure Made Signing-System Parity an Accountability Test
Open Alliance Session