Summary

  • NEXGENET COMPANY LIMITED appears in the APNIC whois database as organisation ORG-NGN2-AP, org-type LIR, country MM, with the Yangon address on Thuzitar Road in North Okkalapa Township and a last-modified timestamp of 2023-09-05T02:19:16Z on the organisation object, per the APNIC web-whois output for the handle: https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-NGN2-AP
  • The company's principal autonomous system, AS151210 (as-name NCL-AS-AP), is registered to that organisation and has been observed announcing two IPv4 prefixes — 103.132.102.0/24 and 103.132.103.0/24, carved from the allocated 103.132.102.0/23 block — plus an IPv6 prefix 2001:df2:5fc0::/48, with roughly 21 peers observed and presences at Bangkok-area exchange points: https://bgp.he.net/AS151210
  • Two further autonomous systems carry NEXGENET as the sponsoring organisation but are registered to separate customer organisations: AS152663 to SMART & SHINE COMPANY LIMITED (ORG-SSCL4-AP) and AS153311 to SMMCL (ORG-SA237-AP) — and both are dark, meaning zero prefixes originated and zero peers observed.
  • AS152663 has not been visible in the global routing table since 11 September 2024 according to Hurricane Electric's BGP view: https://bgp.he.net/AS152663
  • The phrase "NEXGENET COMPANY LIMITED administrator" that appears in public databases traces to a specific APNIC role object, NCLA4-AP, which serves as the administrative and technical contact on the company's number resources — it is a registry role designation, not a court-appointed administrator or insolvency marker: https://whois.ipip.net/AS151210
  • One third-party mirror, Robtex, presents AS152663 under ORG-NGN2-AP with a last-modified date of 2026-07-02, directly contradicting the APNIC-derived mirrors that show ORG-SSCL4-AP with last-modified 2024-03-27T08:49:08Z: http://iad.robtex.com/as/AS152663.html
  • The live APNIC RDAP endpoints for the three autonomous systems and the live RIPEstat as-overview responses were not directly retrieved during research, so the current live registry fields remain attributed to mirrors rather than confirmed at source.
  • The next verifiable state change is concrete: either a live RDAP field change on AS152663 or AS153311 (a reassignment, status change or new last-modified), or renewed prefix announcements from either ASN. Until one of those occurs, the honest description is registered, sponsored and silent.

The public record on NEXGENET COMPANY LIMITED is unusually complete for a company of its size, and unusually easy to misread. The company appears in APNIC's whois database under the organisation handle ORG-NGN2-AP as a Local Internet Registry — org-type LIR — registered in Myanmar, with an address at No. 838-839, Thuzitar Road, corner of Thuzitar 8 Street, North Okkalapa Township, Yangon, a phone contact and an e-mail on the nexgenetwork.com domain, and a last-modified stamp of 2023-09-05T02:19:16Z. That organisation object is the anchor for everything else in this record, because the same handle appears as the sponsoring organisation on two other autonomous systems that are not registered to NEXGENET itself. The authoritative whois output for the handle is published by APNIC and was retrieved in mirror form during research: https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-NGN2-AP

An LIR in the APNIC region is a member organisation of APNIC that can allocate number resources to its own customers. The economic significance of that status is straightforward: an LIR sits between the regional registry and end-user networks, and the sponsorship relationship — the sponsoring-org field in a whois record — is the contractual thread that connects a customer's resource to the LIR that vouched for it.

When a reader sees "sponsoring-org: ORG-NGN2-AP" on a Myanmar autonomous system, the reading is that NEXGENET, as an LIR, brought that resource into the registry and continues to hold institutional responsibility for it. The registry record itself says nothing about who operates the network day to day, who pays for transit, or whether any traffic flows at all. Those questions are answered, or left unanswered, by routing data.

The principal network: one live ASN with a small footprint

