Network · data from 2026-11-12
AS55669 MCS-AS-ID - PT. Maxindo Content Solution
Registry name: MCS-AS-ID - PT. Maxindo Content Solution, ID · not in PeeringDB
10IPv4 routes
0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
10No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
69Route objects not announced
registered with origin AS55669, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55669, 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.244.96.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 103.244.97.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.244.98.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.244.99.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 119.110.79.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.48.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.49.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.55.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.58.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 175.103.59.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
AS-SET
AS55669 isn't in PeeringDB, where networks name their AS-SET.
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 89 are in fix.csv.
- ROA: none10
- Route object: RIR10
- Route object: not announced69
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.244.96.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 103.244.96.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.244.97.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 103.244.97.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.244.98.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 103.244.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.244.99.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 103.244.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 119.110.79.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 119.110.79.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.48.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 175.103.48.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.49.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 175.103.49.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.55.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 175.103.55.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.58.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 175.103.58.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 175.103.59.0/24 | No ROA covers it. Add a ROA for AS55669, maxLength 24. |
| Route object: RIR | 175.103.59.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55669 whose prefix no peer sees AS55669 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.244.51.0/24 | NTTCOM | No ROA |
| 103.244.96.0/22 | NTTCOM | No ROA |
| 103.244.96.0/23 | NTTCOM | No ROA |
| 103.244.98.0/23 | RADB | No ROA |
| 103.244.160.0/24 | NTTCOM | No ROA |
| 103.244.161.0/24 | NTTCOM | No ROA |
| 119.110.64.0/20 | NTTCOM | No ROA |
| 119.110.64.0/21 | NTTCOM | No ROA |
| 119.110.72.0/21 | NTTCOM | No ROA |
| 119.110.76.0/22 | NTTCOM | No ROA |
| 119.110.76.0/23 | NTTCOM | No ROA |
| 119.110.76.0/24 | NTTCOM | No ROA |
| 119.110.77.0/24 | NTTCOM | No ROA |
| 119.110.78.0/23 | NTTCOM | No ROA |
| 119.110.78.0/24 | NTTCOM | No ROA |
| 122.144.0.0/21 | NTTCOM | No ROA |
| 175.103.32.0/19 | NTTCOM | No ROA |
| 175.103.32.0/20 | NTTCOM | No ROA |
| 175.103.32.0/21 | NTTCOM | No ROA |
| 175.103.32.0/22 | NTTCOM | No ROA |
| 175.103.32.0/23 | NTTCOM | No ROA |
| 175.103.34.0/23 | NTTCOM | No ROA |
| 175.103.35.0/24 | NTTCOM | No ROA |
| 175.103.36.0/22 | NTTCOM | No ROA |
| 175.103.36.0/23 | NTTCOM | No ROA |
| 175.103.36.0/24 | NTTCOM | No ROA |
| 175.103.37.0/24 | NTTCOM | No ROA |
| 175.103.38.0/23 | NTTCOM | No ROA |
| 175.103.38.0/24 | NTTCOM | No ROA |
| 175.103.39.0/24 | NTTCOM | No ROA |
| 175.103.40.0/21 | NTTCOM | No ROA |
| 175.103.40.0/22 | NTTCOM | No ROA |
| 175.103.40.0/23 | NTTCOM | No ROA |
| 175.103.40.0/24 | NTTCOM | No ROA |
| 175.103.41.0/24 | NTTCOM | No ROA |
| 175.103.42.0/23 | NTTCOM | No ROA |
| 175.103.42.0/24 | NTTCOM | No ROA |
| 175.103.43.0/24 | NTTCOM | No ROA |
| 175.103.44.0/22 | NTTCOM | No ROA |
| 175.103.44.0/23 | NTTCOM | No ROA |
| 175.103.44.0/24 | NTTCOM | No ROA |
| 175.103.46.0/23 | NTTCOM | No ROA |
| 175.103.46.0/24 | NTTCOM | No ROA |
| 175.103.47.0/24 | NTTCOM | No ROA |
| 175.103.48.0/20 | NTTCOM | No ROA |
| 175.103.48.0/21 | NTTCOM | No ROA |
| 175.103.48.0/22 | NTTCOM | No ROA |
| 175.103.48.0/23 | NTTCOM | No ROA |
| 175.103.50.0/23 | NTTCOM | No ROA |
| 175.103.50.0/24 | NTTCOM | No ROA |
| 175.103.51.0/24 | NTTCOM | No ROA |
| 175.103.52.0/22 | NTTCOM | No ROA |
| 175.103.52.0/23 | NTTCOM | No ROA |
| 175.103.52.0/24 | NTTCOM | No ROA |
| 175.103.54.0/23 | NTTCOM | No ROA |
| 175.103.54.0/24 | NTTCOM | No ROA |
| 175.103.56.0/21 | NTTCOM | No ROA |
| 175.103.56.0/22 | NTTCOM | No ROA |
| 175.103.56.0/23 | NTTCOM | No ROA |
| 175.103.56.0/24 | NTTCOM | No ROA |
| 175.103.58.0/23 | NTTCOM | No ROA |
| 175.103.60.0/22 | NTTCOM | No ROA |
| 175.103.60.0/23 | NTTCOM | No ROA |
| 175.103.60.0/24 | NTTCOM | No ROA |
| 175.103.61.0/24 | NTTCOM | No ROA |
| 175.103.62.0/23 | NTTCOM | No ROA |
| 175.103.62.0/24 | NTTCOM | No ROA |
| 175.103.63.0/24 | NTTCOM | No ROA |
| 203.173.88.0/23 | 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.