bgpreport

Network · data from 2026-11-12

AS24175 VINAREN-AS-AP - National Agency for Scientific and Technological Information

Registry name: VINAREN-AS-AP - National Agency for Scientific and Technological Information, VN · not in PeeringDB

9IPv4 routes 88.9% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
9Low visibility seen by under 10% of full-table peers
53Route objects not announced registered with origin AS24175, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24175, 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.
203.191.48.0/21 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
2406:9000::/32 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
110.35.64.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
110.35.65.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
110.35.66.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
110.35.67.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
119.18.129.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
119.18.130.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
119.18.141.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2
119.18.142.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2

AS-SET

AS24175 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 57 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced53
ChangePrefix or setDetailFull-table peers
ROA: none203.191.48.0/21No ROA covers it. Add a ROA for AS24175, maxLength 21.672 of 673
Route object: RIR203.191.48.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2406:9000::/32No ROA covers it. Add a ROA for AS24175, maxLength 32.2 of 636
Route object: RIR2406:9000::/32Route object only in NTTCOM. Add it in the RIR database for the space.2 of 636

Route objects not announced

Route objects with origin AS24175 whose prefix no peer sees AS24175 announce. Many are kept on purpose (backup routes, space announced only in some places).

110.35.64.0/21APNIC, NTTCOMValid
110.35.64.0/22APNIC, NTTCOMValid
110.35.64.0/23APNIC, NTTCOMValid
110.35.66.0/23APNIC, NTTCOMValid
110.35.68.0/22APNIC, NTTCOMValid
110.35.68.0/23APNIC, NTTCOMValid
110.35.68.0/24APNIC, NTTCOMValid
110.35.69.0/24APNIC, NTTCOMValid
110.35.70.0/23APNIC, NTTCOMValid
110.35.70.0/24APNIC, NTTCOMValid
110.35.71.0/24APNIC, NTTCOMValid
119.18.128.0/20APNIC, NTTCOMValid
119.18.128.0/21APNIC, NTTCOMValid
119.18.128.0/22APNIC, NTTCOMValid
119.18.128.0/23APNIC, NTTCOMValid
119.18.128.0/24APNIC, NTTCOMValid
119.18.130.0/23APNIC, NTTCOMValid
119.18.131.0/24APNIC, NTTCOMValid
119.18.132.0/22APNIC, NTTCOMValid
119.18.132.0/23APNIC, NTTCOMValid
119.18.132.0/24APNIC, NTTCOMValid
119.18.133.0/24APNIC, NTTCOMValid
119.18.134.0/23APNIC, NTTCOMValid
119.18.134.0/24APNIC, NTTCOMValid
119.18.135.0/24APNIC, NTTCOMValid
119.18.136.0/21APNIC, NTTCOMValid
119.18.136.0/22APNIC, NTTCOMValid
119.18.136.0/23APNIC, NTTCOMValid
119.18.136.0/24APNIC, NTTCOMValid
119.18.137.0/24APNIC, NTTCOMValid
119.18.138.0/23APNIC, NTTCOMValid
119.18.138.0/24APNIC, NTTCOMValid
119.18.139.0/24APNIC, NTTCOMValid
119.18.140.0/22APNIC, NTTCOMValid
119.18.140.0/23APNIC, NTTCOMValid
119.18.140.0/24APNIC, NTTCOMValid
119.18.142.0/23APNIC, NTTCOMValid
119.18.143.0/24APNIC, NTTCOMValid
203.191.48.0/22NTTCOM, RADBNo ROA
203.191.48.0/23NTTCOM, RADBNo ROA
203.191.48.0/24NTTCOM, RADBNo ROA
203.191.49.0/24NTTCOM, RADBNo ROA
203.191.50.0/23NTTCOM, RADBNo ROA
203.191.50.0/24NTTCOM, RADBNo ROA
203.191.51.0/24NTTCOM, RADBNo ROA
203.191.52.0/22APNIC, NTTCOM, RADBValid
203.191.52.0/23APNIC, NTTCOM, RADBValid
203.191.52.0/24APNIC, NTTCOM, RADBValid
203.191.53.0/24APNIC, NTTCOM, RADBValid
203.191.54.0/23APNIC, NTTCOM, RADBValid
203.191.54.0/24APNIC, NTTCOM, RADBValid
203.191.55.0/24APNIC, NTTCOM, RADBValid
2001:df7:c1c0::/48APNICValid

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.