Skip to main content

AS150770

SHINENET

SHINE TECH INFORMATION COMPANY LIMITED

Registry

Authoritative registration data

AS number
150770
Name
SHINENET
Organisation
SHINE TECH INFORMATION COMPANY LIMITED
Country
Flag of Taiwan TW Taiwan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS150770
185.238.212.0/23 IPv4 /23 not checked
103.197.158.0/24 IPv4 /24 not checked
103.197.159.0/24 IPv4 /24 not checked
212.23.206.0/24 IPv4 /24 not checked
31.56.37.0/24 IPv4 /24 not checked
87.229.92.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 AS150770 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS150770 in AS paths

Observed upstreams
Families
AS18186 NEBULA-GLOBAL 282 1,151
v4
AS17408 ABOVE-AS-AP 279 764
v4
AS6939 HURRICANE 266 380
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS150770 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

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