bgpreport

Network · data from 2026-11-12

AS13666 VRIS-AS-BLOCK - Verizon Business

Registry name: VRIS-AS-BLOCK - Verizon Business, US · not in PeeringDB

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

Announced routes

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

63.64.73.0/24 No ROA None 673 100% 67
63.64.106.0/23 No ROA None 673 100% 67
65.222.244.0/24 No ROA Other origin only 673 100% 67
65.242.63.0/24 No ROA None 673 100% 67
65.242.112.0/24 No ROA None 673 100% 67
65.242.122.0/24 No ROA None 673 100% 67
204.177.181.0/24 No ROA None 673 100% 67
206.64.200.0/24 No ROA None 673 100% 67
208.251.210.0/24 No ROA None 673 100% 67
2600:803:418::/48 No ROA None 636 100% 67

AS-SET

AS13666 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none63.64.73.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none63.64.73.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none63.64.106.0/23No ROA covers it. Add a ROA for AS13666, maxLength 23.673 of 673
Route object: none63.64.106.0/23No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none65.222.244.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none65.222.244.0/24Route objects for it name AS32296. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none65.242.63.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none65.242.63.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none65.242.112.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none65.242.112.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none65.242.122.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none65.242.122.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none204.177.181.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none204.177.181.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none206.64.200.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none206.64.200.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none208.251.210.0/24No ROA covers it. Add a ROA for AS13666, maxLength 24.673 of 673
Route object: none208.251.210.0/24No route object for it. Add a route object with origin AS13666 in the RIR database for the space.673 of 673
ROA: none2600:803:418::/48No ROA covers it. Add a ROA for AS13666, maxLength 48.636 of 636
Route object: none2600:803:418::/48No route object for it. Add a route object with origin AS13666 in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS13666 is announced.

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.