AS151210 is NEXGENET's own autonomous system. The aut-num record carries as-name NCL-AS-AP, description "NEXGENET COMPANY LIMITED", organisation ORG-NGN2-AP, country MM, and a last-modified timestamp of 2023-05-03T14:21:47Z; independent mirrors of the APNIC whois database reproduce the same fields at https://whois.ipip.net/AS151210 and https://whois.ipinsight.io/AS151210, and Qrator Labs' whois mirror adds the detail that AS151210 sits inside the APNIC ASN block AS150842–AS151865: https://radar.qrator.net/as/151210/whois

What makes this ASN different from the other two in the record is that it is visibly running. Hurricane Electric's BGP view lists 103.132.102.0/24 and 103.132.103.0/24 as prefixes originated by AS151210, described as NEXGENET COMPANY LIMITED, with the underlying allocation being 103.132.102.0/23 from APNIC, status allocated, country code MM. The same view reports roughly 21 observed BGP peers and presences at BGP.Exchange-Bangkok, BKNIX and TH-IX — Bangkok-area exchange infrastructure that a Myanmar network would plausibly use to reach international transit: https://bgp.he.net/AS151210

The address space itself has a documented paper trail in the IRR route-object layer. Robtex's view of AS151210 shows multiple IRR objects for 103.132.102.0/23 and the covering /24s, all with origin AS151210 and rpki-ov-state valid, including an APNIC route object last modified 2025-03-18, an NTTCOM proxy-registered object describing an HGC customer route changed 2023-11-15, and a RADB object describing 103.132.102.0/23 as "Customer route(NEXGENET)" maintained by MAINT-AS137557 with last-modified 2023-11-13T16:19:26Z: http://iad.robtex.com/as/AS151210.html

Two caveats attach to this picture. First, Hurricane Electric's own pages carry an internal inconsistency: the ASN page shows the /24s as announced while a separate page for 103.132.102.0/23 states that the /23 "is not visible in the global routing table" and flags it as a bogon — an apparent collector artifact rather than a state change, but one that illustrates why point-in-time routing snapshots need corroboration. Second, and more consequentially for this article, the live APNIC RDAP record for AS151210 was not directly retrieved during research, so the fields above are attributed to mirrors of the APNIC whois database rather than to a confirmed live read. The RDAP URL that would resolve this is https://rdap.apnic.net/autnum/151210.

Two sponsored customer autonomous systems, both dark

The structurally interesting part of the record is the pair of autonomous systems that NEXGENET sponsors but does not hold in its own name.

AS152663 carries as-name SMARTSHINECOMPANYLIMITED-AS-MM and description "SMART & SHINE COMPANY LIMITED", with an address at Level 2, Room 201, #838, Thuzitar Rd, North Okkalapa Township, Yangon Region — the same building as the NEXGENET organisation object. The registered organisation is ORG-SSCL4-AP, org-type OTHER, country MM, and the sponsoring organisation is ORG-NGN2-AP. The administrative and technical contact is NCLA4-AP and the abuse contact AN3144-AP, with maintainer objects MAINT-NCL-MM for mnt-lower and mnt-routes and APNIC-HM as mnt-by, and a last-modified stamp of 2024-03-27T08:49:08Z. BGP.Tools reproduces this structure and adds registration context — "Registered on 27 Mar 2024", "Network status: Active, Allocated under APNIC" — alongside the operative fact that the ASN "is not currently in the global routing table" with zero IPv4 and zero IPv6 prefixes originated: https://bgp.tools/as/152663

Hurricane Electric's page for the same ASN adds the only datable state change in the entire record: "AS152663 has not been visible in the global routing table since September 11, 2024", with the caveat that some displayed information is from that time, and noting AS151210 NEXGENET COMPANY LIMITED as the related upstream AS and 2401:8d20::/32 as an associated IPv6 prefix: https://bgp.he.net/AS152663

The RTSak aggregator corroborates the ORG-SSCL4-AP registration reading independently: https://rtsak.com/en/as-numbers/AS152663

