BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Live Wire

View all briefings
TD Synnex's Share of Autodesk Revenue Fell to 8%—but the Channel Did Not Vanish|ICANN Marked Nameshop’s .IDN Application “Terminated”—Its Board Resolution Said “Withdrawn”|RIPE Atlas Warns of Bad NTP Offsets. Thousands of Connected Probes Still Report Firmware 5120|HPE Used 76m Preferred-Stock Equivalents in Q2 EPS. Conversion Is Still Open|Satellite Ltd's power-backed business tiers need a failure map|ONEOK's US$9bn Class B deal is a shrinking capital claim|W3C Proposes Dropping AT Driver Before ARIA Has Adopted It|VeriSign's .net wholesale fee rises 9.99% to US$12|Everpure Grew 38%. One Cash-Flow Line Absorbed $577 Million|LACNIC’s FORT Guide Skips the Signature Published Beside Its Tarball|ICANN's IRP Translation Draft Requires the Access Request in English|Tractor Supply Added 3.7 Growth Points to a 2.3% Quarter

Lead Report / IETF

A long amber document path passes through glass handoff stations while a precise green timing arc covers only the central editing segment, ending at a bound archival volume.
An RFC publication service can meet every target assigned to the time it controls and still deliver a slow end-to-end result. That is the central governance problem inside the IETF Administration LLC’s proposed replacement service-level agreement for RFC editing and publication. The consultation, opened on 10 August 2026 and accepting feedback through 6 September, draws a defensible boundary around the RFC Production Center’s own clock. But a bounded clock is not the same thing as the author’s journey from accepted document to published RFC. A useful SLA must make both visible without blaming the RPC for delays it cannot control. Unless a source carries another date, current conditions in this article reflect evidence checked on 27 August 2026.

The Proposed RFC SLA Can Pass While Authors Still Wait

An RFC publication service can meet every target assigned to the time it controls and still deliver a slow end-to-end result. That is the central governance problem inside the IETF Administration LLC’s proposed replacement service-level agreement for RFC editing and publication. The consultation, opened on 10 August 2026 and accepting feedback through 6 September, draws a defensible boundary around the RFC Production Center’s own clock. But a bounded clock is not the same thing as the author’s journey from accepted document to published RFC. A useful SLA must make both visible without blaming the RPC for delays it cannot control. Unless a source carries another date, current conditions in this article reflect evidence checked on 27 August 2026.

Read Full AnalysisIETF Intelligence
  1. One compact site tile forks into conflicting allocation fields, then converges on a repaired policy surface with separate one-site and two-site cases plus four boundary tests.

    Story

    ARIN's Single-Site `/48` Lived in an Example Before It Reached the Rule

    One site filled 100% of the `/48`s inside a `/48`. The sentence therefore pointed to `/44`; the example did not. ARIN-2025-7 repairs that small contradiction, and in doing so reveals a larger rule: examples must never become the hidden execution layer of number policy.

  2. A vast scrubbing manifold removes red attack traffic while clean blue traffic narrows through two tunnels, a measurement prism and one customer handoff.

    Global Cloud Services

    A DDoS Scrubbing Contract Must Say Who Delivers the Clean Gigabit

    A mitigation cloud can absorb an attack measured in terabits and still leave one customer's legitimate traffic dependent on a much smaller circuit, tunnel and router. The purchase decision is therefore not only how much hostile traffic the provider can discard. It is what clean traffic the contract obliges the whole delivery chain to carry, where that obligation is measured, and what happens when the platform is healthy but the protected service is not.

  3. A network-resource path passes from an older six-segment timing dial through a visible handoff to a current three-segment dial and controlled recovery point.

    Story

    LACNIC Cut Its Recovery Window to Three Months in 2015. One Procedure Page Still Says Six

    LACNIC has a clean public record of shortening its resource-recovery publication period from six months to three. It also has a current operational page and policy manual that use the shorter clock. The unresolved problem is simpler and more practical: another public procedure page still tells resource holders to plan around six months.

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

Your Phone Is Inside the Satellite Beam—Why Won’t It Send?

HTTPS at the Edge—Without Copying the Master Key

Your Dashboard Is Green—But Did It Miss the Alarm?

88,000 AI Satellites? The Evidence Starts With One

The Databases Were Running. Creating One Wasn’t

497 Tbps Under the Atlantic—But How Much Goes Live?

Texas Has a 474GW Power Queue. How Much Is Real?

Mexico’s New Edge Was Set to Go Live—Why Is It Still “Monitoring”?

6.5M Connected—But Satellite Calls Aren’t Here Yet

Why a 99% Download Can Still Be Corrupted

Three Green Lights. One Slow AI Rack.

64,000 Subscribers on One CPU — What If It Fails?

AI Cut Mobile Slowdowns — But What Did the Average Hide?

Everything Works. But the Network Can’t Trust the Time.

Why NSW’s 75-Day Data Centre Fast Track Comes With a Power Test

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. Brian Carpenter and the Boundary That Needed Proof
  2. Ray Bellis and the Proxy That Had to Forward the Unknown
  3. An IETF Remote Room Is an Access Point, Not a Constituency
  4. The IAB Wants Age Rules to Name Outcomes, Not Freeze a Gatekeeper
  5. The Writ Reached ICANN; the Registry Data Stayed Abroad
  6. ICANN Can Group Two Strings Without Finding Them Similar. What Does the Middle String Control?
  7. After the Silence: What AFRINIC’s 2017 Written Cure Needed to Prove
  8. Three Supporters Would Buy an IETF Appeal a Hearing, Not Prove It Right
  9. The IETF Liaison Role Conveys Consensus; It Cannot Create It
  10. A Date Is Not a Review Window: AFRINIC’s Missing Assessment-to-Agenda Record
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. Mauritania's 2018 ACE Cable Cut Made International Path Diversity an Accountability Test
  5. China Telecom's 2010 Route Leak Made Prefix-Volume Claims an Accountability Test
  6. Linode and AS63949: Cloud Convenience Still Needs Operator Discipline
  7. The Denominator Behind the Uptime Promise
  8. TPG's 2024 voice outage turned emergency-call notification into a change-control test
  9. Amaliy Aloqalar Biznesi Ltd. and the cash-flow test behind local network reliability
  10. Microsoft's 2023 WAN outage turned an unqualified router command into two routing waves
View Market

Membership

  1. The 90-Day Emergency Policy That Kept Domain Registration Data Moving
  2. A Proposed Charter Is Not a Working Group Mandate
  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. The IAB Can Set Architectural Conditions. It Cannot Set Child-Safety Law
  10. Hostinger Operations UAB as Registrar: Can a Business Recover Its Domain When the Administrator Disappears?
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