Network · data from 2026-11-12
AS393536 NTTDATA-RAGINGWIRE - NTT DATA AMERICAS, INC
Registry name: NTTDATA-RAGINGWIRE - NTT DATA AMERICAS, INC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393536, 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.
| 192.43.232.0/23 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 192.206.110.0/23 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 131.103.22.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 131.103.24.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 157.238.211.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 129.250.203.64/29 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
| 131.103.20.192/29 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
| 131.103.20.224/27 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
| 131.103.21.24/29 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
| 131.103.21.64/27 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
AS-SET
AS393536 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 18 are in fix.csv.
- ROA: none2
- Route object: RIR10
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.43.232.0/23 | No ROA covers it. Add a ROA for AS393536, maxLength 23. |
| Route object: RIR | 192.43.232.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.206.110.0/23 | No ROA covers it. Add a ROA for AS393536, maxLength 23. |
| Route object: RIR | 192.206.110.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.22.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.24.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 157.238.211.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 129.250.203.64/29 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.20.192/29 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.20.224/27 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.21.24/29 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 131.103.21.64/27 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393536 whose prefix no peer sees AS393536 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.2.182.0/23 | NTTCOM | Valid |
| 204.9.98.0/23 | NTTCOM | No ROA |
| 204.9.98.0/24 | NTTCOM | No ROA |
| 204.9.99.0/24 | NTTCOM | No ROA |
| 206.180.192.0/24 | NTTCOM | No ROA |
| 206.180.193.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.