Skip to main content

AS150771

FUYU-AS

FUYU Group Inc.

Registry

Authoritative registration data

AS number
150771
Name
FUYU-AS
Organisation
FUYU Group 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 AS150771
157.20.68.0/24 IPv4 /24 not checked
2401:81a0::/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 AS150771
Address families
STUIX 10,000 Mbps IPv4 · IPv6
TPIX-TW 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 AS150771 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS150771 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 235 344
v6
AS17408 247 338
v4
AS134823 36 60
v4 v6
AS137409 GSLNETWORKS-AS-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS150771 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS18041 1 4
v4 v6
AS24482 SGGS-AS-AP 1 2
v4 v6
AS38855 1 2
v4 v6
AS59105 1 2
v4 v6
AS207705 JK-NETWORK 1 1
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.