Live Wire
View all briefingsLead Report / Story
Nine companies asked a federal judge to stop ARIN from revoking their IPv4 records. Five months later, an arbitrator rejected every claim and incorporated a settlement that the public file says is attached—but is not.
ICANN
Consider three applications for new top-level domains. ICANN’s String Similarity Evaluation Panel finds string A visually confusable with string B. It also finds B visually confusable with C. But it does not find A and C confusable with each other. All three applications can still enter the same contention set.
Global Cloud Services Trends
Cloud uptime percentages look like simple guarantees. They are not. As of 22 August 2026, the major public cloud SLAs examined here show something more precise: a bounded mechanism for allocating a narrow slice of outage risk, defined by what is measured, how the service must be deployed, which fees enter the calculation, what the customer must prove, and how far the remedy can travel beyond the affected resource.
Story
LACNIC’s rules ask a first-time operator to show that customers and equipment already justify an address block. Exhaustion then sends that approved need into a private market. The rule is neutral on paper; the sequence is not neutral between a network starting from zero and one that already owns routable inventory.
Member Access
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.
Governance
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.
Market / Companies
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.
Market / Trends
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.
Market
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.
Governance / NOGS
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
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.
Governance, market, and membership branches operating in one integrated intelligence model.
Reporting on address stewardship, representation, and the institutions shaping number-resource governance.
Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.
North America policy and transfer market signals.
Europe governance transparency and accountability monitoring.
Asia Pacific allocation pressure and policy dynamics.
Board legitimacy, election process, and legal continuity.
Institutional adaptation and ICP-2 governance trajectory.
Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.
Asia-Pacific NOGs
Asia-Pacific NOGs
Europe and Middle East NOGs
North America NOGs
Latin America and Caribbean NOGs
Africa NOGs
Asia-Pacific NOGs
North America NOGs
North America NOGs
History of the Internet
Structural context for current governance behavior and infrastructure control models.
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.
Leadership Alliance
Capital, policy, and institutional leadership alignment in cross-border digital systems.
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.
