Network · data from 2026-11-12
AS139460 Maxindo Mitra Solusi Surabaya
Registry name: MMS-AS-ID - PT Maxindo Mitra Solusi, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139460, 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.117.205.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 103.235.152.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 103.235.153.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 146.196.108.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 146.196.109.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 146.196.110.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 146.196.111.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.35.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.46.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 203.123.56.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 203.123.57.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 103.165.246.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.165.247.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.166.48.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.166.49.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.173.88.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.173.90.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 203.173.91.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS139460: AS139460. 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 (AS139460 isn't in the set, or no route object for AS139460 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 | AS139460 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS139460 | A single AS number, not a set: AS139460 (this network), 21 route objects. | |||||
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 32 are in fix.csv.
- ROA: none11
- Route object: RIR18
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.117.205.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 103.117.205.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.235.152.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 103.235.152.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.235.153.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 103.235.153.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 146.196.108.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 146.196.108.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 146.196.109.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 146.196.109.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 146.196.110.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 146.196.110.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 146.196.111.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 146.196.111.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.35.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 175.103.35.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.46.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 175.103.46.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 203.123.56.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 203.123.56.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 203.123.57.0/24 | No ROA covers it. Add a ROA for AS139460, maxLength 24. |
| Route object: RIR | 203.123.57.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.165.246.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.165.247.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.166.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.166.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.173.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.173.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.173.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139460 whose prefix no peer sees AS139460 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.165.246.0/23 | RADB | Valid |
| 203.173.88.0/23 | RADB | No ROA |
| 2404:3900:1394::/48 | 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.