Summary
- APNIC’s 3 November extended original lists
192.68.110.0plus 512 addresses asavailable. Its 4 November original lists that exact /23 asVU,allocated, dated 3 November, with holder codeA91E8525. Exact APNIC RDAP namesVUTELECOM-VU; its registrant record names Telecom Vanuatu Limited. - At
2026-11-04T00:00:00 UTC, RIPE NCC RIS routing status for the exact /23 reports zero of 323 full-table IPv4 peers seeing it. The same response says RIS last saw that exact prefix at2024-03-13T00:00:00 UTC, 966 days earlier. RIPE NCC’s endpoint documentation defines these as collector observations at scheduled snapshots.
A card in the register, a dark panel in the route room
The daily change is as plain as a rubber stamp. On 3 November’s APNIC sheet, 192.68.110.0/23 sits in available stock with no country or holder. On 4 November’s sheet, the same 512 addresses are allocated, coded VU, and carry holder A91E8525. Nothing was split off. APNIC changed the status of the whole interval.
The live registry gives the allocation a human-readable destination. Its exact IP object covers 192.68.110.0–192.68.111.255, calls the network VUTELECOM-VU, and points to ORG-TVL1-AP, Telecom Vanuatu Limited. Registration is timestamped 2026-11-03T00:26:21Z; the last change is 25 seconds later. These are unusually crisp public handles for an allocation that a reader might otherwise know only by an opaque holder code.
Then the second clock refuses to play along. RIPE NCC’s RIS query for the exact /23 at midnight UTC on 4 November has a simple visibility fraction: 0/323. The endpoint also carries a much older memory: it first saw the exact route on 15 February 2012 and last saw it on 13 March 2024. The 966-day gap is measured from that last RIS sighting to the 4 November snapshot. An allocation newly visible in APNIC’s daily file is therefore attached to a prefix with an old routing history and no route at this observation point.
That is a useful distinction for a registry, a network team and anyone trying to attach a network address to a responsible institution. APNIC’s allocation says who has the current resource registration. RIS says what its full-table peers observed in BGP at one scheduled moment. Neither clock supplies the other clock’s missing hand.
A network might announce later, through a different or more specific route, or in places outside this collector set; the present public evidence gives a dated registration and a dated RIS silence.
The same company appeared in an earlier BTW story on two APNIC IXP-purpose prefixes: 163.61.162.64/26 and 2001:de9:2000::/48. This /23 is a different resource and a different allocation. The IXP pair raised the question of which exchange was served. Here the question is when an ordinary 512-address block, already seen in BGP years ago, will have an observable operational life under its current registration.
An APNIC resource-action record would establish why the old available range was allocated now. A dated operator announcement or later RIS snapshot would establish its activation. Until then, the honest ledger has two entries: Telecom Vanuatu holds the exact /23 in APNIC, and RIS’s 4 November panel remained dark.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance





