Seven ARIN–RIPE transfers, seven earlier RIPE holder timestamps

RIPE Stamped Seven New Holders Before ARIN’s Transfer Clock Caught Up

Why it matters

Seven address blocks crossed from ARIN to RIPE NCC on 2 November. In every case, the receiving registry’s exact holder card carries a timestamp five to ten minutes earlier than ARIN’s transfer entry.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

Seven RIPE holder registrations precede the matching ARIN transfer timestamps by 297–611 seconds in public records.

Summary

ARIN’s 3 November transfer export and RIPE NCC’s incoming IPv4 table match seven 2 November cross-registry ranges, totalling 38,400 addresses.
Every exact RIPE RDAP holder object has a 2 November registration event 297–611 seconds before the timestamp in its matching ARIN transfer row. The recipients match across the records; the public files give no shared case-level sequence of steps.

The receiving registry got its cards on the desk first. Seven ARIN-to-RIPE IPv4 transfers dated 2 November have second-level timestamps in ARIN’s export. The exact recipient objects in RIPE RDAP were registered between 4 minutes 57 seconds and 10 minutes 11 seconds earlier. This is a pattern across all seven rows, not one lonely clock quirk.

The largest lead belongs to 153.52.128.0/19: ARIN dates NCR Voyix Corporation’s transfer to GIGAGROUP Sp. z o.o. at 14:04:35 UTC; RIPE’s exact /19 holder record was registered at 13:54:24, ten minutes eleven seconds earlier. DELMARVA ONLINE LLC’s 64.254.88.0/21 reached NexGen Cloud at 14:24:09 in ARIN’s file; its RIPE card says 14:14:53, a nine-minute-sixteen lead.

Three St Mary's University ranges to Salesforce carry one ARIN timestamp, 14:37:52. RIPE created the exact /21 and /19 objects at 14:29:41, and the /22 at 14:29:42. That puts all three about eight minutes ahead. Globenet Cabos Submarinos America Inc.’s M247 /18 leads its ARIN stamp by seven minutes 37 seconds. Dunmore Management’s Zero Services /23 leads by four minutes 57 seconds.

All seven exact ranges and final recipients reconcile. ARIN uses the recipient handle org-zsg3-ripe for the last /23; the RIPE object resolves that to Zero Services GmbH. The NexGen row spells “Limited” in ARIN and “Ltd” in RIPE. Those are label details on matched resources, not extra transactions. The address total is 38,400, counted once per exact, nonoverlapping range.

RIPE’s transfer procedure says the two RIRs update their registries on a specified date after approval. It does not publish the second-by-second handover for these cases. The missing receipt is a shared event log showing when approval, recipient-object creation, source-record retirement and the effective transfer occurred. Without that sequence, the public sees seven matched outcomes and two different clocks. RIPE's RDAP guide identifies these responses as access to RIPE Database registration data.