bgpreport

Network · data from 2026-11-12

AS14814 VSE14814 - V.S. Enterprises LTD

Registry name: VSE14814 - V.S. Enterprises LTD, US · not in PeeringDB

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

Announced routes

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

64.71.64.0/21 No ROA RIR databaseARIN, RADB 671 100% 68
64.71.69.0/24 No ROA RIR databaseARIN 670 100% 68
64.71.70.0/24 No ROA RIR databaseARIN 0 0%low visibility 1

AS-SET

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

  • ROA: none3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none64.71.64.0/21No ROA covers it. Add a ROA for AS14814, maxLength 21.671 of 673
ROA: none64.71.69.0/24No ROA covers it. Add a ROA for AS14814, maxLength 24.670 of 673
ROA: none64.71.70.0/24No ROA covers it. Add a ROA for AS14814, maxLength 24.0 of 673

Route objects not announced

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

64.71.64.0/19RADBNo ROA
64.71.64.0/22ARINNo ROA
64.71.64.0/24ARINNo ROA
64.71.65.0/24ARINNo ROA
64.71.66.0/24ARINNo ROA
64.71.67.0/24ARINNo ROA
64.71.68.0/22ARINNo ROA
64.71.68.0/24ARINNo ROA
64.71.71.0/24ARINNo ROA
2604:620::/32ARINNo 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.