bgpreport

Network · data from 2026-11-12

AS394708 HORIZONCHILLICOTHETELEPHONE - Horizon Telcom Inc.

Registry name: HORIZONCHILLICOTHETELEPHONE - Horizon Telcom Inc., US · not in PeeringDB

46IPv4 routes 97.8% RPKI valid · 95.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS394708, seen from no peer

Announced routes

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

198.245.215.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.38.76.0/24 Valid Nonecovered by 199.38.72.0/21 673 100% 67
199.38.78.0/24 Valid Nonecovered by 199.38.72.0/21 673 100% 67
66.209.134.0/23 Valid RIR databaseARIN, RADB 671 100% 68
66.209.134.0/24 Valid RIR databaseARIN 671 100% 68
66.209.135.0/24 Valid RIR databaseARIN 671 100% 68
74.126.72.0/21 Valid RIR databaseARIN, RADB 671 100% 68
74.126.72.0/22 Valid RIR databaseARIN 671 100% 68
74.126.76.0/22 Valid RIR databaseARIN 671 100% 68
74.126.77.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 68
74.126.78.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 68
74.126.79.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 68
173.249.128.0/20 Valid RIR databaseARIN 671 100% 68
198.45.12.0/22 Valid RIR databaseARIN 671 100% 68
199.38.72.0/21 Valid RIR databaseARIN 671 100% 68
199.187.196.0/22 Valid RIR databaseARIN, RADB 671 100% 68
209.143.11.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.143.18.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.143.57.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.143.63.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.173.162.0/23 Valid RIR databaseARIN, RADB 671 100% 68
209.173.162.0/24 Valid RIR databaseARIN 671 100% 68
209.173.163.0/24 Valid RIR databaseARIN 671 100% 68
209.173.182.0/24 Valid RIR databaseARIN, RADB 671 100% 68
209.173.184.0/21 Valid RIR databaseARIN, RADB 671 100% 68
209.173.184.0/24 Valid RIR databaseARIN 671 100% 68
209.173.185.0/24 Valid RIR databaseARIN 671 100% 68
209.173.186.0/24 Valid RIR databaseARIN 671 100% 68
209.173.187.0/24 Valid RIR databaseARIN 671 100% 68
209.173.188.0/24 Valid RIR databaseARIN 671 100% 68
209.173.189.0/24 Valid RIR databaseARIN 671 100% 68
209.173.190.0/24 Valid RIR databaseARIN 671 100% 68
209.173.191.0/24 Valid RIR databaseARIN 671 100% 68
216.201.42.0/24 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 68
216.255.0.0/21 Valid RIR databaseARIN, RADB 671 100% 68
216.255.4.0/24 Valid RIR databaseARIN 671 100% 68
216.255.5.0/24 Valid RIR databaseARIN 671 100% 68
216.255.6.0/24 Valid RIR databaseARIN 671 100% 68
216.255.7.0/24 Valid RIR databaseARIN 671 100% 68
216.255.21.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.255.34.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.255.43.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.255.44.0/23 Valid RIR databaseARIN, RADB 671 100% 68
216.255.51.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.255.60.0/23 Valid RIR databaseARIN, RADB 671 100% 68
216.255.62.0/24 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

AS394708 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 11 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none198.245.215.0/24No ROA covers it. Add a ROA for AS394708, maxLength 24.671 of 673
Route object: RIR198.245.215.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none199.38.76.0/24No route object for it. A route object for 199.38.72.0/21 with origin AS394708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394708 in the RIR database for the space.673 of 673
Route object: none199.38.78.0/24No route object for it. A route object for 199.38.72.0/21 with origin AS394708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394708 in the RIR database for the space.673 of 673

Route objects not announced

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

184.105.21.0/24ARINInvalid: origin
184.105.44.0/24ARINInvalid: origin
184.105.56.0/24ARINInvalid: origin
209.173.184.0/22ARIN, RADBValid
209.173.188.0/22ARIN, RADBValid
216.66.55.0/24ARINInvalid: origin
2606:f800::/32ARINValid

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.