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
ARIN Used 199 Cleared Blocks to Fulfill 307 Requests. The Split Map Is Missing
ARIN’s July distribution closes one scarcity question and opens an accounting one: the registry says 199 cleared IPv4 blocks fulfilled 307 waiting-list requests, but its public records do not show how the input prefixes were divided into the issued prefixes.
Story
AFRINIC's IPv4 Summary Rose by Two. One Reserved Block Split into Three
AFRINIC's daily file gained two IPv4 records on 9 September. The tempting story is two new allocations. The rows tell a more useful one: a conserved block changed shape.
Story
LACNIC Made Merger Transfer Fees Equal. It Did Not Make the Payment Rules Equal
A price list can make two transactions look alike long before their obligations are alike. LACNIC has put merger, acquisition and name-change transfers on the same published fee bands as ordinary IPv4 transfers and has attached both to an annual inflation clock. Yet the public…
Story
AFRINIC’s IPv4 waiver needs an evidence standard
AFPUB-2026-IPv4-002-DRAFT02 keeps the 90% utilisation rule but opens a difficult decision boundary: when is use below that threshold an unavoidable technical constraint rather than ordinary operational convenience?
Story
AFRINIC’s recovered IPv4 pool needs a quarantine exit receipt
AFRINIC’s draft policy sets a consequential boundary between recovered address space and space that can be allocated. The public record explains the quarantine period, but not yet the block-level evidence trail an operator would need to show why a particular block was released.
Story
AFRINIC's IPv4 Pool Plan Needs Two Ledgers
An AFRINIC draft sets out exact rules for recovered addresses and a post-exhaustion queue. Its procedural history shows why operators also need an exact record of when those rules acquire authority.
Story
ARIN’s Proposed /24 Out-of-Region Rule Needs an Exposure Ratio
Moving the threshold from /22 to /24 would make the qualifying in-region IPv4 footprint sixteen times smaller. That change makes the relevant control question proportional: how much in-region footprint supports how much out-of-region space?
Europe and Middle East Regional ISP Trends
QuickSoft: peering breadth is not the same as service accountability
QuickSoft LLC presents a compact but geographically varied public network footprint. Six operator-maintained exchange records and six prefixes visible to RIPEstat are useful evidence of reachability options. They are not, by themselves, evidence of how a customer service is…
Europe and Middle East Regional ISP Trends
Promsvyaz Engineering: what four more-specific routes reveal about control
A registered address block can look singular in a ledger while behaving as several operational units on the Internet. Promsvyaz Engineering’s records show why buyers should inspect the route beneath the aggregate before treating address count as one asset.
Europe and Middle East Regional ISP Trends
Promservice: the cost of keeping address capacity commercially ready
Promservice Ltd. appears in RIPE records associated with sizeable IPv4 and IPv6 allocations. Yet a dated RIPEstat view did not see two exact aggregate prefixes announced. That contrast is not evidence of failure. It is a due-diligence prompt: registry association, route…
Story
APNIC proposal tests a one-/24 IPv4 bridge for IPv6-only networks
APNIC prop-165 version 4 would let an organisation eligible for an initial IPv6 allocation request one IPv4 `/24` for transitional functions in an IPv6-only deployment. The proposal is still under discussion: its practical significance lies less in the size of the grant than in…
Story
APNIC's Larger IPv4 Delegations Need a Queue Rule Before a Bigger Ceiling
APNIC's prop-168 would let eligible account holders grow toward an aggregated /22 while proposing a separate /12 transition reserve. The proposal defines who may ask and how much they may receive; its own scarcity arithmetic shows why it must also define who goes first when…
Number Resource Society
An IPv4 Transfer Pre-Approval Needs a Registration-and-Expiry Ledger
An IPv4 transfer pre-approval answers a narrow question: how much address space a recipient may qualify to receive during a defined period. It does not identify a source, complete a transfer or prove that the registry has changed.
Story
LACNIC’s IPv4 transfer market and the price of scarcity
IPv4 exhaustion does not end allocation politics. It changes the place where they happen: from the distribution of a free pool to the rules governing transfers of resources that are already held.
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…