Network · data from 2026-11-12
AS9993 ITOCHU Techno-Solutions Corporation
Registry name: CTC-ODC - ITOCHU Techno-Solutions Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9993, 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.
| 27.34.168.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 220.152.120.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 220.213.224.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 157.113.0.0/16 | No ROA | Other IRR onlyRADB | 672 100% |
| 202.51.48.0/21 | No ROA | Other IRR onlyRADB | 672 100% |
| 202.83.128.0/19 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.111.240.0/21 | No ROA | Other IRR onlyRADB | 672 100% |
| 211.128.96.0/20 | No ROA | Other IRR onlyRADB | 672 100% |
| 182.50.172.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 2402:1400::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS9993'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 92 are in fix.csv.
- ROA: none10
- Route object: RIR10
- Route object: not announced72
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 27.34.168.0/21 | No ROA covers it. Add a ROA for AS9993, maxLength 21. |
| Route object: RIR | 27.34.168.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 220.152.120.0/21 | No ROA covers it. Add a ROA for AS9993, maxLength 21. |
| Route object: RIR | 220.152.120.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 220.213.224.0/20 | No ROA covers it. Add a ROA for AS9993, maxLength 20. |
| Route object: RIR | 220.213.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 157.113.0.0/16 | No ROA covers it. Add a ROA for AS9993, maxLength 16. |
| Route object: RIR | 157.113.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.51.48.0/21 | No ROA covers it. Add a ROA for AS9993, maxLength 21. |
| Route object: RIR | 202.51.48.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.83.128.0/19 | No ROA covers it. Add a ROA for AS9993, maxLength 19. |
| Route object: RIR | 202.83.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.111.240.0/21 | No ROA covers it. Add a ROA for AS9993, maxLength 21. |
| Route object: RIR | 203.111.240.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 211.128.96.0/20 | No ROA covers it. Add a ROA for AS9993, maxLength 20. |
| Route object: RIR | 211.128.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 182.50.172.0/22 | No ROA covers it. Add a ROA for AS9993, maxLength 22. |
| Route object: RIR | 182.50.172.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2402:1400::/32 | No ROA covers it. Add a ROA for AS9993, maxLength 32. |
| Route object: RIR | 2402:1400::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9993 whose prefix no peer sees AS9993 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.34.168.0/24 | RADB | No ROA |
| 27.34.169.0/24 | RADB | No ROA |
| 27.34.170.0/24 | RADB | No ROA |
| 27.34.171.0/24 | RADB | No ROA |
| 27.34.172.0/24 | RADB | No ROA |
| 27.34.173.0/24 | RADB | No ROA |
| 27.34.174.0/24 | RADB | No ROA |
| 27.34.175.0/24 | RADB | No ROA |
| 157.113.0.0/17 | RADB | No ROA |
| 157.113.128.0/17 | RADB | No ROA |
| 182.50.172.0/24 | RADB | No ROA |
| 182.50.173.0/24 | RADB | No ROA |
| 182.50.174.0/24 | RADB | No ROA |
| 182.50.175.0/24 | RADB | No ROA |
| 202.51.48.0/24 | RADB | No ROA |
| 202.51.49.0/24 | RADB | No ROA |
| 202.51.50.0/24 | RADB | No ROA |
| 202.51.51.0/24 | RADB | No ROA |
| 202.51.52.0/24 | RADB | No ROA |
| 202.51.53.0/24 | RADB | No ROA |
| 202.51.54.0/24 | RADB | No ROA |
| 202.51.55.0/24 | RADB | No ROA |
| 202.83.128.0/20 | RADB | No ROA |
| 202.83.152.0/21 | RADB | No ROA |
| 203.111.240.0/24 | RADB | No ROA |
| 203.111.241.0/24 | RADB | No ROA |
| 203.111.242.0/24 | RADB | No ROA |
| 203.111.243.0/24 | RADB | No ROA |
| 203.111.244.0/24 | RADB | No ROA |
| 203.111.245.0/24 | RADB | No ROA |
| 203.111.246.0/24 | RADB | No ROA |
| 203.111.247.0/24 | RADB | No ROA |
| 211.128.96.0/24 | RADB | No ROA |
| 211.128.97.0/24 | RADB | No ROA |
| 211.128.98.0/24 | RADB | No ROA |
| 211.128.99.0/24 | RADB | No ROA |
| 211.128.100.0/24 | RADB | No ROA |
| 211.128.101.0/24 | RADB | No ROA |
| 211.128.102.0/24 | RADB | No ROA |
| 211.128.103.0/24 | RADB | No ROA |
| 211.128.104.0/24 | RADB | No ROA |
| 211.128.105.0/24 | RADB | No ROA |
| 211.128.106.0/24 | RADB | No ROA |
| 211.128.107.0/24 | RADB | No ROA |
| 211.128.108.0/24 | RADB | No ROA |
| 211.128.109.0/24 | RADB | No ROA |
| 211.128.110.0/24 | RADB | No ROA |
| 211.128.111.0/24 | RADB | No ROA |
| 220.152.120.0/24 | RADB | No ROA |
| 220.152.121.0/24 | RADB | No ROA |
| 220.152.122.0/24 | RADB | No ROA |
| 220.152.123.0/24 | RADB | No ROA |
| 220.152.124.0/24 | RADB | No ROA |
| 220.152.125.0/24 | RADB | No ROA |
| 220.152.126.0/24 | RADB | No ROA |
| 220.152.127.0/24 | RADB | No ROA |
| 220.213.224.0/24 | RADB | No ROA |
| 220.213.225.0/24 | RADB | No ROA |
| 220.213.226.0/24 | RADB | No ROA |
| 220.213.227.0/24 | RADB | No ROA |
| 220.213.228.0/24 | RADB | No ROA |
| 220.213.229.0/24 | RADB | No ROA |
| 220.213.230.0/24 | RADB | No ROA |
| 220.213.231.0/24 | RADB | No ROA |
| 220.213.232.0/24 | RADB | No ROA |
| 220.213.233.0/24 | RADB | No ROA |
| 220.213.234.0/24 | RADB | No ROA |
| 220.213.235.0/24 | RADB | No ROA |
| 220.213.236.0/24 | RADB | No ROA |
| 220.213.237.0/24 | RADB | No ROA |
| 220.213.238.0/24 | RADB | No ROA |
| 220.213.239.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.