bgpreport

Network · data from 2026-11-12

AS23522 ASN-HRNET - GigeNET

Registry name: ASN-HRNET - GigeNET, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23522, 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.
66.252.8.0/21 Valid Nonecovered by 66.252.0.0/19 673 100% 67
66.252.16.0/21 Valid Nonecovered by 66.252.0.0/19 673 100% 67
66.252.6.0/24 Valid Nonecovered by 66.252.0.0/19 671 100% 67
66.252.0.0/24 Valid Other IRR onlyRADB 671 100% 67
66.252.1.0/24 Valid Other IRR onlyRADB 671 100% 67
66.252.2.0/24 Valid Other IRR onlyRADB 671 100% 67
66.252.3.0/24 Valid Other IRR onlyRADB 671 100% 67
66.252.5.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS23522 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.

  • Route object: none3
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none66.252.8.0/21No route object for it. A route object for 66.252.0.0/19 with origin AS23522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23522 in the RIR database for the space.673 of 673
Route object: none66.252.16.0/21No route object for it. A route object for 66.252.0.0/19 with origin AS23522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23522 in the RIR database for the space.673 of 673
Route object: none66.252.6.0/24No route object for it. A route object for 66.252.0.0/19 with origin AS23522 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23522 in the RIR database for the space.671 of 673
Route object: RIR66.252.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.252.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.252.2.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.252.3.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.252.5.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.252.0.0/19RADBValid
66.252.27.0/24RADBValid
66.252.31.0/24RADBValid

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.