APNIC IXP pools give Telecom Vanuatu a /26 and /48

APNIC Gave Telecom Vanuatu Two IXP-Pool Prefixes. The Exchange Is Unnamed.

Why it matters

An IPv4 /26 and IPv6 /48 entered APNIC’s register a minute apart on 2 November. Both came from address pools set aside for Internet exchange points; the public objects identify the telecom, but no exchange or peering LAN.

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

APNIC registered a /26 and /48 from IXP-purpose pools to Telecom Vanuatu Limited on 2 November; the exact public records do not name an exchange.

Summary

APNIC’s 3 November daily file records 163.61.162.64/26 and 2001:de9:2000::/48 as Vanuatu assignments dated 2 November, with the same holder ID. The prior file showed both starting points as available.
APNIC identifies both parent pools as reserved for IXP assignments. Current RDAP names Telecom Vanuatu Limited for the exact /26 and /48, but gives no exchange or peering-LAN name.

Sixty-four IPv4 addresses can tell a larger institutional story than a million unlabelled ones. In APNIC’s 2 November file, 163.61.162.64 lay in available space. In the 3 November file, it is a Vanuatu-coded, 64-address assignment dated 2 November. The same file records an IPv6 /48 beginning at 2001:de9:2000::, also coded VU, assigned that day, with the same opaque holder ID. The earlier IPv6 row had been available.

The pools supply the purpose. APNIC’s published resource-range list sets aside 163.61.160.0/20 for small IXP IPv4 assignments and 2001:de8::/29 for IXP IPv6. Both new prefixes sit inside those ranges. The active IPv4 IXP policy makes /26 the default for a new exchange and confines such addresses to peering use. APNIC’s portable-assignment guidance gives an IXP a minimum IPv6 /48 for its transit LAN.

The IPv4 RDAP object and IPv6 object both say VUTELECOM-VU and point to ORG-TVL1-AP. APNIC’s organisation record expands that to Telecom Vanuatu Limited. The two registration events are 61 seconds apart, at 00:08:34 and 00:09:35 UTC. The registry gives the holder and the resource class precisely. Neither object identifies the exchange, its peering LAN or its participants. An APNIC assignment-case note naming the exchange would fill that gap. For now, the public evidence ends at the company’s name.

Sources: APNIC 3 November file; APNIC resource ranges; IPv4 RDAP; IPv6 RDAP; APNIC policy.