Summary

  • APNIC logs AS9327 leaving One New Zealand Group Limited for the RIPE NCC region at 01:49 UTC on 20 October, with ORG-KNL2-RIPE in its recipient field. RIPE NCC’s incoming ASN table dates the APNIC arrival 19 October and names Joseph Abley.
  • RIPE’s organization record resolves ORG-KNL2-RIPE to Jump Networks Ltd, while its current AS9327 object points to a different organization record for Joseph Abley. The two transfer tables offer no public join key that explains the handoff between those labels.

An autonomous system number has one numerical identity. Its two registries have managed to give its arrival two human ones. APNIC’s transfer file records AS9327 moving out of One New Zealand Group Limited on 20 October 2026. The destination cell does not name a company. It says ORG-KNL2-RIPE, marks the economy ZZ, and points to RIPE NCC. Open RIPE’s organization object for that exact handle: it names Jump Networks Ltd in the United Kingdom. So far, the reader has an outbound row and a resolvable destination handle.

Now open RIPE NCC’s incoming inter-RIR ASN table. Its AS9327 row names APNIC as the source RIR, Joseph Abley as the recipient, the Netherlands as the destination country, and 19 October as the transfer date. Same number and direction; different recipient label and date. RIPE’s current AS9327 registration supports RIPE’s recipient name: its registrant reference is ORG-JA630-RIPE, whose organization record names Joseph Abley. The descriptive AS name, STRANDKIP, is a separate field. None of these strings is interchangeable merely because it appears beside the same ASN.

The clocks add a smaller but useful puzzle. RIPE’s aut-num object was created at 14:38:59 UTC on 19 October and last changed four minutes and 15 seconds later. APNIC’s row gives 01:49:18 UTC on 20 October, 11 hours, 10 minutes and 19 seconds after the RIPE registration event. RIPE’s transfer table gives only a calendar date, 19 October. These may be distinct processing or publication clocks; neither table defines a shared case timestamp. Compressing them to “transferred on 20 October” or “transferred on 19 October” quietly chooses one institution’s clock.

There is a material difference between a receiving account, a registered holder, an intermediary and a transfer log’s label. The public records here identify none of those roles for Jump Networks Ltd beyond the fact that ORG-KNL2-RIPE resolves to it. RIPE’s table and current object both name Joseph Abley. A public case record linking the outbound handle, the RIPE recipient and the effective time would explain the relationship. Until then, the honest ledger has two recipient labels. It does not have a proved chain between them.

This is not a question that requires privileged routing telemetry. APNIC publishes a transfer log with from and to columns. RIPE publishes an incoming table and describes its inter-RIR transfer procedure. Each institution supplies the raw pieces. The missing piece is an explanation that lets an operator match the same border crossing across both records without guessing which name describes which role. A transfer log is most useful precisely when the resource has crossed an institutional boundary; this one makes the reader do the institution’s reconciliation work.