Network · data from 2026-11-12
AS135589 Internet Maekhong Network
Registry name: IMNCL-AS-AP - Internet Maekhong Network Company Limited, MM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135589, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 103.13.35.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.129.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.129.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.129.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.129.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 2403:79c0::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS135589: AS-IMNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS135589 isn't in the set, or no route object for AS135589 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS135589 in it | Not covered |
|---|---|---|---|---|---|
| AS-IMNET | APNIC | 0 | 1 | No | 6 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- AS-SET: own ASN1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | AS-IMNET | AS135589 isn't in AS-IMNET (APNIC) once expanded. Add AS135589 to it. |
Route objects not announced
Route objects with origin AS135589 whose prefix no peer sees AS135589 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.129.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.144.8.0/24 | RADB | No ROA |
| 103.144.9.0/24 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.