bgpreport

Network · data from 2026-11-12

AS45590 HGCINTNET-AS-AP - Hutch Connect

Registry name: HGCINTNET-AS-AP - Hutch Connect, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45590, 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.
2a00:8422:b216::/48 Valid Other IRR onlyRADB 636 100% 69
112.137.17.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
112.137.20.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

AS-SET

AS45590 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 3 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR2a00:8422:b216::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

112.137.16.0/20RADBNo ROA
203.184.180.0/24APNICValid

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.