bgpreport

Network · data from 2026-11-12

AS63959 Hong Kong Syscloud Technology

Registry name: HKSTL-HK - Hong Kong Syscloud Technology Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63959, 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.
45.113.32.0/24 No ROA Other origin onlycovered by 45.113.32.0/22 671 100% 68
103.105.132.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.52.188.0/23 No ROA RIR databaseAPNIC 671 100% 68
103.52.188.0/24 No ROA RIR databaseAPNIC 670 100% 68
103.52.189.0/24 No ROA RIR databaseAPNIC 670 100% 68
45.113.34.0/24 No ROA RIR databaseAPNIC, RADB 669 99% 67
2400:c2c0::/32 No ROA RIR databaseAPNIC, RADB 634 100% 69

AS-SET

AS63959'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 21 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none45.113.32.0/24No ROA covers it. Add a ROA for AS63959, maxLength 24.671 of 673
Route object: none45.113.32.0/24Route objects for it name AS131450, AS133012, AS199524. A route object for 45.113.32.0/22 with origin AS63959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63959 in the RIR database for the space.671 of 673
ROA: none103.105.132.0/24No ROA covers it. Add a ROA for AS63959, maxLength 24.672 of 673
Route object: RIR103.105.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.52.188.0/23No ROA covers it. Add a ROA for AS63959, maxLength 23.671 of 673
ROA: none103.52.188.0/24No ROA covers it. Add a ROA for AS63959, maxLength 24.670 of 673
ROA: none103.52.189.0/24No ROA covers it. Add a ROA for AS63959, maxLength 24.670 of 673
ROA: none45.113.34.0/24No ROA covers it. Add a ROA for AS63959, maxLength 24.669 of 673
ROA: none2400:c2c0::/32No ROA covers it. Add a ROA for AS63959, maxLength 32.634 of 636

Route objects not announced

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

45.113.32.0/22APNICNo ROA
103.52.188.0/22APNICNo ROA
103.52.191.0/24APNIC, RADBNo ROA
103.105.133.0/24RADBNo ROA
103.105.134.0/24APNICNo ROA
103.105.135.0/24APNICNo ROA
103.126.188.0/24NTTCOM, RADBNo ROA
103.126.191.0/24RADBNo ROA
2001:470:62::/48ARINValid
2400:c2c0:0:6::/64APNICNo ROA
2400:c2c0:0:7::/64APNICNo ROA
2400:c2c0:0:8::/64APNICNo 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.