bgpreport

Network · data from 2026-11-12

AS25687 KVH02842 - KVH INDUSTRIES,INC.

Registry name: KVH02842 - KVH INDUSTRIES,INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25687, 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.
199.244.86.0/24 No ROA Nonecovered by 199.244.86.0/23 673 100% 67
162.246.224.0/22 No ROA RIR databaseARIN 673 100% 67
185.47.84.0/22 No ROA RIR databaseRIPE 673 100% 67
185.47.85.0/24 No ROA RIR databaseRIPE 673 100% 67
199.244.86.0/23 No ROA RIR databaseARIN 673 100% 67
162.246.226.0/24 No ROA RIR databaseARIN 671 100% 68
103.224.8.0/22 Valid RIR databaseAPNIC 673 100% 67
103.224.9.0/24 Valid RIR databaseAPNIC 673 100% 67
103.224.8.0/24 Valid RIR databaseAPNIC 671 100% 68
199.244.84.0/24 Valid RIR databaseARIN 671 100% 67
199.244.85.0/24 Valid RIR databaseARIN 671 100% 67
2602:fe9a:a::/48 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none199.244.86.0/24No ROA covers it. Add a ROA for AS25687, maxLength 24.673 of 673
Route object: none199.244.86.0/24No route object for it. A route object for 199.244.86.0/23 with origin AS25687 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25687 in the RIR database for the space.673 of 673
ROA: none162.246.224.0/22No ROA covers it. Add a ROA for AS25687, maxLength 22.673 of 673
ROA: none185.47.84.0/22No ROA covers it. Add a ROA for AS25687, maxLength 22.673 of 673
ROA: none185.47.85.0/24No ROA covers it. Add a ROA for AS25687, maxLength 24.673 of 673
ROA: none199.244.86.0/23No ROA covers it. Add a ROA for AS25687, maxLength 23.673 of 673
ROA: none162.246.226.0/24No ROA covers it. Add a ROA for AS25687, maxLength 24.671 of 673

Route objects not announced

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

162.246.224.0/24ARINNo ROA
199.244.84.0/23RADBNo ROA
2001:470:2a4::/48ARINValid
2602:fe9a:224::/48ARINNo ROA
2a01:8e60:222::/48RIPENo 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.