Topic
Transfer-market Architecture
Within the Topic facet, Transfer-market Architecture 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
EVEO Collected 32,256 IPv4 Addresses. LACNIC Filed Eleven Separate Receipts.
Eleven transfers from ten Brazilian sources put 32,256 addresses under EVEO S.A. The current RDAP records still match all eleven ranges, but the log makes readers assemble the total.
Story
Synergy’s /20 Split Eight Ways Over 259 Days
The last 512 addresses went to Viola Communications in October. ARIN’s ledger now divides the entire 4,096-address strip among eight recipients, with a quarter under RIPE NCC.
Story
A College's Entire 65,536-Address Block Changed Names in One ARIN Line
Franklin and Marshall College's complete /16 went to Modal Labs on 20 October. The registry preserves a 1991 source date and a second-precise 2026 handoff, while the bargain stays private.
Story
APNIC Sent 1,024 Addresses Out and Back in Five and a Half Hours. What Happened to the First Receipt?
Two opposite transfers for one IPv4 /22 appeared in APNIC’s public file on 19 June. Its current registry points back to GLOBECOMM SYSTEMS INC.; the public case link is missing.
Story
LACNIC Moved 17,408 IPs to One Holder. RIS Sees the Small Block, Not the Big One.
Two October transfers have the same source and recipient. The larger /18 last appeared in RIPE’s routing view in August; the /22 is visible to 320 of 322 peers.
CASE FILE
Pledged but Not Seizable: The Registry Gap Inside IPv4-Backed Lending
A US company whose registered name declares the borrowing side of an address trade sits in BTW's directory with two public references and no confirmed network operation. Its name is not evidence that a loan exists. It is, however, the cleanest specimen we have of a structural…
Story
AS9327 Crossed from APNIC to RIPE. The Two Ledgers Name Different Recipients.
APNIC records a RIPE organization handle; RIPE names its current holder. The date shifts by a day, and neither table supplies a case key to join the accounts.
Story
APNIC Logged 21 Transfers to NIXI/YOTTA. The Slash Carries 20 Source Names.
The rows contain 27 separate IPv4 ranges, all now labelled YOTTA in exact RDAP lookups. Counting only the common prefix loses the trail.
Story
A /20 Left LACNIC for ARIN. It Came Back 438 Days Later to Someone Else.
The same 4,096 addresses crossed the registry border twice. A current registration names the final holder; two transfer rows explain the round trip.
Story
ARIN’s ‘Original’ Range Grew Back a /24. The Address Didn’t.
Three October transfers divided a four-part IPv4 span. One log field widened after a part had left; four current registrations keep the ledger straight.
Story
2.17 Million IPv4 Addresses Moved. RIPE’s First Waitlist LIR Had Waited 487 Days.
The registry recorded a busy September for transfers and a longer queue for recovered address space. These numbers belong to different pipes.
Story
RIPE Moved Four Telefonica Tech Blocks in One Second. The Old Names Went With Them.
Four IPv4 allocations from 2009, 2010 and 2019 switched holder references at 09:59:10 UTC. The register kept all 5,120 addresses in place and started a new transfer clock.
Story
TalkTalk’s /16 Left RIPE in Three Pieces. Two Registries Got the Pieces.
One September IPv4 block became three exact transfers in eleven days. RIPE names the source; APNIC adds a recipient and a different kind of source identity.
Story
RIPE Registered Three IPv4 Blocks at 14:29. Its Transfer Table Found Them at 20:00.
A 16:41 capture missed 2,304 addresses already bearing the same registration timestamp. The later public table added exactly three rows, all to one recipient.
Story
APNIC Logged 1,511,424 IPv4 Addresses from “GCSA-20”. ARIN Supplies the Name.
Fifteen ARIN-to-APNIC transfer records point to one source handle, ten recipient names and a source country code of ZZ. A second registry holds the identity behind the handle.
Story
SERRA Got Half a /22 in Two Slips. ANDRA Kept the Other Half.
LACNIC’s 26 October transfer file has two /24 receipts, not one /23. Current RDAP leaves the adjoining /23 with the source and makes the split exact.
Story
ARIN Screens Transfer Brokers and Charges $10,000. The Customer Keeps the Risk.
The registry demands insurance, background checks, references and senior approval before it calls a facilitator qualified. Its program terms put the facilitator’s performance on the customer’s side of the table.
Story
RIPE Logged Seven ARIN Arrivals. Three Went to a US Company.
The 2 November inward-transfer ledger covers 38,400 IPv4 addresses. Salesforce received 11,264 of them with a US country code inside RIPE’s register.
Story
LACNIC Charges $200 to Apply for an IPv4 List It Keeps Behind a Door
The registry offers a place for sellers, buyers and intermediaries to find one another. Entry has a fee, visibility is restricted, and LACNIC expressly declines to audit the intermediaries it lists.
Story
Leap’s Seventh APNIC Transfer Brought an ASN Alongside the Addresses
Leap’s Seventh APNIC Transfer Brought an ASN Alongside the Addresses 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.…