Network · data from 2026-11-12

AS16608 KENTEC - Kentec Communications, Inc.

Registry name: KENTEC - Kentec Communications, Inc., US · not in PeeringDB

22IPv4 routes 95.5% RPKI valid · 95.5% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

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

4Route objects not announced registered with origin AS16608, seen from no peer

Announced routes

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


204.238.214.0/24	No ROA	RIR databaseALTDB, ARIN	670 100%	68
64.187.82.0/24	Valid	Nonecovered by 64.187.82.0/23	671 100%	68
64.187.64.0/20	Valid	RIR databaseARIN	671 100%	68
64.187.64.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.65.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.66.0/23	Valid	RIR databaseARIN	671 100%	68
64.187.67.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.68.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.69.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.70.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.71.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.72.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.73.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.74.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.75.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.76.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.77.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.78.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.79.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.81.0/24	Valid	RIR databaseARIN	671 100%	68
64.187.84.0/22	Valid	RIR databaseARIN	671 100%	68
64.187.94.0/23	Valid	RIR databaseARIN	671 100%	68
2604:5f80::/32	Valid	RIR databaseARIN	635 100%	69

AS-SET

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

ROA: none1
Route object: none1
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: none	204.238.214.0/24	No ROA covers it. Add a ROA for AS16608, maxLength 24.	670 of 673
Route object: none	64.187.82.0/24	No route object for it. A route object for 64.187.82.0/23 with origin AS16608 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16608 in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

204.238.214.0/24

No ROA covers it. Add a ROA for AS16608, maxLength 24.

670 of 673

Route object: none

64.187.82.0/24

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

671 of 673

Route objects not announced

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


64.187.64.0/19	ARIN	No ROA
64.187.82.0/23	ARIN	Valid
64.187.88.0/22	ARIN	Valid
64.187.92.0/23	ARIN	Valid

64.187.64.0/19

ARIN

No ROA

64.187.82.0/23

ARIN

Valid

64.187.88.0/22

ARIN

Valid

64.187.92.0/23

ARIN

Valid

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.