Summary

  • ARIN's transfer log records 173.234.200.0–173.234.207.255, a /21 of 2,048 addresses, moving from Leaseweb USA, Inc. in ARIN to Leaseweb Deutschland GmbH in RIPE NCC on 29 October 2026. RIPE's incoming table lists the same /21, date and recipient.
  • ARIN RDAP responds with a referral to RIPE for 173.234.200.0 and 173.234.207.255. A query for the immediately next address, 173.234.208.0, stays with ARIN and returns an ARIN /22 record.

Internet registry jurisdiction can change between one address and the next. Ask ARIN RDAP about 173.234.200.0 and it returns an HTTP 303 referral to RIPE NCC. The last address of that /21, 173.234.207.255, also goes to RIPE. Ask ARIN about 173.234.208.0, the immediate successor, and ARIN answers with its own record for 173.234.208.0–173.234.211.255. No map has a line this precise. The line belongs to the address book.

The dated event is in ARIN's 2 November transfer snapshot. A RESOURCE_TRANSFER row says Leaseweb USA, Inc. sent 173.234.200.0–173.234.207.255 to Leaseweb Deutschland GmbH on 29 October 2026, from ARIN to RIPE NCC. That is exactly 173.234.200.0/21, or 2,048 addresses. The row's original_set is wider, from 173.234.144.0 through 173.234.255.255; its transfer_set is only the /21. ARIN's format guide describes these public transfer files. The distinction between original and transferred sets keeps the jurisdictional change from swallowing the whole earlier range.

RIPE publishes its matching side. Its incoming inter-RIR IPv4 table lists 173.234.200.0/21 from ARIN to Leaseweb Deutschland GmbH, dated 29 October, classified POLICY and PERMANENT. The current RIPE RDAP object covers precisely 173.234.200.0–173.234.207.255 and links the registrant to ORG-nA8-RIPE, displayed as Leaseweb Deutschland GmbH. On the other side of the seam, ARIN's /22 object at 173.234.208.0 displays LeaseWeb USA, Inc. Los Angeles as registrant. Similar names may tell a corporate story elsewhere; these records establish the registry boundary.

There is a second seam in the clocks. ARIN dates its transfer row 2026-10-29T14:13:19Z. RIPE's present /21 object records registration at 2026-10-29T13:58:13Z, 15 minutes and 6 seconds earlier. The public fields do not define those timestamps as one shared processing clock. A cross-RIR timeline that silently sorts them into a legal sequence would turn two labeled registry times into an invented account of the transaction. A common processing receipt would settle the order; the address boundary is already settled by both live RDAP answers.

The registry's most consequential decision here is not a country name. It is where a query goes. 173.234.207.255 sends the reader to RIPE; 173.234.208.0 keeps the reader at ARIN. The first belongs to the transferred /21, the second to an adjacent ARIN object. An institution can argue about jurisdiction in paragraphs. These two addresses settle the administrative question in one step each.