AS153311 follows the same sponsorship pattern with a different customer. The aut-num record shows as-name SMMCL-AS-MM, description SMMCL, address KYAINGE LATT MYO THIT, NO.(244), (4) QUARTER/KENG TUNG/EASTERN SHAN STATE, SHAN STATE, country MM, organisation ORG-SA237-AP and sponsoring-org ORG-NGN2-AP, with NCLA4-AP again as admin-c and tech-c, and a last-modified stamp of 2024-09-02T19:49:01Z. The organisation object behind it, ORG-SA237-AP, shows org-name SMMCL, org-type OTHER, country MM, and — significantly for the sponsorship relationship — an e-mail on the sponsoring company's own domain, last-modified 2024-08-27T11:30:25Z: https://whois.ipip.net/AS153311

The routing picture here is stark. Hurricane Electric reports zero prefixes originated (all, v4 and v6), zero prefixes announced, and zero BGP peers observed for AS153311: https://bgp.he.net/AS153311

A small unofficial mirror, rg443hh.x10.mx, groups AS151210, AS152663 and AS153311 together under NEXGENET COMPANY LIMITED as the sponsoring organisation, which is accurate at the sponsorship layer but overstates the operational relationship if read carelessly: https://rg443hh.x10.mx/hh/153311

Both RDAP endpoints for these two autonomous systems exist and would resolve the registry fields directly: https://rdap.apnic.net/autnum/152663 and https://rdap.apnic.net/autnum/153311. Neither was directly retrieved during research; every field reported above comes from third-party mirrors of the APNIC whois database, and the article treats them accordingly.

Where "administrator" comes from — and why it is not insolvency

The phrase that anchors this directory card — "NEXGENET COMPANY LIMITED administrator" — invites a wrong reading. In many jurisdictions, an "administrator" is a court-appointed insolvency practitioner; a reader encountering the phrase next to a company name could reasonably conclude the company is under administration. The registry record says otherwise, and it says so precisely.

The APNIC whois database contains a role object with nic-hdl NCLA4-AP, whose role line reads "NEXGENET COMPANY LIMITED administrator", with the same Thuzitar Road address in North Okkalapa Township, the same phone contact, an e-mail on the nexgenetwork.com domain, and a last-modified timestamp of 2023-05-03T06:31:01Z. That role object serves as the admin-c and tech-c — administrative and technical contact — on AS151210, AS152663 and AS153311 alike. In registry terms, a role object is a named contact point, and the "administrator" wording in its role field describes the contact function within the company's own registry administration, not any legal status. Every autonomous system in this record names that same role object as its contact: https://whois.ipip.net/AS151210

The distinction matters economically. An insolvency administrator would imply control transferred, creditor processes underway and asset disposals possible. A whois role handle implies none of those things; it implies only that the same operational contact manages registry objects for the organisation. No public record retrieved during research indicates insolvency, receivership, licence revocation or restructuring. The misreading risk is real because aggregators copy the role-object name into organisation fields, and the phrase then propagates into search results detached from its registry context.

The unresolved contradiction: who holds AS152663 now?

One source in the retained set contradicts the rest, and this article flags it rather than resolving it. Robtex's page for AS152663 presents the object as NCL-AS-AP / NEXGENET COMPANY LIMITED under ORG-NGN2-AP, with a last-modified stamp reported as 2026-07-02T06:52:24Z. That reading conflicts with the APNIC-derived mirrors (BGP.Tools, RTSak, ipip.net) that show ORG-SSCL4-AP / SMART & SHINE COMPANY LIMITED with last-modified 2024-03-27T08:49:08Z: http://iad.robtex.com/as/AS152663.html

Two explanations are plausible and are not mutually exclusive. The first is a mirror defect: the Robtex page appears to re-use template fields from AS151210 — the same as-name and organisation — which would make it a mis-keyed or stale mirror rather than evidence of a registry transfer. The second is a live registry event: a reassignment of AS152663 from ORG-SSCL4-AP back to ORG-NGN2-AP sometime after March 2024, which would be a genuine state change with a 2026 timestamp. The resolution requires a direct read of the live RDAP record, which research could not obtain: https://rdap.apnic.net/autnum/152663

