Topic
IPv4 Scarcity Economics
Within the Topic facet, IPv4 Scarcity Economics topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger
RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…
Story
Four Counterparty Pairs Made 89% of RIPE NCC's July IPv4 Transfer Total
RIPE NCC's August member update says 5,935,616 IPv4 addresses were transferred in July, 4,159,744 more than in June. The public transfer tables reproduce both numbers exactly. They also change the meaning of the headline: four repeated from-to pairs account for 5,299,712…
Story
RIPE NCC's 708 Extra Accounts Need a Migration Ledger
RIPE NCC has identified a rare simplification window. Only 410 members now operate more than one Local Internet Registry account, yet their 708 additional accounts keep complexity embedded across registry, billing, compliance and portal systems. Closing an exception is not the…
Story
The 27 August Redline: Reading APNIC’s prop-165 Through Its Assessment Delta
APNIC’s canonical `prop-165` record now points to `prop-165-v004`, published on 27 August 2026, while the Secretariat analysis displayed on that record is expressly introduced as applying to version 3. With the APNIC 62 Open Policy Meeting scheduled for 10 September 2026, the…
Story
The Prefix Must Keep Its History: AFRINIC’s Proposed Pool Decision
Under `AFPUB-2026-IPv4-003-DRAFT01`, one recovered IPv4 block would first enter the temporary `Recovered Pool`. AFRINIC staff would trace its original source-pool category, return it there, classify a partial block proportionally, or send an uncertain origin to the…
Global Regional ISP Trends
Only $57m of Cogent’s Data-Centre Sale Was Free to Move
Cogent received $224.2 million from selling ten former Sprint data centres, yet about $168 million entered a creditor-controlled account and only about $57 million was available for general corporate purposes. The split reveals a company whose fibre, IPv4 leases, acquisition…
Global Institutional Trends
The Registry Receipt Was Not a Price Tape
On 18 August, one Spanish address holder became the offering party in seven RIPE NCC transfer records. What left VODAFONE ONO, S.A. did not travel as one neat block. It was cut into eight prefixes, from /24 slices to a /20, and registered to seven organisations across six…
Story
The Prefix in the Credit File: What a LACNIC Lender Can Actually Recover
An IPv4 block can look valuable on a market screen and still fail a lender’s recovery test. In the LACNIC region, collateral value depends on a chain that joins company authority, applicable secured-transactions law, transfer eligibility, registry recognition and uninterrupted…
Story
Three LACNIC Numbers an IPv4 Accounting Memo Must Not Collapse
An IPv4 transfer can produce a private price, a registry-processing charge and a recurring membership invoice. They may arrive in the same transaction folder, but each number proves something different.
Story
LACNIC Turns IPv4 Value Into a Chain of Proof
An IPv4 block may attract a price, but a board cannot rely on that value until authority, eligibility and the registry change can survive diligence.
Story
At LACNIC, the Most Valuable IPv4 Option Is Waiting
At LACNIC, the Most Valuable IPv4 Option Is Waiting intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Story…
IETF
The quarter-second bargain behind Happy Eyeballs
Happy Eyeballs turned dual-stack connection setup into a managed race. Its success lies in making path failure less visible to users; its cost is that the same success can make broken paths less urgent to repair.
Story
At LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4
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…
Story
The Nine Applicants and the Missing Settlement in ARIN Arbitration
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.
Story
LACNIC's Anti-Fake-IXP Log Has No Event Column
LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…
Story
APNIC Would Remove `/23`; Three Prefix Sizes Still Need Names
One bit separates a `/23` from a `/24`. It also separates 512 IPv4 addresses from 256. APNIC's current initial-LIR test can ask for immediate need for the smaller block and a one-year plan for the larger one. Prop-169 would repair that mismatch. Its replacement noun now needs an…
Story
AFRINIC Draft 2 Can Waive 90%; “Sufficiently Documented” Has No Fields
AFRINIC recorded the second-data-centre trap in 2018. An End User wanted another `/24` for redundancy, had used less than 90% of its existing space and was therefore ineligible. Draft 2 finally names that class of problem, then leaves the proof inside two words: sufficiently…
Story
APNIC's /12 Reserve Turns a /22 Offer Into a Queue
The newest impact assessment for prop-168 starts with a subtraction. APNIC counted 11,729 `/24` units in hand; protecting a `/12` for future transition use would remove 4,096 of them, leaving 7,633 for a wider group of applicants whose combined maximum demand would be larger.
Story
ARIN Lowered One Threshold and Closed Three Doors
The latest ARIN-2025-3 draft makes a smaller network four times easier to count as sufficiently in-region, then bars that same out-of-region justification from the Waiting List, micro-allocations and the IPv6-deployment pool. The argument is no longer only about how much need is…
Story
The Consequential Verb Was Publish: AFRINIC’s Resolution 202201.673 and the Limits of an AS0 Mandate
In January 2022, AFRINIC’s Board ratified a policy that asked the registry to do something concrete with its own cryptographic machinery: identify IPv4 and IPv6 inventory recorded as unallocated or unassigned, create covering AS0 Route Origin Authorisations, and publish the…