Skip to main content

AS38856

WalksCloud-AS

Walks Cloud Inc.

Registry

Authoritative registration data

AS number
38856
Name
WalksCloud-AS
Organisation
Walks Cloud Inc.
Country
Flag of Taiwan TW Taiwan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS38856
103.159.118.0/23 IPv4 /23 not checked
2406:d040::/32 IPv6 /32 not checked

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 AS38856
Address families
STUIX 10,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 AS38856 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS38856 in AS paths

Observed upstreams
Families
AS134823 SDCL-AS-AP 1,080 4,076
v4 v6
AS6939 HURRICANE 192 228
v4 v6
AS24482 SGGS-AS-AP 6 33
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 3
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS38856 in AS paths

Observed downstreams
Families
AS57429 HARAGUROICHA-AS 628 2,606
v4 v6
AS212360 Jimmy-Pan 233 1,189
v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS38855 STUIX-AS-TW 4 15
v4 v6
AS207705 JK-NETWORK 4 13
v6
AS18041 TWDS-AS-TW 2 6
v4 v6

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.