bgpreport

Network · data from 2026-11-12

AS38248 VTC-AS-VN - VTC-VN

Registry name: VTC-AS-VN - VTC-VN, VN · not in PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
113Route objects not announced registered with origin AS38248, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38248, 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.

2401:b800::/48 No ROA Nonecovered by 2401:b800::/32 636 100% 68
2401:b800:1::/48 No ROA Nonecovered by 2401:b800::/32 636 100% 69
2401:b800:2::/48 No ROA Nonecovered by 2401:b800::/32 636 100% 69
2401:b800::/32 No ROA RIR databaseAPNIC 636 100% 68
117.103.192.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.196.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.200.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.204.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.208.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.212.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.216.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.220.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.224.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.228.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.232.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
117.103.236.0/22 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
117.103.240.0/22 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
117.103.244.0/22 Valid Other IRR onlyNTTCOM, RADB 670 100% 67

AS-SET

AS38248 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 134 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: RIR14
  • Route object: not announced113
ChangePrefix or setDetailFull-table peers
ROA: none2401:b800::/48No ROA covers it. Add a ROA for AS38248, maxLength 48.636 of 636
Route object: none2401:b800::/48No route object for it. A route object for 2401:b800::/32 with origin AS38248 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38248 in the RIR database for the space.636 of 636
ROA: none2401:b800:1::/48No ROA covers it. Add a ROA for AS38248, maxLength 48.636 of 636
Route object: none2401:b800:1::/48No route object for it. A route object for 2401:b800::/32 with origin AS38248 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38248 in the RIR database for the space.636 of 636
ROA: none2401:b800:2::/48No ROA covers it. Add a ROA for AS38248, maxLength 48.636 of 636
Route object: none2401:b800:2::/48No route object for it. A route object for 2401:b800::/32 with origin AS38248 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38248 in the RIR database for the space.636 of 636
ROA: none2401:b800::/32No ROA covers it. Add a ROA for AS38248, maxLength 32.636 of 636
Route object: RIR117.103.192.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.196.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.200.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.204.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.208.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.212.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.216.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.220.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.224.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.228.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.232.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR117.103.236.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR117.103.240.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR117.103.244.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

117.103.192.0/18APNIC, NTTCOM, RADBValid
117.103.192.0/19NTTCOM, RADBValid
117.103.192.0/20NTTCOM, RADBValid
117.103.192.0/21NTTCOM, RADBValid
117.103.192.0/23NTTCOM, RADBValid
117.103.192.0/24NTTCOM, RADBValid
117.103.193.0/24NTTCOM, RADBValid
117.103.194.0/23NTTCOM, RADBValid
117.103.194.0/24NTTCOM, RADBValid
117.103.195.0/24NTTCOM, RADBValid
117.103.196.0/23NTTCOM, RADBValid
117.103.196.0/24NTTCOM, RADBValid
117.103.197.0/24NTTCOM, RADBValid
117.103.198.0/23NTTCOM, RADBValid
117.103.198.0/24NTTCOM, RADBValid
117.103.199.0/24NTTCOM, RADBValid
117.103.200.0/21NTTCOM, RADBValid
117.103.200.0/23NTTCOM, RADBValid
117.103.200.0/24NTTCOM, RADBValid
117.103.201.0/24NTTCOM, RADBValid
117.103.202.0/23NTTCOM, RADBValid
117.103.202.0/24NTTCOM, RADBValid
117.103.203.0/24NTTCOM, RADBValid
117.103.204.0/23NTTCOM, RADBValid
117.103.204.0/24NTTCOM, RADBValid
117.103.205.0/24NTTCOM, RADBValid
117.103.206.0/23NTTCOM, RADBValid
117.103.206.0/24NTTCOM, RADBValid
117.103.207.0/24NTTCOM, RADBValid
117.103.208.0/20NTTCOM, RADBValid
117.103.208.0/21NTTCOM, RADBValid
117.103.208.0/23NTTCOM, RADBValid
117.103.208.0/24NTTCOM, RADBValid
117.103.209.0/24NTTCOM, RADBValid
117.103.210.0/23NTTCOM, RADBValid
117.103.210.0/24NTTCOM, RADBValid
117.103.211.0/24NTTCOM, RADBValid
117.103.212.0/23NTTCOM, RADBValid
117.103.212.0/24NTTCOM, RADBValid
117.103.213.0/24NTTCOM, RADBValid
117.103.214.0/23NTTCOM, RADBValid
117.103.214.0/24NTTCOM, RADBValid
117.103.215.0/24NTTCOM, RADBValid
117.103.216.0/21NTTCOM, RADBValid
117.103.216.0/23NTTCOM, RADBValid
117.103.216.0/24NTTCOM, RADBValid
117.103.217.0/24NTTCOM, RADBValid
117.103.218.0/23NTTCOM, RADBValid
117.103.218.0/24NTTCOM, RADBValid
117.103.219.0/24NTTCOM, RADBValid
117.103.220.0/23NTTCOM, RADBValid
117.103.220.0/24NTTCOM, RADBValid
117.103.221.0/24NTTCOM, RADBValid
117.103.222.0/23NTTCOM, RADBValid
117.103.222.0/24NTTCOM, RADBValid
117.103.223.0/24NTTCOM, RADBValid
117.103.224.0/19NTTCOM, RADBValid
117.103.224.0/20NTTCOM, RADBValid
117.103.224.0/21NTTCOM, RADBValid
117.103.224.0/23NTTCOM, RADBValid
117.103.224.0/24NTTCOM, RADBValid
117.103.225.0/24NTTCOM, RADBValid
117.103.226.0/23NTTCOM, RADBValid
117.103.226.0/24NTTCOM, RADBValid
117.103.227.0/24NTTCOM, RADBValid
117.103.228.0/23NTTCOM, RADBValid
117.103.228.0/24NTTCOM, RADBValid
117.103.229.0/24NTTCOM, RADBValid
117.103.230.0/23NTTCOM, RADBValid
117.103.230.0/24NTTCOM, RADBValid
117.103.231.0/24NTTCOM, RADBValid
117.103.232.0/21NTTCOM, RADBValid
117.103.232.0/23NTTCOM, RADBValid
117.103.232.0/24NTTCOM, RADBValid
117.103.233.0/24NTTCOM, RADBValid
117.103.234.0/23NTTCOM, RADBValid
117.103.234.0/24NTTCOM, RADBValid
117.103.235.0/24NTTCOM, RADBValid
117.103.236.0/23NTTCOM, RADBValid
117.103.236.0/24NTTCOM, RADBValid
117.103.237.0/24NTTCOM, RADBValid
117.103.238.0/23NTTCOM, RADBValid
117.103.238.0/24NTTCOM, RADBValid
117.103.239.0/24NTTCOM, RADBValid
117.103.240.0/20NTTCOM, RADBValid
117.103.240.0/21NTTCOM, RADBValid
117.103.240.0/23NTTCOM, RADBValid
117.103.240.0/24NTTCOM, RADBValid
117.103.241.0/24NTTCOM, RADBValid
117.103.242.0/23NTTCOM, RADBValid
117.103.242.0/24NTTCOM, RADBValid
117.103.243.0/24NTTCOM, RADBValid
117.103.244.0/23NTTCOM, RADBValid
117.103.244.0/24NTTCOM, RADBValid
117.103.245.0/24NTTCOM, RADBValid
117.103.246.0/23NTTCOM, RADBValid
117.103.246.0/24NTTCOM, RADBValid
117.103.247.0/24NTTCOM, RADBValid
117.103.248.0/21NTTCOM, RADBValid
117.103.248.0/22NTTCOM, RADBValid
117.103.248.0/23NTTCOM, RADBValid
117.103.248.0/24NTTCOM, RADBValid
117.103.249.0/24NTTCOM, RADBValid
117.103.250.0/23NTTCOM, RADBValid
117.103.250.0/24NTTCOM, RADBValid
117.103.251.0/24NTTCOM, RADBValid
117.103.252.0/22NTTCOM, RADBValid
117.103.252.0/23NTTCOM, RADBValid
117.103.252.0/24NTTCOM, RADBValid
117.103.253.0/24NTTCOM, RADBValid
117.103.254.0/23NTTCOM, RADBValid
117.103.254.0/24NTTCOM, RADBValid
117.103.255.0/24NTTCOM, RADBValid

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.