Skip to main content

Lead Report / History

A 1990s university mainframe connects toward CERN while a separate ring links Austrian university campuses and a later IP triangle is faintly drawn.
Austria’s first fixed Internet milestone and its national academic backbone were not the same event: a Vienna–CERN circuit changed protocols in 1990, while ACOnet’s countrywide core remained an X.25 ring until 1992.

The CERN Line Spoke TCP/IP. ACOnet Still Ran X.25: Austria, 1990–92

Austria’s first fixed Internet milestone and its national academic backbone were not the same event: a Vienna–CERN circuit changed protocols in 1990, while ACOnet’s countrywide core remained an X.25 ring until 1992.

  1. An abstract 1990s research workstation and route table show a configured westbound path while the return path remains unproven.

    A Routing Entry Did Not Prove Global Reach: Romania, 1993

    On 9 April 1993, a line in an NSFNET policy-routing update named RO-EARN in Bucharest and listed preferred paths through European and Atlantic networks. A week later, Romania’s ICI says it received notice that NSFNET would route traffic for Romania and calls 16 April the country’s arrival at full global connectivity. The dates sit close together because they describe different things: a route-policy record and a later institutional account of reach.

  2. Conceptual illustration of a Kenyan researcher moving from queued institutional email to interactive Internet access.

    Kenya’s Full Internet Link Came After Years of Email

    Kenya’s full TCP/IP connection in October 1995 did not begin the country’s networked life. It changed what an existing, mostly institutional system could do.

  3. Göran Marby

    Göran Marby left ICANN’s CEO post; his consulting term ran to May 2024

    The Board accepted Göran Marby’s resignation on 21 December 2022, ending his status as ICANN’s president, chief executive and ex-officio director. The next day, a consulting arrangement began under the remainder of his executive agreement. That change of status makes his departure a useful test of corporate accountability: the Board’s authority is visible, but the public evidence about performance pay, reported payments and the contract tail sits in several records with different periods and different levels of detail.

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

Before Emoji: Why We Started Typing :-)

Who Could Step In If an Internet Registry Stops Working?

One Scam Call. How Many Networks?

What Could Your App Leave Behind in a Cloud Move?

Undersea Cables Don’t End at the Beach

The DNS Root Key Changed. Did You Notice?

Tiny Packets, Big Pressure: How DDoS Strains Networks

No Cell Signal. Could One Chip Reach a Satellite?

New Page. Same Shirt. How?

Too Many Updates at Once: What Went Wrong at Azure?

Why India Has Two Broadband Totals

When Banking AI Can Act, Who Approves?

Can AI Data Stay in Light?

The Power Goes Out. How Long Does Your Signal Last?

Your Phone Lands Abroad. What Makes It Connect?

AI editorial portrait of Emile Aben against an illustrative network-measurement backdrop.

Market

Emile Aben and the Trade-Off Behind a Wider BGP Sample

RIPE NCC’s Routing Information Service once treated more peerings as a way to see more of global routing. Emile Aben’s work on RIS makes a harder question visible: when does another BGP peer add a genuinely different view, and when does it mostly add data to store?

AI editorial portrait of Tomek Mrugalski in a restrained network engineering setting.

Governance

Tomek Mrugalski and the DHCPv6 name that points an IPv4 tunnel upstream

A DHCPv6 Reply can carry one fully qualified domain name for a Dual-Stack Lite endpoint. That name tells a customer edge device where it may try to send IPv4 through an IPv6 network; it does not show that DNS resolved, a tunnel formed, translation state exists, or a service answered. The narrowness of that field reveals a larger division of work: the customer side can stay simple because the provider must place, scale, secure, and keep the AFTR service available.

Пустые страницы договора, счетчик использования, счет и бухгалтерская книга соединены прозрачным каналом.

Market / Trends

Intuit’s Sequence deal puts the contract-to-cash handoff on trial

The acquisition gives Intuit a route into negotiated, usage-linked billing. Its value will depend on whether a customer’s terms remain traceable from contract change through invoice and accounting—and whether the customer can still move the records.

Conceptual illustration contrasting a suspended primary cloud operations room, a separated backup vault, and an alternate compute hall.

Market / Companies

IDCF’s outage put the recovery control plane in view

