Summary
- APNIC's own web-whois records the abuse role AN3144-AP for NEXGENET COMPANY LIMITED (ORG-NGN2-AP) with the mailbox on the sponsor's own nexgenetwork.com domain carrying a validation remark dated 2026-07-07 — the freshest dated accountability signal in the record.
- The holder of AS152663 remains formally unresolved: authoritative RDAP endpoints could not be read directly, and public mirrors now split between a NEXGENET re-registration dated 2026-07-02 and the original SMART & SHINE registration of 2024-03-27.
- A validation remark proves the mailbox was checked by APNIC's tooling on a date. It does not prove that a named human answers it. No person is named anywhere in the record.
NEXGENET COMPANY LIMITED is registered in the APNIC database as a local internet registry in Yangon, at No. 838-839 Thuzitar Road, North Okkalapa Township, with the contact address on the nexgenetwork.com domain and a last-modified stamp of 5 September 2023, according to APNIC's own web-whois interface. https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-NGN2-AP The organisation holds AS151210, a live network that originates 103.132.102.0/24 and 103.132.103.0/24 with roughly twenty observed peers and a Bangkok-area exchange presence, per third-party routing mirrors. https://bgp.he.net/AS151210
The same organisation sponsors two other autonomous systems. AS153311 is registered to SMMCL in Keng Tung, Eastern Shan State, with a contact email on the sponsor's own domain; it originates no prefixes. AS152663 is the problem case. Two mirrors — Hurricane Electric and Robtex — now render its registration as NEXGENET COMPANY LIMITED (ORG-NGN2-AP) with a last-modified timestamp of 2 July 2026, https://bgp.he.net/AS152663 while two others — RTSak and bgp.tools — still reproduce the original SMART & SHINE COMPANY LIMITED registration (ORG-SSCL4-AP) dated 27 March 2024, at the same Thuzitar Road building. https://rtsak.com/en/as-numbers/AS152663
The decisive step — reading the authoritative APNIC RDAP record for AS152663 directly — could not be taken in this investigation; the primary RDAP endpoints returned no readable payload, as they also failed for the previous BTW briefing published 28 September 2026. https://rdap.apnic.net/autnum/152663 What this run adds is that the mirror divergence now has a shape: the newer NEXGENET rendering carries a registry-side last-modified date of 2 July 2026, suggesting the holder question is being resolved inside the registry even though it cannot yet be adjudicated from the outside.
The accountability chain itself is dated and visible. The abuse role AN3144-AP, generated from IRT-NCL-MM, lists the same-domain mailbox with the remark that it "was validated on 2026-07-07", last-modified 2026-07-07T13:18:17Z, maintained by APNIC-ABUSE. https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=AN3144-AP Administrative, technical and abuse responsibility for all three ASNs concentrates on one role object, NCLA4-AP, titled "NEXGENET COMPANY LIMITED administrator" — a role designation, not a legal status. No individual is named. The abuse role's phone field reads a zero-filled placeholder value, while the organisation object carries a Myanmar-format contact number — two different numbers in one record.
What the validation remark establishes is that APNIC's mailbox-validation process touched the address on 7 July 2026 and the object was updated the same day. What it does not establish is whether a person answers, how fast, or with what authority over the network's routing. The route object for AS152663's only observed prefix, 2401:8d20::/32, is maintained by a third-party maintainer, MAINT-AS137557, with RPKI over-claim state not found. http://iad.robtex.com/as/AS152663.html The economic mechanism is familiar from earlier coverage: a small LIR concentrates contact, sponsorship and abuse handling for customer ASNs in a single mailbox, and the observable record tells you when that mailbox was last machine-validated — nothing about the humans behind it.
Sources consulted:
http://iad.robtex.com/as/AS152663.html https://bgp.he.net/AS151210 https://bgp.he.net/AS152663 https://bgp.he.net/AS153311 https://bgp.tools/as/152663 https://btw.media/en/nexgenet-accountability-surface-briefing https://btw.media/en/nexgenet-administrator-routing-asymmetry https://rdap.apnic.net/autnum/151210 https://rdap.apnic.net/autnum/152663 https://rdap.apnic.net/autnum/153311 https://rdap.apnic.net/entity/ORG-NGN2-AP https://rtsak.com/en/as-numbers/AS152663 https://whois.ipip.net/AS151210 https://whois.ipip.net/AS153311 https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=AN3144-AP https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-NGN2-AP
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

