Skip to main content

AS54286

AS-TAIPEI-ARIN

TAIPEI101 NETWORK LLC

Registry

Authoritative registration data

AS number
54286
Name
AS-TAIPEI-ARIN
Organisation
TAIPEI101 NETWORK LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

7

Total announced

13

Announced prefixes

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

Prefixes announced by AS54286
107.1.57.0/24 IPv4 /24 not checked
23.147.120.0/24 IPv4 /24 RPKI valid
23.246.164.0/24 IPv4 /24 not checked
23.246.166.0/24 IPv4 /24 not checked
23.246.167.0/24 IPv4 /24 not checked
64.49.28.0/24 IPv4 /24 not checked
2602:faa8:90::/44 IPv6 /44 RPKI valid
2602:faa8:166::/48 IPv6 /48 not checked
2602:faa8:205::/48 IPv6 /48 RPKI valid
2602:faa8:206::/48 IPv6 /48 not checked
2602:faa8:404::/48 IPv6 /48 RPKI valid
2602:faa8:609::/48 IPv6 /48 RPKI valid
2602:faa8:784::/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

Internet Exchange memberships listed for AS54286
Address families
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
NRIX 10,000 Mbps 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 AS54286 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS54286 in AS paths

Observed upstreams
Families
AS46475 LIMESTONENETWORKS 849 3,084
v4 v6
AS6939 HURRICANE 170 238
v6
AS44324 MOEDOVE-AS 142 177
v6
AS25091 IP-Max 2 4
v6
AS48646 STEFAN6 1 1
v6
AS401753 BIXCE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS54286 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

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.