Summary

  • NEXGENET COMPANY LIMITED (ORG-NGN2-AP), a Myanmar LIR, holds one routing-active autonomous system, AS151210, which announces 103.132.102.0/24 and 103.132.103.0/24 with RPKI-valid route objects and roughly 21 observed peers including a Bangkok exchange presence.
  • Its two sponsored customer ASNs — AS152663, registered for SMART & SHINE COMPANY LIMITED in March 2024, and AS153311, registered for SMMCL in Shan State in September 2024 — originate zero prefixes and are absent from the global routing table.
  • Third-party mirrors disagree on who currently holds AS152663: bgp.tools reproduces the SMART & SHINE record, while robtex and bgp.he.net's embedded whois show NEXGENET with a 2026-07-02 last-modified stamp. The conflict is documented here, not adjudicated.
  • All three ASN records share the same role contacts, maintainer chain and abuse mailbox domain, which concentrates operational identity in the sponsoring LIR regardless of which organisation nominally holds each number.

The sponsoring organisation behind the registration family is ORG-NGN2-AP: org-name NEXGENET COMPANY LIMITED, org-type LIR, country MM, with an address at No. 838-839, Thuzitar Road, corner of Thuzitar 8 Street, North Okkalapa Township, Yangon, an e-mail on the nexgenetwork.com domain and a last-modified stamp of 2023-09-05. That object is the hub of this briefing's subject. https://rest.db.ripe.net/whois?source=APNIC&query-string=ORG-NGN2-AP https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-NGN2-AP

AS151210 (NCL-AS-AP) is the only member of the family doing any visible work. Routing observers record it originating 103.132.102.0/24 and 103.132.103.0/24, both drawn from the 103.132.102.0/23 block, with IRR route objects whose rpki-ov-state reads valid, roughly 21 observed BGP peers, and presence at the BKNIX exchange and Bangkok peering points. https://whois.ipinsight.io/AS151210 For a small Myanmar operator, that footprint — a /23, an IPv6 /48's worth of regional presence, an exchange fabric a border away — is a plausible shape for a functioning local ISP with modest transit purchases.

The two customer ASNs are the inverse. AS152663 was registered on 2024-03-27 under ORG-SSCL4-AP (SMART & SHINE COMPANY LIMITED, org-type OTHER) with NEXGENET as sponsoring organisation, and bgp.tools confirms it is not currently in the global routing table, with zero prefixes originated. https://bgp.tools/as/152663 Hurricane Electric's page is more specific: AS152663 has not been visible in the global routing table since 2024-09-11, announces nothing, and has exactly one observed peer — an IPv6 session with AS151210 itself. https://bgp.he.net/AS152663 That last detail matters: the only trace of AS152663 in live routing is a session to its own sponsor, which is consistent with an ASN configured but never given transit or prefixes to sell onward.

AS153311 shows the same pattern with no ambiguity at all. It is registered to ORG-SA237-AP — SMMCL, org-type OTHER, with an address in Keng Tung, Eastern Shan State — sponsored by ORG-NGN2-AP, with NCLA4-AP as admin-c and tech-c, last-modified 2024-09-02. https://rest.db.ripe.net/whois?source=APNIC&query-string=AS153311 https://whois.ipip.net/AS153311 Both Hurricane Electric and Qrator Radar record zero prefixes, zero observed peers, and no RPKI activity for it. https://bgp.he.net/AS153311 https://radar.qrator.net/as/153311

Here the briefing reaches its principal unresolved question. The mirrors disagree about AS152663's holder. bgp.tools reproduces the original aut-num object: as-name SMARTSHINECOMPANYLIMITED-AS-MM, descr SMART & SHINE COMPANY LIMITED, org ORG-SSCL4-AP, sponsoring-org ORG-NGN2-AP, last-modified 2024-03-27. But robtex's mirror lists the same ASN under as-name NCL-AS-AP with descr NEXGENET COMPANY LIMITED, org ORG-NGN2-AP, and a last-modified stamp of 2026-07-02 — implying a registry-level reassignment to NEXGENET itself. http://iad.robtex.com/as/AS152663.html Hurricane Electric's embedded whois matches robtex's newer record while its own page title still reads SMART & SHINE COMPANY LIMITED, an internal inconsistency that suggests a stale title over a refreshed registry copy. Direct retrieval of the authoritative APNIC object did not succeed in this research run, so this article records the divergence rather than ruling on it. https://rest.db.ripe.net/whois?source=APNIC&query-string=AS152663

One more artifact narrows what AS152663 was ever meant to be. A single route object — 2401:8d20::/32, a customer route in RADB, origin AS152663, registered 2024-04-29 with an rpki-ov-state of not_found — is the only prefix the silent ASN was ever associated with. That object plus HE's report of a single observed IPv6 peer (AS151210) sketches a brief 2024 episode: an ASN registered in March, given an IPv6 route object in April, visible to exactly one peer, and gone from the global table by September.

The mechanism that binds all three records is administrative, not financial in any directly observable way. Every ASN in the family names the same role object NCLA4-AP — literally "NEXGENET COMPANY LIMITED administrator" — as admin-c and tech-c, resolves abuse contact through IRT-NCL-MM to a mailbox on the sponsoring LIR's own nexgenetwork.com domain, validated 2026-07-07, and depends on maintainer objects in NEXGENET's chain. What this shows is that a sponsoring-org relationship concentrates accountability — the person reachable when something goes wrong — in the sponsor, even where nominal holding differs.

What it does not show is control of routing: sponsorship confers no evidenced power to make a customer ASN announce prefixes, as two silent records demonstrate by existing.

The uncertainty register is short but material. The authoritative APNIC objects for all three ASNs were read through mirrors and search excerpts, not through the registry directly; cached mirrors may be stale. BGP visibility figures are point-in-time snapshots from third-party observers. No company filing, transaction record or Myanmar regulator record was obtainable, so every conclusion here is bounded to registry and routing evidence.

The observable conditions that would change this picture are correspondingly concrete: any prefix announcement from AS152663 or AS153311; a change in the sponsoring-org field on either customer ASN; or a consistent authoritative APNIC record for AS152663 that resolves the holder conflict one way or the other. Until one of those occurs, the defensible description of NEXGENET is a small operator running a real, modest network and holding two registrations that have never done routing work — one of which may or may not still belong to somebody else.