Network · data from 2026-11-12
AS131427 AOHOAVIET-VN-AS - AOHOAVIET-VN
Registry name: AOHOAVIET-VN-AS - AOHOAVIET-VN, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131427, 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.53.228.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.53.229.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.53.230.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.53.231.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.127.192.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.127.193.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.127.194.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.127.195.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
AS-SET
AS131427 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 22 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.53.228.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.53.228.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.53.229.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.53.229.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.53.230.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.53.230.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.53.231.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.53.231.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.127.192.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.127.192.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.127.193.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.127.193.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.127.194.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.127.194.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 103.127.195.0/24 | No ROA covers it. Add a ROA for AS131427, maxLength 24. |
| Route object: RIR | 103.127.195.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131427 whose prefix no peer sees AS131427 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 10.53.228.0/22 | NTTCOM | No ROA |
| 10.53.228.0/24 | NTTCOM | No ROA |
| 103.53.228.0/22 | NTTCOM | No ROA |
| 103.127.192.0/22 | APNIC, NTTCOM | No ROA |
| 103.196.248.0/22 | NTTCOM | No ROA |
| 2404:b7c0::/48 | APNIC, 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.