bgpreport

Network · data from 2026-11-12

AS62514 VENUS-TEL-CORP - Venus Telephone Corporation

Registry name: VENUS-TEL-CORP - Venus Telephone Corporation, US · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 25.0% with a route object
0IPv6 routes
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
1Route objects not announced registered with origin AS62514, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62514, 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.
147.92.116.0/23 No ROA Nonecovered by 147.92.112.0/21 673 100% 67
147.92.112.0/23 No ROA Nonecovered by 147.92.112.0/21 670 100% 67
147.92.114.0/23 No ROA Nonecovered by 147.92.112.0/21 670 100% 67
147.92.112.0/21 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none147.92.116.0/23No ROA covers it. Add a ROA for AS62514, maxLength 23.673 of 673
Route object: none147.92.116.0/23No route object for it. A route object for 147.92.112.0/21 with origin AS62514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62514 in the RIR database for the space.673 of 673
ROA: none147.92.112.0/23No ROA covers it. Add a ROA for AS62514, maxLength 23.670 of 673
Route object: none147.92.112.0/23No route object for it. A route object for 147.92.112.0/21 with origin AS62514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62514 in the RIR database for the space.670 of 673
ROA: none147.92.114.0/23No ROA covers it. Add a ROA for AS62514, maxLength 23.670 of 673
Route object: none147.92.114.0/23No route object for it. A route object for 147.92.112.0/21 with origin AS62514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62514 in the RIR database for the space.670 of 673
ROA: none147.92.112.0/21No ROA covers it. Add a ROA for AS62514, maxLength 21.673 of 673

Route objects not announced

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

65.210.96.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.