Announced routes
Every prefix a peer of the route collectors sees with origin AS59102, 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.
| 87.101.96.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 87.101.104.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 87.101.108.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 103.41.252.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 153.124.168.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 153.124.172.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 219.100.48.0/22 | No ROA | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS59102's PeeringDB record names no 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 16 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 87.101.96.0/21 | No ROA covers it. Add a ROA for AS59102, maxLength 21. |
| Route object: RIR | 87.101.96.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 87.101.104.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 87.101.104.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 87.101.108.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 87.101.108.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.41.252.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 103.41.252.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 153.124.168.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 153.124.168.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 153.124.172.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 153.124.172.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 219.100.48.0/22 | No ROA covers it. Add a ROA for AS59102, maxLength 22. |
| Route object: RIR | 219.100.48.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59102 whose prefix no peer sees AS59102 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.41.253.0/24 | NTTCOM | No ROA |
| 103.41.254.0/24 | NTTCOM | 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.