Skip to main content

Lead Report / History

Веб-сервер 1990-х годов стоит рядом с разветвлённой структурой сайта; условный робот изучает файл в корне. Концептуальная иллюстрация, не историческая фотография.
In 1994, Web robot authors agreed on a modest convention: a server could publish crawler preferences at one predictable address, /robots.txt. The choice made the rule cheap to find and easy to serve, but it also concentrated editing in the site administrator and depended on crawlers choosing to comply.

A Plain File Put Each Site’s Crawler Rules at the Root: robots.txt, 1994

In 1994, Web robot authors agreed on a modest convention: a server could publish crawler preferences at one predictable address, /robots.txt. The choice made the rule cheap to find and easy to serve, but it also concentrated editing in the site administrator and depended on crawlers choosing to comply.

  1. A conceptual chain of Maldivian atolls linked by microwave relays, with a satellite path south and an unjoined local exchange route.

    Telephone Reach Was Not Internet Peering: The Maldives’ Undecided Exchange, 1999–2003

    In 1999, every inhabited Maldivian island had telephone service. Four years later, the national backbone still carried no data protocols, while an Internet exchange remained a discussion without a decision. The distinction matters: a telephone network can span an archipelago without creating local Internet interconnection.

  2. Two input streams pass through differently sized frames toward the same unbranded compute rack, illustrating the shorter hosted context limit.

    Cloudflare’s Clef-flash price cut trades a shorter context window for a lower rate

    Cloudflare has cut Clef-flash’s displayed input rate by 58%, while shrinking the hosted context window by 62.5%. The commercial question is how many real customer requests fit inside the cheaper lane—not how small one company-wide request statistic looks.

  3. Conceptual illustration of IRC expanding through independently run servers.

    IRC Grew by Adding Servers Before RFC 1459 Described It, 1988–93

    Internet Relay Chat moved from an unreliable feature on OuluBox to a network of independently run servers before RFC 1459 described its operating rules in 1993.

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

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?

The First .com Existed Before the Web. How?

Conceptual editorial illustration of multiple Saudi ISP racks converging on one international Internet gateway in 1998.

Governance

Forty Private ISP Licenses, One Gateway: Saudi Arabia’s Internet Opening, 1997–99

Saudi Arabia approved public Internet access in 1997. Two years later, dozens of private providers could sell it—but their international traffic still passed through a government-run gateway, and the date announced for launch marked network activation, not the moment a household could necessarily sign up.

Per Narvinger in a generated network-operations setting with abstract mobile-network displays

Market

Per Narvinger’s Ericsson career now meets the customer-return test

The new CEO has moved through research, product, customer-facing work, software services and network systems. That breadth makes for a compelling résumé, but it also sharpens the question awaiting him: can Ericsson turn technical reach into customer outcomes that recur, survive a full product life cycle and earn a return for both sides?

A small business owner publishes a web app as distinct workload streams reach a shared hosting server; editorial illustration, not a GoDaddy facility.

Market / Companies

GoDaddy’s app host skips the usage meter; the subscription must carry the load

GoDaddy has moved a small business from a private preview to a published Node.js app without charging separately for each request, gigabyte or build minute. That lowers the first deployment hurdle for code made with AI tools; it also makes plan conversion, workload mix and service cost the tests that matter.

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

Market / Trends

UOB’s Singapore cloud plan leaves five-market economics unresolved

The memorandum with AWS sketches a dedicated Singapore environment and the possibility of isolated extensions elsewhere. Until UOB identifies workloads, control boundaries and the number of environments, the announcement describes an option to design a regional operating model—not a cloud bill or a completed migration.

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. A Legitimate Packet Can Still Fail the Filter: RFC 3704
  2. BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518
  3. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
  4. The First NAPTR in the Packet Was Not the First Rule: RFC 3403
  5. One Path, Four Algebras, and One Contagious Unknown: RFC 2215
  6. RFC 9019: A Signed Firmware Manifest Is Not Installation Authority
  7. RFC 9810: The Certificate Was Granted, but Not as Requested
  8. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
  9. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
  10. Why .YU Stayed in the DNS Root Until 2010
