APNIC’s Adjacent /23s: RDAP Names One Holder

APNIC Gave Two Neighbouring /23s Names. RDAP Remembered Only One.

Why it matters

A 2 November allocation put adjacent IPv4 blocks in Indonesia and Bangladesh. The machine-readable lookup names Braintel; the Indonesian holder appears in Whois while RDAP returns a root object.

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

APNIC’s 2 November delegated file records adjacent /23s for Indonesia and Bangladesh; current RDAP resolves them at different levels of specificity.

Summary

APNIC's 2 November delegated file places adjacent 512-address IPv4 blocks in Indonesia and Bangladesh, alongside separate IPv6 and ASN rows.
Exact Whois records name both holders. Current RDAP returns Braintel's Bangladesh objects precisely but broad root objects for the Indonesian resources.

Two fresh address blocks meet at a single boundary. APNIC's extended delegated file dates 43.249.124.0/23 to Indonesia and the neighbouring 43.249.126.0/23 to Bangladesh on 2 November. Each covers 512 IPv4 addresses; together they fill the mathematical 43.249.124.0/22. The same file carries an IPv6 /48 and an ASN for each country. Adjacent numbers make a clean map. They do not make the two recipients partners.

The database answers are less tidy. APNIC Whois names PT Viriya Manggala Abadi on the Indonesian /23, 2001:df7:cc40::/48 and AS155075. It names Braintel Infotech Limited on the Bangladesh /23, 2001:df7:ccc0::/48 and AS155076. The IDNIC Whois query also displays Viriya's exact IPv4 record. In APNIC's live RDAP answer for Indonesia's /23, however, the returned network is IANA-BLOCK, spanning all IPv4 space. The Indonesian IPv6 lookup returns ROOT at ::/0; AS155075 returns an ASN block AS154938–AS155961. The Bangladesh /23 RDAP answer gives the exact block and Braintel's registrant handle. Its IPv6 and ASN answers are exact too.

This matters to anyone who lets a structured lookup finish the investigation. The Indonesian address is already allocated and named in Whois, yet the RDAP record presented to that reader is a root-level envelope. APNIC's RDAP infrastructure notice describes redirects to dedicated NIR hosts; the Indonesian responses point to idnic.rdap.apnic.net. APNIC's NIR policy assigns NIRs responsibility for their records and says the APNIC database server should answer for NIR address space. The public responses at 00:23 UTC establish the mismatch. An exact later RDAP object or an APNIC explanation would establish whether it was a lag or a lasting data path gap. The other primary record checks are: IDNIC AS155075, ID IPv6, BD IPv6, ID AS155075, BD AS155076.