bgpreport

Network · data from 2026-11-12

AS62728 Velocity, The Greatest Phone Company Ever, Inc

Registry name: VGPE-ASN1 - VELOCITY, A MANAGED SERVICES COMPANY, US · PeeringDB

11IPv4 routes 27.3% RPKI valid · 63.6% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS62728, seen from no peer

Announced routes

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

161.115.127.0/24 No ROA Nonecovered by 161.115.96.0/19 671 100% 68
130.250.240.0/20 No ROA Other IRR onlyRADB 670 100% 68
161.115.96.0/19 No ROA Other IRR onlyRADB 670 100% 68
162.220.72.0/24 No ROA Other IRR onlyRADB 670 100% 68
162.220.73.0/24 No ROA Other IRR onlyRADB 670 100% 68
162.220.74.0/24 No ROA Other IRR onlyRADB 670 100% 68
168.92.224.0/19 No ROA Other IRR onlyRADB 670 100% 68
8.9.40.0/21 No ROA Other IRR onlyRADB 663 99% 68
192.210.16.0/21 Valid Nonecovered by 192.210.16.0/20 670 100% 68
192.210.24.0/22 Valid Nonecovered by 192.210.16.0/20 670 100% 68
192.210.28.0/23 Valid Nonecovered by 192.210.16.0/20 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS62728: RADB::AS62728. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS62728 isn't in the set, or no route object for AS62728 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS62728 in itNot covered
RADB::AS62728 A single AS number, not a set: AS62728 (this network), 11 route objects.

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

  • ROA: none8
  • Route object: none4
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none161.115.127.0/24No ROA covers it. Add a ROA for AS62728, maxLength 24.671 of 673
Route object: none161.115.127.0/24No route object for it. A route object for 161.115.96.0/19 with origin AS62728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62728 in the RIR database for the space.671 of 673
ROA: none130.250.240.0/20No ROA covers it. Add a ROA for AS62728, maxLength 20.670 of 673
Route object: RIR130.250.240.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none161.115.96.0/19No ROA covers it. Add a ROA for AS62728, maxLength 19.670 of 673
Route object: RIR161.115.96.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.220.72.0/24No ROA covers it. Add a ROA for AS62728, maxLength 24.670 of 673
Route object: RIR162.220.72.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.220.73.0/24No ROA covers it. Add a ROA for AS62728, maxLength 24.670 of 673
Route object: RIR162.220.73.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.220.74.0/24No ROA covers it. Add a ROA for AS62728, maxLength 24.670 of 673
Route object: RIR162.220.74.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.92.224.0/19No ROA covers it. Add a ROA for AS62728, maxLength 19.670 of 673
Route object: RIR168.92.224.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none8.9.40.0/21No ROA covers it. Add a ROA for AS62728, maxLength 21.663 of 673
Route object: RIR8.9.40.0/21Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: none192.210.16.0/21No route object for it. A route object for 192.210.16.0/20 with origin AS62728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62728 in the RIR database for the space.670 of 673
Route object: none192.210.24.0/22No route object for it. A route object for 192.210.16.0/20 with origin AS62728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62728 in the RIR database for the space.670 of 673
Route object: none192.210.28.0/23No route object for it. A route object for 192.210.16.0/20 with origin AS62728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62728 in the RIR database for the space.670 of 673

Route objects not announced

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

65.36.46.0/24RADBNo ROA
162.220.72.0/22RADBNo ROA
192.210.16.0/20RADBValid
204.77.13.0/24RADBNo 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.