This is exactly the kind of unresolved question that should be settled before any stronger claim is made about NEXGENET's sponsorship book. If the live record still shows ORG-SSCL4-AP, the contradiction is a mirror artifact and the article's framing stands unchanged. If it shows ORG-NGN2-AP with a 2026 last-modified, then the sponsorship relationship has been dissolved or internalised and the operational story changes. The article takes no position beyond stating the conflict and naming the test.

What the routing data can and cannot prove

The routing measurements carry their own epistemic limits, and the RIPEstat documentation states them precisely. The as-overview endpoint's "announced" field is true only if the ASN originates prefixes visible to at least ten RIS full-feed peers — a transit-only ASN would report false even while carrying traffic — and the "holder" field returns the descriptive name of the ASN holder from the RIR, or null if unregistered: https://stat.ripe.net/docs/data-api/api-endpoints/as-overview

The live as-overview responses for the three ASNs were not directly retrieved during research; the documented endpoint is https://stat.ripe.net/docs/data-api/api-endpoints/as-overview. This matters for one specific inference: the absence of announcements in Hurricane Electric's collectors for AS152663 and AS153311 does not strictly prove the networks are dormant — it proves that no routes from them were observed in those collectors. The distinction is narrow in practice, because zero prefixes and zero peers across the major collector networks is a strong dormancy signal, but it is a measurement fact, not a corporate status fact.

The corporate layer adds self-published claims that sit outside the registry evidence and are attributed as such. The company's own website, https://www.nexgenetwork.com/, states that NexGeNet Company Limited was founded in 2015, is a Network Facilities Service (individual) and International Gateway licensee of Myanmar's Posts and Telecommunications Department under the Ministry of Transport and Communications, and is a wholly-owned subsidiary of Crystal Shine Group. No independent confirmation of current licence status surfaced in this research pass, and nothing in the registry or routing record speaks to licence standing either way.

The economic reading: a sponsorship-only LIR footprint

Pull the layers together and the state difference at the centre of this article becomes legible. NEXGENET is a registered, current LIR with one live autonomous system of modest scale — two /24s and an IPv6 /48, roughly 21 peers, exchange presences in Bangkok — and a sponsorship book of two customer autonomous systems, both registered in 2024, both carrying the same contact objects, and both silent in the global routing table, one since a datable date of 11 September 2024.

Three mechanisms explain how such a configuration arises, and the record does not yet distinguish between them. First, customer provisioning in progress: an LIR sponsors ASNs for customers whose networks are built but not yet announcing, in which case the dark record is a snapshot of a pipeline, not a failure. Second, churn or abandonment: customers registered resources, never operated them or stopped operating them, and the sponsor retains the registry relationship without an operating network behind it.

Third, corporate-group structuring: the shared building address for ORG-NGN2-AP and ORG-SSCL4-AP, and the nexgenetwork.com e-mail on the SMMCL organisation object, suggest the "customers" may be affiliated entities within the same group — Crystal Shine Group, per the company's own website — in which case the sponsorship book maps group structure rather than commercial sales.

Each mechanism has a different economic implication. A pipeline implies growth ahead; churn implies wasted registration overhead and a sponsorship book that should be pruned; group structuring implies that NEXGENET's LIR function is an internal service to affiliated networks, not a market-facing business line. The observable that separates them is the same one named above: a live RDAP field change, or a renewed announcement. The APNIC whois search interface at https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-SSCL4-AP would show whether the SMART & SHINE organisation object has changed, and the parallel query for the SMMCL object at https://wq.apnic.net/apnic-bin/whois.pl?form_type=advanced&searchtext=ORG-SA237-AP would show the same for AS153311's registered organisation. Neither live read was obtained during research; both mirrors point to the March 2024 and August–September 2024 timestamps respectively.

The bounded consequence is therefore modest and precise. NEXGENET's visible market position — one small live network plus a silent two-ASN sponsorship book — is a real but thin infrastructure footprint, and no public evidence supports reading the "administrator" tag as corporate distress. The falsifiable test of any stronger narrative — distress, restructuring, expansion — is a registry or routing change, and until one occurs the defensible statement is exactly what the record shows.