Skip to main content

AS17415

MINGYITEA-AS-TW

Ming Yi Tea Farm

Registry

Authoritative registration data

AS number
17415
Name
MINGYITEA-AS-TW
Organisation
Ming Yi Tea Farm
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 AS17415
103.152.202.0/24 IPv4 /24 not checked
2406:3540::/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 AS17415
Address families
Poema IX 1,000 Mbps IPv6
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 AS17415 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS17415 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 266 400
v4 v6
AS20473 169 213
v4
AS134823 SDCL-AS-AP 57 75
v4
AS137409 GSLNETWORKS-AS-AP 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS17415 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 TWDS-AS-TW 1 4
v4 v6
AS24482 SGGS-AS-AP 1 2
v4 v6
AS38855 STUIX-AS-TW 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.