Network · data from 2026-11-12
AS131769 Mayatama Solusindo
Registry name: IDNIC-MAYATAMA-AS-ID - PT Mayatama Solusindo, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131769, 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.
| 2400:c080:2::/48 | Valid | Nonecovered by 2400:c080::/32 | 636 100% |
| 2400:c080:1::/48 | Valid | Nonecovered by 2400:c080::/32 | 635 100% |
| 103.16.132.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.16.133.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.102.248.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.111.86.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.116.13.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.141.254.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.141.255.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.227.148.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.227.149.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 160.22.177.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.153.20.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.21.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.22.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.23.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 210.87.122.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.177.218.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.102.249.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 103.211.160.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.18.39.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS131769: AS131769. 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 (AS131769 isn't in the set, or no route object for AS131769 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 | AS131769 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS131769 | A single AS number, not a set: AS131769 (this network), 29 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 29 are in fix.csv.
- Route object: none2
- Route object: RIR17
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2400:c080:2::/48 | No route object for it. A route object for 2400:c080::/32 with origin AS131769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131769 in the RIR database for the space. |
| Route object: none | 2400:c080:1::/48 | No route object for it. A route object for 2400:c080::/32 with origin AS131769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131769 in the RIR database for the space. |
| Route object: RIR | 103.16.132.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.16.133.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.248.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.111.86.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.116.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.141.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.141.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.227.148.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.227.149.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.22.177.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.20.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.21.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.22.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.23.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.87.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.177.218.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.249.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131769 whose prefix no peer sees AS131769 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.16.132.0/23 | APNIC, NTTCOM | Valid |
| 103.102.248.0/23 | NTTCOM | No ROA |
| 103.141.254.0/23 | RADB | No ROA |
| 103.177.218.0/23 | RADB | No ROA |
| 103.177.219.0/24 | RADB | Valid |
| 103.227.148.0/23 | APNIC, NTTCOM | Valid |
| 203.153.20.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.153.20.0/23 | NTTCOM, RADB | Valid |
| 203.153.22.0/23 | NTTCOM, RADB | Valid |
| 2400:c080::/32 | RADB | Valid |
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.