Skip to main content

AS138401

TUPLENET2-AS-AP

TupleTech Corporation

Registry

Authoritative registration data

AS number
138401
Name
TUPLENET2-AS-AP
Organisation
TupleTech Corporation
Country
Flag of China CN China
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

8

Total announced

9

Announced prefixes

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

Prefixes announced by AS138401
143.246.55.0/24 IPv4 /24 not checked
2406:840:f860::/48 IPv6 /48 not checked
2406:840:f861::/48 IPv6 /48 not checked
2406:840:f862::/48 IPv6 /48 not checked
2406:840:f863::/48 IPv6 /48 not checked
2406:840:f868::/48 IPv6 /48 not checked
2406:840:f869::/48 IPv6 /48 not checked
2406:840:f86c::/48 IPv6 /48 not checked
2406:840:fea1::/48 IPv6 /48 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 AS138401 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS138401 in AS paths

Observed upstreams
Families
AS20473 AS-VULTR 218 891
v6
AS17433 HNSL-AS-AP 623 890
v4 v6
AS7720 SKYWOLF-AS-AP 352 717
v6
AS139317 ZX-AS-AP 225 291
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS138401 in AS paths

Observed downstreams
Families
AS138211 TUPLENET-AS-AP 216 283
v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS203472 POEMA-AS-EU 1 6
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.