Network · data from 2026-11-12

AS399912 HAYO-TELECOM - Hayo Telecom, Inc

Registry name: HAYO-TELECOM - Hayo Telecom, Inc, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

2No ROA 1 with no route object for this origin

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

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

Announced routes

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


207.228.212.0/22	No ROA	None	673 100%	67
2604:9240::/32	No ROA	Other IRR onlyRADB	635 100%	67
216.73.188.0/24	Valid	RIR databaseARIN, RADB	673 100%	67

AS-SET

AS399912 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 4 are in fix.csv.

ROA: none2
Route object: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	207.228.212.0/22	No ROA covers it. Add a ROA for AS399912, maxLength 22.	673 of 673
Route object: none	207.228.212.0/22	No route object for it. Add a route object with origin AS399912 in the RIR database for the space.	673 of 673
ROA: none	2604:9240::/32	No ROA covers it. Add a ROA for AS399912, maxLength 32.	635 of 636
Route object: RIR	2604:9240::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

207.228.212.0/22

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

673 of 673

Route object: none

207.228.212.0/22

No route object for it. Add a route object with origin AS399912 in the RIR database for the space.

673 of 673

ROA: none

2604:9240::/32

No ROA covers it. Add a ROA for AS399912, maxLength 32.

635 of 636

Route object: RIR

2604:9240::/32

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

635 of 636

Route objects not announced

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