Skip to main content

AS17476

CHL-AS-AP

CloudRadium (HK) Limited

Registry

Authoritative registration data

AS number
17476
Name
CHL-AS-AP
Organisation
CloudRadium (HK) Limited
Country
Flag of Hong Kong SAR China HK Hong Kong SAR China
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS17476
178.107.43.0/24 IPv4 /24 not checked
178.107.46.0/24 IPv4 /24 not checked
178.107.47.0/24 IPv4 /24 not checked
183.90.184.0/24 IPv4 /24 not checked
183.90.185.0/24 IPv4 /24 RPKI valid
202.36.160.0/24 IPv4 /24 RPKI valid
202.36.161.0/24 IPv4 /24 RPKI valid
203.29.202.0/24 IPv4 /24 not checked
203.29.203.0/24 IPv4 /24 not checked
2401:ada0:100::/40 IPv6 /40 RPKI valid
2401:ada0::/40 IPv6 /40 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS17476
Address families
Equinix Hong Kong 300,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS17476 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

19 networks seen before AS17476 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 4,986 61,449
v4 v6
AS2914 NTT-DATA-2914 5,895 55,665
v4 v6
AS3257 GTT-BACKBONE 5,375 55,583
v4
AS6453 AS6453 2,365 17,386
v4 v6
AS3356 LEVEL3 764 14,311
v4
AS6939 HURRICANE 1,161 12,341
v4
AS24482 SGGS-AS-AP 70 6,722
v4 v6
AS58453 CMI-INT-HK 320 5,619
v4
AS38008 APERTURE-AS-AP 150 2,650
v4
AS9002 RETN-AS 150 1,448
v4
AS286 KPN 27 345
v4
AS23764 CTGNet 6 252
v4
AS58807 CMI-INT-AS 51 73
v4
AS8966 Etisalat-AS 33 67
v4
AS9498 BBIL-AP 17 47
v4
AS137409 GSLNETWORKS-AS-AP 8 29
v4
AS10099 UNICOM-Global 2 7
v4
AS138997 EDCL-AS-AP 1 5
v4
AS4134 CHINANET-BACKBONE 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

43 networks seen after AS17476 in AS paths

Observed downstreams
Families
AS40065 CNSERVERS 1,581 46,616
v4
AS398478 PEG-HK 1,240 22,828
v4
AS138415 YANCYLIMITED-AS-HK 3,586 21,889
v4 v6
AS132839 POWERLINE-AS-AP 149 19,713
v4
AS201501 isec-asn 669 16,794
v4
AS398823 PEG-LA 835 16,779
v4
AS18013 ASLINE-AS-AP 1,178 14,416
v4
AS398993 PEG-TY 301 11,289
v4
AS58807 CMI-INT-AS 10 10,314
v4
AS153706 STACKNETWORK-AS-AP 1,143 9,401
v4 v6
AS58453 CMI-INT-HK 99 7,205
v4
AS135097 MYCLOUD-AS-AP 947 6,745
v4 v6
AS219499 ZUNGWAICLOUD 453 5,507
v4
AS36137 PEG-FR 296 5,144
v4
AS152194 CTGSERVERLIMITED-AS-AP 295 5,099
v4
AS152918 LNL-AS-AP 1,027 4,993
v4
AS136038 HDTIDCCLOUD-AS-AP 458 3,731
v4
AS36002 GOMAMI 576 3,378
v4
AS400468 AXIOGIC 357 2,298
v4
AS402436 LV-NETWORKS 268 1,968
v4
AS8143 NEBUSRT 785 1,952
v4
AS402309 AS-AURO 517 1,636
v4
AS401586 SQUIRREL 261 1,309
v4
AS402306 AS-DATAFORGE 261 1,309
v4
AS402139 PEEKABO-ANYCAST 315 1,285
v4
AS30006 TOP-BUSINESS-INC 447 987
v4
AS150706 HKZTCL-AS-AP 516 732
v4
AS55720 GIGABIT-MY 280 698
v4
AS152320 GOALNOW-AS-AP 70 661
v4
AS14293 UNI-EDGE 266 654
v4
AS402075 PEEKABO 260 645
v4
AS139659 LUCID-AS-AP 11 394
v4 v6
AS57406 Zero-Distance 271 329
v4
AS15012 TRIOLAB 268 329
v4
AS400906 AS-MINO 264 327
v4
AS399870 BYNARIUM-BACKBONE 232 282
v4
AS932 XNNET 23 225
v4
AS714 APPLE-ENGINEERING 1 77
v4
AS396856 AS-SHARON 29 43
v4
AS10111 ZEONET-AS-AP 13 42
v4
AS6939 HURRICANE 4 11
v4
AS132825 MYTEK-AS-AP 2 6
v4
AS1299 TWELVE99 2 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS55720 GIGABIT-MY 118 17,638
v4
AS49544 i3Dnet 55 810
v4 v6
AS35280 F5 53 713
v4
AS134823 SDCL-AS-AP 57 518
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.