Network · data from 2026-11-12

AS62592 HOPI - HOPI TELECOMMUNICATIONS

Registry name: HOPI - HOPI TELECOMMUNICATIONS, US · not in PeeringDB

10IPv4 routes 60.0% RPKI valid · 30.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 7 with no route object for this origin

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

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

Announced routes

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


38.29.196.0/23	No ROA	Nonecovered by 38.29.196.0/22	673 100%	67
38.29.198.0/24	No ROA	Nonecovered by 38.29.196.0/22	672 100%	67
38.29.199.0/24	No ROA	Nonecovered by 38.29.196.0/22	672 100%	67
38.29.196.0/22	No ROA	Other IRR onlyALTDB	673 100%	67
162.219.129.0/24	Valid	Nonecovered by 162.219.128.0/21	673 100%	67
162.219.130.0/23	Valid	Nonecovered by 162.219.128.0/21	673 100%	67
162.219.132.0/24	Valid	Nonecovered by 162.219.128.0/21	673 100%	67
162.219.135.0/24	Valid	Nonecovered by 162.219.128.0/21	673 100%	67
161.199.60.0/22	Valid	RIR databaseALTDB, ARIN	673 100%	67
162.219.128.0/21	Valid	RIR databaseARIN, RADB	673 100%	67

AS-SET

AS62592 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: none4
Route object: none7
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.29.196.0/23	No ROA covers it. Add a ROA for AS62592, maxLength 23.	673 of 673
Route object: none	38.29.196.0/23	No route object for it. A route object for 38.29.196.0/22 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	673 of 673
ROA: none	38.29.198.0/24	No ROA covers it. Add a ROA for AS62592, maxLength 24.	672 of 673
Route object: none	38.29.198.0/24	No route object for it. A route object for 38.29.196.0/22 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	672 of 673
ROA: none	38.29.199.0/24	No ROA covers it. Add a ROA for AS62592, maxLength 24.	672 of 673
Route object: none	38.29.199.0/24	No route object for it. A route object for 38.29.196.0/22 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	672 of 673
ROA: none	38.29.196.0/22	No ROA covers it. Add a ROA for AS62592, maxLength 22.	673 of 673
Route object: RIR	38.29.196.0/22	Route object only in ALTDB. Add it in the RIR database for the space.	673 of 673
Route object: none	162.219.129.0/24	No route object for it. A route object for 162.219.128.0/21 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	673 of 673
Route object: none	162.219.130.0/23	No route object for it. A route object for 162.219.128.0/21 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	673 of 673
Route object: none	162.219.132.0/24	No route object for it. A route object for 162.219.128.0/21 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	673 of 673
Route object: none	162.219.135.0/24	No route object for it. A route object for 162.219.128.0/21 with origin AS62592 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62592 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.29.196.0/23

No ROA covers it. Add a ROA for AS62592, maxLength 23.

673 of 673

Route object: none

38.29.196.0/23

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

673 of 673

ROA: none

38.29.198.0/24

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

672 of 673

Route object: none

38.29.198.0/24

672 of 673

ROA: none

38.29.199.0/24

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

672 of 673

Route object: none

38.29.199.0/24

672 of 673

ROA: none

38.29.196.0/22

No ROA covers it. Add a ROA for AS62592, maxLength 22.

673 of 673

Route object: RIR

38.29.196.0/22

Route object only in ALTDB. Add it in the RIR database for the space.

673 of 673

Route object: none

162.219.129.0/24

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

673 of 673

Route object: none

162.219.130.0/23

673 of 673

Route object: none

162.219.132.0/24

673 of 673

Route object: none

162.219.135.0/24

673 of 673

Route objects not announced

Every route object with origin AS62592 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.