Skip to main content

Lead Report / History

A central origin pavilion presents one misted uncertain opening and one deliberate coral withdrawal boundary, with finite time rings and links extending to independent remote pavilions.
Two dead-looking links can lead to the same empty browser view while making very different claims. HTTP 404 leaves the reason and duration unresolved. HTTP 410 lets an origin say that access ended deliberately, is likely to stay ended, and should change how the rest of the Web maintains its references.

The Link the Origin Asked to Remove: Why HTTP 410 Was Not 404

Two dead-looking links can lead to the same empty browser view while making very different claims. HTTP 404 leaves the reason and duration unresolved. HTTP 410 lets an origin say that access ended deliberately, is likely to stay ended, and should change how the rest of the Web maintains its references.

  1. An incomplete SNMP configuration row with two empty column sockets, held apart from a live bus while a device-side mechanism waits above it

    The Row That Existed Before It Was Ready

    An SNMP manager can write `createAndWait`, yet it can never read `createAndWait` back. What returns may be `notReady`: the row now exists, but the device cannot yet attempt to use it. That asymmetry turned a request into an action and incompleteness into an observable fact.

  2. AI editorial portrait of Sally Floyd beside several packet flows converging on a shared network bottleneck.

    Sally Floyd and the Test That Throughput Alone Could Not Pass

    A faster flow can be a worse network result. Sally Floyd’s work on congestion-control evaluation shows why a headline rate must be tested against delay, loss, fairness, instability, difficult paths and the traffic it displaces before an algorithm earns a wider deployment.

  3. Later IPv4 fragments occupy a transparent reassembly chamber while the empty leading slot remains disconnected from an amber error-report channel

    The Timeout That Could Speak Only After Fragment Zero

    The receiver had pieces of the datagram, an identity for the unfinished whole and a timer measuring how long its memory would remain committed. What it did not have was the beginning. When the timer expired, IPv4 required the state to disappear; whether the failure could speak back to the sender depended on one missing piece whose offset was zero.

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

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 Files Vanished. Did the Internet Go Down?

37 Million Accounts Exposed—What Should You Do?

Fibre, 5G, Satellite—Why Your Business Can Still Go Offline

Your Flight Changed. Did Your Bag?

Google Cloud Capacity Changed. Another Team May Stop

The Cloudflare API Said Success. Nothing Changed

Full Signal. Failed Call

The Sensor Worked—But Did the Warning Reach Anyone?

The Backup Worked—So Why Did the Internet Still Feel Broken?

3 Files Named release.zip — Which One Actually Passed?

One Dot Sent Cookies to the Wrong Website | curl Bug Explained

Zero Alerts. Same Code. What Actually Changed?

Why Waymo Stopped During San Francisco’s Blackout

Archived on GitHub. Still Running in Your App?

Can This Wristband Measure Your Grip? There’s a Catch

An amber value query searches one bounded server while separate cyan DNS name trees remain outside its reach

Governance

The Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY

A DNS request once arrived with no question at all. Instead, it placed a resource record in the Answer section and asked the server to supply every name that matched it. The reversal looked elegant on paper: if an ordinary query mapped a name to a value, an inverse query would map the value back to names. But DNS had distributed its authority by names, not by every possible value stored beneath them. IQUERY could search one server’s memory; it could never establish that the server was the right place to ask or that its list was complete.

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.

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

Market / Companies

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.

AI-generated editorial illustration showing a bespectacled man in a data centre beside Ceph distributed-storage nodes and block, object and file storage symbols.

Market

Sage Weil: The Architect Who Made Distributed Storage Calculable

Sage Weil’s most durable contribution to internet infrastructure was not a storage appliance but an architecture. Ceph used CRUSH to calculate where data belongs and RADOS to spread storage, repair and movement across a cluster. The design helped commodity machines behave like one storage system—and created an operational project that ultimately had to outgrow its founder.

An open legal folder holds NANOG's trademark, domain record, archives, contract and ledger while routers remain outside it.

Governance / NOGS

What, Exactly, Did NANOG Acquire?

NewNOG incorporated in 2010. The 2011 handoff then transferred named NANOG assets to that corporation, giving the forum a legal holder for its name and domain, archives, contracts and financial risk. It made NANOG more durable and its responsibilities easier to locate without making NANOG, Inc. the governor of the autonomous networks gathered around the forum.

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 Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
  2. An Expired Internet-Draft Is Not a Rejected Proposal
  3. The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
  4. The assent that completed AFRINIC’s part of the IPv6 supply chain
  5. The Router That Pointed Sideways: How ICMP Redirect Stayed Local
  6. The Record the Receiver Could Not Hold: How TLS Made Size a Local Claim
  7. The Name TLS Had to Hear Before It Could Hide It: How SNI Made Shared HTTPS Possible
  8. The Memory the Server Sealed for Later: How TLS Session Tickets Made State Client-Carried
  9. The Request Arrived Before the Handshake: TCP Fast Open's Replay Bargain
  10. The Header That Waited Behind Its Data
View Governance

Market

  1. From 200 Days to 47, TLS Renewal Becomes Runtime State
  2. The Zero-Egress Invoice Is Not the Cost of Leaving Scaleway
  3. The Denominator Behind the Uptime Promise
  4. The Default Slice Can Make a 5G SLA Look Healthy
  5. Equinix Fabric and the Limits of Programmable Interconnection
  6. Alkira: Building a Managed Network Across Clouds and Fibre
  7. CoreWeave's Network Must Turn Financed Capacity into Useful AI Uptime
  8. GitHub's Attestation Proves a Build Path, Not a Safe Binary
  9. Monitoring’s FTTH menu exposes where passive access ends and power responsibility begins
  10. Four AS Identities Around Internetmanufaktur Karlsruhe
View Market

Membership

  1. The Message That Chose Failure Over Cleartext
  2. ICANN Wrote a 24-Hour Disclosure Clock. Authentication Decides When It Starts
  3. The Relay That Added Context by Cutting Off the Message
  4. Two Registrations, One Phone
  5. The New Key That Inherited Its Past: What TLS KeyUpdate Could Rotate
  6. The 90-Day Emergency Policy That Kept Domain Registration Data Moving
  7. The Knock That Brought the Client Back
  8. A Proposed Charter Is Not a Working Group Mandate
  9. The Command That Gave Away the Connection: Why SMTP Replaced TURN with ETRN
  10. The Proposed RFC SLA Can Pass While Authors Still Wait
View Membership

Number Resource Society

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

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

An amber request capsule is stopped at a barrier marked 425 before an incomplete handshake ring, while the same capsule passes after the ring closes

The Request That Had to Wait for Proof: Why HTTP Needed 425

TLS 1.3 let returning clients send requests before a new handshake finished. HTTP 425 made replayable early data wait without changing the request itself.

  1. The Receiver That Chose What Came First
  2. The Save That Left the Page Intact: HTTP 204
  3. The Address That Grew Old Before It Died
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.

One IPv4 datagram enters a splitter; three fragments emerge, but only the zero-offset fragment retains both option modules.

The Instruction That Had to Survive the Split

One IPv4 datagram entered a router with two options. Loose Source and Record Route, type 131, had its high bit set. Record Route, type 7, did not. When the router cut the datagram into three fragments, the zero-offset fragment kept both options; the other two kept only the source-route instruction. Their headers were deliberately unequal. One bit had separated state every fragment needed from state whose authority remained with the beginning.

  1. The Address That Needed a Local Footnote
  2. The Host That Learned a Small Routing Table: How IPv6 Ranked First Hops
  3. The Session Ticket Could Not Remember the Protocol
Open Alliance Session