ArcNode's new IPv4 /23 appeared under AS9923, not AS155078

ArcNode Got Its Own ASN. Its New /23 Went Out Under Someone Else’s.

Why it matters

APNIC registered ArcNode’s AS155078, IPv4 /23 and IPv6 /48 on 3 November. Eight hours after RIPE RIS saw no full-table peer carrying the exact /23, 322 of 323 peers saw it with AS9923 as origin. The fresh ASN and IPv6 prefix had no matching announcement in that snapshot. The registry finished its paperwork; the route took another name.

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

APNIC registered three ArcNode resources; RIPE RIS observed the IPv4 /23 under AS9923 while the new ASN and IPv6 /48 had no announcement in the sampled window.

Summary

APNIC’s exact RDAP records name ArcNode (Asia Pacific) Holdings Limited on 202.50.60.0/23, 2001:df7:cdc0::/48 and AS155078, all registered on 3 November 2026.
RIPE RIS saw the exact IPv4 /23 at 0/323 full-table peers at 08:00 UTC and 322/323 at 16:00, with AS9923 as origin. At 16:00 the IPv6 /48 was at 0/314 IPv6 peers, and RIS listed no announced prefixes for AS155078 through that collection time.

The new APNIC entries supplied ArcNode with three identifiers. They did not supply a BGP plot. APNIC’s 4 November delegated original dates the IPv4 /23, IPv6 /48 and AS155078 to 3 November; exact RDAP names one registrant on all three. A separate Theo March article has already joined those registry cards. The next question is what a routing observer actually saw.

At 08:00 UTC on 3 November, RIPE RIS reported zero of 323 full-table IPv4 peers seeing the exact 202.50.60.0/23. At 16:00, 322 of 323 saw it. The reported origin was AS9923, and the response also listed two more-specific /24s with that same origin. ArcNode’s newly registered AS155078 was not the origin of the observed /23. The public RIS announced-prefixes response listed no prefixes for AS155078 through the 16:00 collection.

The IPv6 card had a different clock. The exact 2001:df7:cdc0::/48 registered to ArcNode, but the 16:00 RIS IPv6 sample returned zero of 314 full-table peers and no origin for that prefix. RIPE’s routing-status method defines these as observations at scheduled collection times. It does not timestamp the operator command between 08:00 and 16:00, or identify the agreement behind AS9923’s announcement. A dated routing change record would answer how the handoff was arranged.

Official records: APNIC daily file; IPv4 RDAP; IPv6 RDAP; AS155078 RDAP; RIPE RIS method; IPv4 08:00; IPv4 16:00; IPv6 16:00; AS155078 announcements.