Network · data from 2026-11-12
AS2506 NTT WEST CHUGOKU CORPORATION
Registry name: SuperCSI - NTT business Solutions corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2506, 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.
| 133.41.0.0/16 | No ROA | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 150.19.0.0/16 | No ROA | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 165.242.0.0/16 | No ROA | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 202.15.112.0/22 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 202.245.144.0/24 | No ROA | Other IRR onlyJPIRR, NTTCOM | 670 100% |
| 2001:44a0::/32 | No ROA | Other IRR onlyJPIRR, NTTCOM | 634 100% |
| 202.249.192.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 202.249.224.0/19 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 202.249.200.0/22 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.204.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.206.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.207.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.208.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.214.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.236.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
| 202.249.237.0/24 | Valid | Other IRR onlyJPIRR | 670 100% |
AS-SET
AS2506'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 65 are in fix.csv.
- ROA: none6
- Route object: RIR16
- Route object: not announced43
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 133.41.0.0/16 | No ROA covers it. Add a ROA for AS2506, maxLength 16. |
| Route object: RIR | 133.41.0.0/16 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 150.19.0.0/16 | No ROA covers it. Add a ROA for AS2506, maxLength 16. |
| Route object: RIR | 150.19.0.0/16 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 165.242.0.0/16 | No ROA covers it. Add a ROA for AS2506, maxLength 16. |
| Route object: RIR | 165.242.0.0/16 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.15.112.0/22 | No ROA covers it. Add a ROA for AS2506, maxLength 22. |
| Route object: RIR | 202.15.112.0/22 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.245.144.0/24 | No ROA covers it. Add a ROA for AS2506, maxLength 24. |
| Route object: RIR | 202.245.144.0/24 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2001:44a0::/32 | No ROA covers it. Add a ROA for AS2506, maxLength 32. |
| Route object: RIR | 2001:44a0::/32 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.192.0/19 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.224.0/19 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.200.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.204.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.206.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.207.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.208.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.214.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.236.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.249.237.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2506 whose prefix no peer sees AS2506 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.245.0.0/16 | NTTCOM | No ROA |
| 202.245.168.0/22 | NTTCOM | No ROA |
| 202.249.192.0/18 | NTTCOM | Valid |
| 202.249.192.0/24 | JPIRR | Valid |
| 202.249.193.0/24 | JPIRR | Valid |
| 202.249.194.0/24 | JPIRR | Valid |
| 202.249.195.0/24 | JPIRR | Valid |
| 202.249.196.0/24 | JPIRR | Valid |
| 202.249.197.0/24 | JPIRR | Valid |
| 202.249.198.0/23 | JPIRR | Valid |
| 202.249.209.0/24 | JPIRR, NTTCOM | Valid |
| 202.249.210.0/24 | JPIRR | Valid |
| 202.249.211.0/24 | JPIRR | Valid |
| 202.249.212.0/24 | JPIRR | Valid |
| 202.249.213.0/24 | JPIRR | Valid |
| 202.249.215.0/24 | JPIRR | Valid |
| 202.249.216.0/24 | JPIRR | Valid |
| 202.249.217.0/24 | JPIRR | Valid |
| 202.249.218.0/24 | JPIRR | Valid |
| 202.249.219.0/24 | JPIRR | Valid |
| 202.249.220.0/24 | JPIRR | Valid |
| 202.249.221.0/24 | JPIRR | Valid |
| 202.249.222.0/24 | JPIRR | Valid |
| 202.249.223.0/24 | JPIRR | Valid |
| 202.249.235.0/24 | JPIRR | Valid |
| 202.249.238.0/24 | JPIRR | Valid |
| 202.249.239.0/24 | JPIRR | Valid |
| 202.249.240.0/24 | JPIRR | Valid |
| 202.249.241.0/24 | JPIRR | Valid |
| 202.249.242.0/24 | JPIRR | Valid |
| 202.249.243.0/24 | JPIRR | Valid |
| 202.249.244.0/24 | JPIRR | Valid |
| 202.249.245.0/24 | JPIRR | Valid |
| 202.249.246.0/24 | JPIRR | Valid |
| 202.249.247.0/24 | JPIRR | Valid |
| 202.249.248.0/24 | JPIRR | Valid |
| 202.249.249.0/24 | JPIRR | Valid |
| 202.249.250.0/24 | JPIRR | Valid |
| 202.249.251.0/24 | JPIRR | Valid |
| 202.249.252.0/24 | JPIRR | Valid |
| 202.249.253.0/24 | JPIRR | Valid |
| 202.249.254.0/24 | JPIRR | Valid |
| 202.249.255.0/24 | JPIRR | 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.