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.
History
The Address Plan Was 87% Full While Most Addresses Were Still Empty: RFC 3194
RFC 3194 put a percentage on the pain of hierarchical addressing. The result looked familiar and meant something unusual: an IPv4-sized plan at 87% Host Density held about 240 million entities, not 87% of 4.3 billion addresses. The metric compared scaling pressure across…
Story
The frozen stack: what DFINFRA's address footprint can and cannot prove
The frozen stack: what DFINFRA's address footprint can and cannot prove 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.…
History
The Broadcast Address Became a Router: RFC 3021
On an ordinary IPv4 subnet, an address whose host bits are all ones had long carried broadcast meaning. RFC 3021 made that same bit pattern identify one router—provided the link really had only two ends and both ends understood the exception.
Global Regional ISP
Who Runs AS17494? A Bangladeshi Telecom Giant Hiding Behind a Registry Description Line
Who Runs AS17494? A Bangladeshi Telecom Giant Hiding Behind a Registry Description Line intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
CASE FILE
A Hong Kong Cloud Company, Its Taiwan Routers, and Two Imclouds
APNIC records place IMCLOUD TECHNOLOGY COMPANY LIMITED in Hong Kong. The internet's routing tables place its traffic in Taiwan. Reconciling those two placements exposes a small operator with a large identity question.
Story
DFINFRA and AS210860: the lifecycle ledger of a silent network
DFINFRA and AS210860: the lifecycle ledger of a silent network 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…
Asia-Pacific National Telecom
Registered, Routed, and Named by a Description Line: What the Public Record Actually Proves About the Operator of AS17494
Registered, Routed, and Named by a Description Line: What the Public Record Actually Proves About the Operator of AS17494 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure…
Story
Where Registration Ends and Operation Begins: Inside the AS216429 Case File
Where Registration Ends and Operation Begins: Inside the AS216429 Case File 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…
Story
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
ARIN’s Draft Defines “Out of Region” Without Defining the Unit
ARIN’s Draft Defines “Out of Region” Without Defining the Unit 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
AFRINIC’s IPv6 Draft Changed What 95% Means
Draft 3 keeps the comfort of a familiar percentage while changing the thing being counted. A future result can be comparable only if it travels with the policy version, denominator and measurement method that produced it.
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.