The ransomware incident at IDC Frontier did not prove that IDCF Cloud Backup failed. It did expose a more useful market question: when the ordinary cloud console is stopped, who can reach a copy, authorize its use and supply somewhere to run the restored service?

Three conference microphones stand apart from an organised production desk in a quiet Pokhara meeting room.

Governance / NOGS

Who opens the room? What npNOG-10's welcome order can—and cannot—prove

The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.

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 First NAPTR in the Packet Was Not the First Rule: RFC 3403
  2. One Path, Four Algebras, and One Contagious Unknown: RFC 2215
  3. RFC 9019: A Signed Firmware Manifest Is Not Installation Authority
  4. RFC 9810: The Certificate Was Granted, but Not as Requested
  5. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
  6. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
  7. Why .YU Stayed in the DNS Root Until 2010
  8. The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
  9. The First Ping Was Only One Route: Mauritius’s Internet, 1993–96
  10. The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041
View Governance

Market

  1. Terry Manderson and the Reverse DNS Split That Needed Operators
  2. FiberCop’s fibre gains still need to earn their way into cash
  3. BT bought continuity before clearance; the costs are still being counted
  4. Paul Vixie and DNS RRL: A Response Limit, Not an Identity Test
  5. Arctic Way Adds a Cable. Space Norway Still Has to Prove the Switch
  6. Cloudflare R2’s zero-egress price is not a zero-cost exit
  7. Japan’s virtual hyperscaler still has to become a service
  8. PowerCompute’s 11 MW contract firms only 300 kW at peak
  9. Nick McKeown and the Barrier Reply That Never Saw a Packet
  10. INWIT’s reported buyout would purchase equity, not settle the tower contracts
View Market

Membership

  1. IETF Humming Was a Start, Not a Vote: RFC 7282, 2014
  2. Myanmar’s First Official E-mail Came Before the Public Web, 1997–2001
  3. 3C Datalec’s US$400m forecast still needs a test after construction
  4. Tata Communications’ AI network win leaves payback unproven
  5. Proofpoint’s Varonis deal starts with an overlap inside data security
  6. Adrian Farrel and the Path That Exists Only on the Controller
  7. A Legitimate Packet Can Still Fail the Filter: RFC 3704
  8. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  9. BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518
  10. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
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. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  9. Bayan Telecommunications, AS6648 and the Boundary Between Network Records and Control
  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

Burkina Faso’s Research Network Had Two Routing Centres

Before Burkina Faso’s public Internet service began in 1997, a research network already moved email between local institutions and international research systems. Its design assigned domestic message routing to the École supérieure d’informatique and international routing to ORSTOM, making connectivity a division of work rather than a single gateway.

Conceptual editorial illustration of Burkina Faso’s 1994–1995 research email network, with local institutional routing and international message transfer shown abstractly.

Burkina Faso’s Research Network Had Two Routing Centres

Before Burkina Faso’s public Internet service began in 1997, a research network already moved email between local institutions and international research systems. Its design assigned domestic message routing to the École supérieure d’informatique and international routing to ORSTOM, making connectivity a division of work rather than a single gateway.

  1. The Address List Was Not Permission: DEC’s ARPANET Email, 1978
  2. The Usenet Approved Header Marked a Decision, but Left Identity Open
  3. Zimbabwe’s Early Internet Was a Patchwork of Routes and Gateways
Open History Session

Leadership Alliance

A Cent for Every 320 Bytes: How BELINET Financed Belize’s International Mail

In 1994, the University College of Belize faced an unusual constraint: the international telephone call could cost more than the messages it carried. BELINET pooled institutions around a monthly site fee and a charge for each 320-byte block of international email.

概念性 1994 年伯利兹大学邮件工作台:拨号调制解调器、软盘和打印出的邮件。

A Cent for Every 320 Bytes: How BELINET Financed Belize’s International Mail

In 1994, the University College of Belize faced an unusual constraint: the international telephone call could cost more than the messages it carried. BELINET pooled institutions around a monthly site fee and a charge for each 320-byte block of international email.

  1. Hurricane Andrew Hit Costa Rica’s Internet Route Before It Opened
  2. One IGMP Report Could Prove Presence, Not Headcount
  3. Slovenia’s X.400 Mail Server Went to the Basement During the 1991 War
Open Alliance Session