View Governance

Market

  1. Adrian Farrel and the Path That Exists Only on the Controller
  2. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  3. IDCF’s outage put the recovery control plane in view
  4. Terry Manderson and the Reverse DNS Split That Needed Operators
  5. FiberCop’s fibre gains still need to earn their way into cash
  6. BT bought continuity before clearance; the costs are still being counted
  7. Paul Vixie and DNS RRL: A Response Limit, Not an Identity Test
  8. Arctic Way Adds a Cable. Space Norway Still Has to Prove the Switch
  9. Cloudflare R2’s zero-egress price is not a zero-cost exit
  10. Japan’s virtual hyperscaler still has to become a service
View Market

Membership

  1. Authorization Was Not Access: CAFE’s Togo Satellite Network, 1997
  2. The Source Shipped in March; Mozilla’s Independence Took Five Years
  3. CenpacNet’s Satellite Link Was Not the Whole Internet: Nauru, 1998–2010
  4. Before JAMNet, UWI’s Internet Mail Arrived on Someone Else’s Clock
  5. DENIC Was Founded in 1996. Karlsruhe Ran .de Until 1999.
  6. Uruguay’s .uy Identified Email Before the Internet Link Arrived, 1988–94
  7. Akamai’s Anthropic warrant turns expansion into four vesting gates
  8. A Root Server Moved to London; the Root Zone Did Not: K-root, 1997
  9. When Bulgaria’s Research Network Lost Its External Link, 1997
  10. The LAN Bridge Chose a Root Before a Route: DEC’s Spanning Tree, 1985–86
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. When One Corporate Group Casts Twenty Registry Votes
  10. Digital Identity Requirements at the Registry Gate

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

When the Exchange Became a Service: JPIX and Japan’s Commercial Peering Turn, 1997

Japan’s first commercial exchange was announced with an unusual promise: reliability would be built into a company, a customer service and a second site, while the experimental network it followed would remain a partner. JPIX’s founding shows how the Internet’s shared infrastructure acquired a payer and an operating institution.

A late-1990s exchange switch links two Tokyo facilities across the skyline.

When the Exchange Became a Service: JPIX and Japan’s Commercial Peering Turn, 1997

Japan’s first commercial exchange was announced with an unusual promise: reliability would be built into a company, a customer service and a second site, while the experimental network it followed would remain a partner. JPIX’s founding shows how the Internet’s shared infrastructure acquired a payer and an operating institution.

  1. From Fuzzball PING to BSD ping: Mike Muuss’s 1983 Port
  2. Tonga’s .to Records Reached Abroad While Its 64 kbps Link Was Still Planned, 1996–97
  3. TANet’s No-Transit Boundary: ISP Interconnection Rules, 1996–2006
Open History Session

Leadership Alliance

Four Licensed ISPs, One IAP: Vietnam’s 1997 Internet Opening

Vietnam’s Internet opening is often dated to a single day, 19 November 1997. The more revealing event was a division of authority: four licensed service providers could reach users, while one licensed access provider connected those providers to the international Internet. The law made that boundary visible before the public milestone made it famous.

رسم مفاهيمي لبوابة إنترنت دولية واحدة متصلة بأربعة مزودي خدمات فيتناميين في أواخر التسعينيات.

Four Licensed ISPs, One IAP: Vietnam’s 1997 Internet Opening

Vietnam’s Internet opening is often dated to a single day, 19 November 1997. The more revealing event was a division of authority: four licensed service providers could reach users, while one licensed access provider connected those providers to the international Internet. The law made that boundary visible before the public milestone made it famous.

  1. NUNet Routed Nigerian University Mail Through Abuja and Trieste
  2. When Class C Was Too Large: RFC 1375’s Small-Network Address Proposal, 1992
  3. David Huberman’s Role in ARIN’s Thirteen-Site Test for Direct IPv6 Space
Open Alliance Session