bgpreport

Network · data from 2026-11-12

AS8018 VEL-AS - Velocity Networks, Inc.

Registry name: VEL-AS - Velocity Networks, Inc., US · not in PeeringDB

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

Announced routes

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

185.123.180.0/24 No ROA Nonecovered by 185.123.180.0/22 673 100% 67
185.124.40.0/22 No ROA None 673 100% 67
185.124.42.0/23 No ROA None 673 100% 67
206.126.130.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.132.0/23 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.136.0/23 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.144.0/23 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.146.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.147.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.148.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.152.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.153.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.154.0/23 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.157.0/24 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
206.126.158.0/23 No ROA Nonecovered by 206.126.128.0/19 673 100% 67
207.182.230.0/23 No ROA Nonecovered by 207.182.224.0/19 673 100% 67
207.182.250.0/23 No ROA Nonecovered by 207.182.224.0/19 673 100% 67
208.85.187.0/24 No ROA Other origin onlycovered by 208.85.186.0/23 673 100% 67
208.85.184.0/24 No ROA Other IRR onlyRADB 673 100% 67
206.126.128.0/19 No ROA RIR databaseARIN, RADB 673 100% 67
207.182.224.0/19 No ROA RIR databaseARIN, RADB 673 100% 67
208.85.184.0/22 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

AS8018 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 50 are in fix.csv.

  • ROA: none22
  • Route object: none18
  • Route object: RIR1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none185.123.180.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none185.123.180.0/24No route object for it. A route object for 185.123.180.0/22 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none185.124.40.0/22No ROA covers it. Add a ROA for AS8018, maxLength 22.673 of 673
Route object: none185.124.40.0/22No route object for it. Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none185.124.42.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none185.124.42.0/23No route object for it. Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.130.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.130.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.132.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none206.126.132.0/23No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.136.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none206.126.136.0/23No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.144.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none206.126.144.0/23No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.146.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.146.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.147.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.147.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.148.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.148.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.152.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.152.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.153.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.153.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.154.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none206.126.154.0/23No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.157.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none206.126.157.0/24No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none206.126.158.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none206.126.158.0/23No route object for it. A route object for 206.126.128.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none207.182.230.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none207.182.230.0/23No route object for it. A route object for 207.182.224.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none207.182.250.0/23No ROA covers it. Add a ROA for AS8018, maxLength 23.673 of 673
Route object: none207.182.250.0/23No route object for it. A route object for 207.182.224.0/19 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none208.85.187.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: none208.85.187.0/24Route objects for it name AS36707. A route object for 208.85.186.0/23 with origin AS8018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8018 in the RIR database for the space.673 of 673
ROA: none208.85.184.0/24No ROA covers it. Add a ROA for AS8018, maxLength 24.673 of 673
Route object: RIR208.85.184.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.126.128.0/19No ROA covers it. Add a ROA for AS8018, maxLength 19.673 of 673
ROA: none207.182.224.0/19No ROA covers it. Add a ROA for AS8018, maxLength 19.673 of 673
ROA: none208.85.184.0/22No ROA covers it. Add a ROA for AS8018, maxLength 22.673 of 673

Route objects not announced

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

64.161.254.0/23RADBNo ROA
64.162.97.0/24RADBNo ROA
185.123.180.0/22RADBNo ROA
199.245.246.0/24RADBNo ROA
208.85.184.0/23RADBNo ROA
208.85.185.0/24RADBNo ROA
208.85.186.0/23RADBNo ROA
208.85.186.0/24RADBNo ROA
209.76.232.0/22RADBNo 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.