Network · data from 2026-11-12

AS401514 KVW-AS01 - Kern Valley Wireless, Inc

Registry name: KVW-AS01 - Kern Valley Wireless, Inc, US · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 66.7% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS401514, seen from no peer

Announced routes

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


136.175.7.0/24	Valid	Nonecovered by 136.175.6.0/23	670 100%	68
198.212.10.0/24	Valid	Nonecovered by 198.212.8.0/22	670 100%	68
2607:3dc0::/36	Valid	Nonecovered by 2607:3dc0::/32	635 100%	69
23.151.88.0/24	Valid	RIR databaseARIN	670 100%	68
64.112.44.0/23	Valid	RIR databaseARIN	670 100%	68
136.175.6.0/23	Valid	RIR databaseARIN	670 100%	68
198.212.8.0/22	Valid	RIR databaseARIN	670 100%	68
2607:3dc0::/32	Valid	RIR databaseARIN	635 100%	69

AS-SET

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

Route object: none3

Change	Prefix or set	Detail	Full-table peers
Route object: none	136.175.7.0/24	No route object for it. A route object for 136.175.6.0/23 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.	670 of 673
Route object: none	198.212.10.0/24	No route object for it. A route object for 198.212.8.0/22 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.	670 of 673
Route object: none	2607:3dc0::/36	No route object for it. A route object for 2607:3dc0::/32 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

136.175.7.0/24

No route object for it. A route object for 136.175.6.0/23 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.

670 of 673

Route object: none

198.212.10.0/24

No route object for it. A route object for 198.212.8.0/22 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.

670 of 673

Route object: none

2607:3dc0::/36

No route object for it. A route object for 2607:3dc0::/32 with origin AS401514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401514 in the RIR database for the space.

635 of 636

Route objects not announced

Every route object with origin AS401514 is announced.

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.