bgpreport

Network · data from 2026-11-12

AS2731 Horizon Telcom

Registry name: HORIZONTELCOM - Infinity Fiber LLC, US · PeeringDB

11IPv4 routes 90.9% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS2731, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2731, 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.
24.223.59.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.44.224.0/21 Valid RIR databaseARIN, NTTCOM 673 100% 67
66.33.48.0/21 Valid RIR databaseARIN, NTTCOM, RADB 673 100% 67
205.164.184.0/21 Valid RIR databaseARIN, NTTCOM 673 100% 67
205.164.224.0/21 Valid RIR databaseARIN, NTTCOM 673 100% 67
206.82.176.0/20 Valid RIR databaseARIN, NTTCOM, RADB 673 100% 67
8.21.104.0/23 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 67
8.21.120.0/23 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 67
8.21.122.0/23 Valid RIR databaseARIN, NTTCOM 671 100% 67
8.21.124.0/23 Valid RIR databaseARIN, NTTCOM 671 100% 67
8.225.240.0/22 Valid RIR databaseARIN, NTTCOM, RADB 671 100% 67
2606:7c40::/32 Valid RIR databaseARIN, RADB 237 37% 59

AS-SET

AS2731's PeeringDB record names no 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 5 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none24.223.59.0/24No ROA covers it. Add a ROA for AS2731, maxLength 24.670 of 673
Route object: RIR24.223.59.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

38.46.160.0/21ARINValid
38.46.176.0/20ARINValid
38.133.76.0/22RADBNo ROA

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.