Live Wire
View all briefingsLead Report / Leaders
A traffic ratio can show how packets crossed one boundary during one period. It cannot, by itself, tell two networks whether a direct connection is worth the cost, which routes matter more, or whose policy should decide.
Story
A February staff review of ARIN-2025-3 anticipated more IPv4 Waiting List requests and more ticket work. A September review of the revised text marked the effect on registry operations and services “None.” The rule changed between those assessments; the public record does not say whether that change explains the different answer.
Asia-Pacific Cloud Services
Some companies are hard to write about because the record is thin. Ordos UniCloud Technology Company Limited is hard to write about for the opposite reason: the record is thick, and it contradicts itself. The same name appears in the APNIC registry attached to two autonomous systems that have never announced a single route; in Uptime Institute's awards database as the certified client for exactly one data-center project in Inner Mongolia; and in a commercial aggregator's write-up as a project company of Tsinghua Unigroup's cloud business — an attribution that the registry's own contact fields, which point at ZTE-domain e-mail addresses, do not support, and that the cloud company's own website quietly fails to confirm. This article reconstructs what each layer of the public record actually documents, where the layers disagree, and why none of the disagreement can be resolved from public sources today.
CASE FILE
A registry record can name a company that legally no longer exists — and the people sending abuse reports to it have no way of knowing. Svea's RIPE record still routes complaints across three differently named entities and a third-party mailbox, while the Swedish regulator's finalized SEK 45 million sanction shows what a durable remedy actually looks like.
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
RFC 9933 lets a path request name an SR-Algorithm. For a Flexible Algorithm, however, the number is only a handle: the policy that actually selects a route lives in a winning definition, a metric dictionary, a topology snapshot and an ordered evaluator that can all change underneath it.
Market
A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.
Market / Trends
Overwriting one object can leave several generations on the bill. A shorter minimum duration, a new invoice and a new price each change a different part of that history.
Market / Companies
ARTEMIS compares public BGP observations with an operator’s own model of permitted routing to classify suspicious announcements and respond faster. Its history exposes the harder problem: when visibility is incomplete and a counter-announcement can itself cause harm, speed helps only when authority, evidence and rollback have been prepared in advance.
Governance / NOGS
npNOG describes its mailing list as open, available to anyone and “sometimes moderated”. It also publishes seven content rules. What the reviewed pages do not publish is who moderates, what activates moderation, how a participant is notified or where a disputed decision goes.
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
Africa NOGs
Asia-Pacific NOGs
Asia-Pacific NOGs
North America NOGs
Latin America and Caribbean NOGs
Asia-Pacific NOGs
Europe and Middle East NOGs
History of the Internet
In 1996, an organisation could keep the same prefix after leaving a provider and still become unreachable from part of the Internet. RFC 2008 explained why: the registry record, two providers’ cooperation and the rest of the world’s routing decisions were three different promises.
In 1996, an organisation could keep the same prefix after leaving a provider and still become unreachable from part of the Internet. RFC 2008 explained why: the registry record, two providers’ cooperation and the rest of the world’s routing decisions were three different promises.
Leadership Alliance
A link that explains why a name was filtered looks like a simple act of transparency. By the time it reaches a user, however, a resolver, an application and the user have each made a different decision. The record must preserve all three.
A link that explains why a name was filtered looks like a simple act of transparency. By the time it reaches a user, however, a resolver, an application and the user have each made a different decision. The record must preserve all three.
