bgpreport

Network · data from 2026-11-12

AS210597 HAOXIANGYONG HONGKONG HAO XIANG YONG TECHNOLOGY CO., LIMITED

Registry name: HAOXIANGYONG HONGKONG HAO XIANG YONG TECHNOLOGY CO., LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210597, 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.
2a13:9500:1ea::/48 Invalid: origin Other origin only 25 4%low visibility 15
41.180.168.0/23 Valid RIR databaseAFRINIC 673 100% 66

AS-SET

AS210597 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin2a13:9500:1ea::/48ROAs covering it name AS218539, not AS210597. If AS210597 should announce it, add a ROA for AS210597.25 of 636
Route object: none2a13:9500:1ea::/48Route objects for it name AS218539. Add a route object with origin AS210597 in the RIR database for the space.25 of 636

Route objects not announced

Every route object with origin AS210597 is announced.

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.