bgpreport

Network · data from 2026-11-12

AS54646 HARDYNET - Hardy Telecommunications

Registry name: HARDYNET - Hardy Telecommunications, US · not in PeeringDB

7IPv4 routes 42.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
4No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS54646, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS54646, 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.
63.67.238.0/24 No ROA RIR databaseARIN, NTTCOM 673 100% 67
63.67.240.0/23 No ROA RIR databaseARIN, NTTCOM 673 100% 67
65.209.25.0/24 No ROA RIR databaseARIN, NTTCOM 673 100% 67
63.92.148.0/23 No ROA RIR databaseARIN, NTTCOM 2 0%low visibility 2
131.162.152.0/21 Valid RIR databaseARIN, NTTCOM 673 100% 67
172.111.4.0/22 Valid RIR databaseARIN, NTTCOM 673 100% 67
198.41.48.0/20 Valid RIR databaseARIN, NTTCOM 670 100% 67
2604:bfc0::/32 Valid RIR databaseARIN, NTTCOM 635 100% 67

AS-SET

AS54646 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 5 are in fix.csv.

  • ROA: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none63.67.238.0/24No ROA covers it. Add a ROA for AS54646, maxLength 24.673 of 673
ROA: none63.67.240.0/23No ROA covers it. Add a ROA for AS54646, maxLength 23.673 of 673
ROA: none65.209.25.0/24No ROA covers it. Add a ROA for AS54646, maxLength 24.673 of 673
ROA: none63.92.148.0/23No ROA covers it. Add a ROA for AS54646, maxLength 23.2 of 673

Route objects not announced

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

63.67.219.192/26ARINNo 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.