RIPE transfer table: U.S. recipient, same registry

RIPE Logged a U.S. Recipient. The /20 Stayed in RIPE’s Book.

Why it matters

A 30 October transfer moved 4,096 IPv4 addresses to a U.S.-registered company. RIPE filed it as an internal transfer, and its live database still holds the record.

Theo March2 November 2026Reading Time 2 minLast update: 2 November 2026

RIPE NCC classified the 30 October transfer to a US-registered recipient as within its own service region; its RDAP still holds the /20.

Summary

RIPE’s 30 October internal transfer log moves 85.149.240.0/20 from Euronet Communications B.V. to Argonaut HQ, Inc; the recipient’s legal country code is US.
The 4,096-address block appears in RIPE RDAP with an Argonaut organisation and a 30 October registration timestamp.

One country code can start an expensive argument in the wrong registry. On 30 October, the RIPE NCC allocation-transfer table recorded Euronet Communications B.V. in the Netherlands transferring 85.149.240.0/20 to Argonaut HQ, Inc, whose legal country code is US. It was a permanent POLICY transfer of 4,096 addresses. RIPE placed the row in its within-service-region table.

The current RIPE RDAP object supplies the useful second half: the /20 is registered as US-ARGONAUT-20041006, carries RIPE organisation handle ORG-AHI4-RIPE and was changed on 30 October at 08:03:37 UTC. Its country field says GB. Dutch source, U.S. recipient, British object field, RIPE registry. A four-letter column would have made a poor map of authority.

RIPE’s statistics guide defines the transfer country columns as the organisations’ legal registration countries at processing time. Its transfer policy gives transfers inside its service region a separate section from inter-RIR transfers. The U.S. code therefore identifies a corporate address, while the published transfer classification and the live registry record identify who holds the ledger. The row publishes no price or routing destination.