Skip to main content

AS131659

NETEASE-AS-TW

NETEASE

Registry

Authoritative registration data

AS number
131659
Name
NETEASE-AS-TW
Organisation
NETEASE
Country
Flag of Taiwan TW Taiwan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS131659
103.124.252.0/22 IPv4 /22 not checked
103.131.252.0/22 IPv4 /22 not checked
103.131.253.0/24 IPv4 /24 not checked
103.160.226.0/24 IPv4 /24 not checked
103.160.227.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS131659 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS131659 in AS paths

Observed upstreams
Families
AS13335 CLOUDFLARENET 270 725
v4
AS6939 HURRICANE 268 718
v4
AS21859 ZEN-ECN 271 355
v4
AS4780 SEEDNET 26 39
v4
AS9505 TWGATE-AP 6 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS131659 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 1
v4
AS134823 SDCL-AS-AP 1 1
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.