Skip to main content

AS59956

S3WAY

------------------------

Registry

Authoritative registration data

AS number
59956
Name
S3WAY
Organisation
------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS59956
185.235.186.0/24 IPv4 /24 not checked
192.162.198.0/24 IPv4 /24 not checked
194.145.227.0/24 IPv4 /24 not checked
195.191.200.0/24 IPv4 /24 not checked
195.191.201.0/24 IPv4 /24 not checked
195.39.240.0/24 IPv4 /24 not checked
5.53.116.0/24 IPv4 /24 not checked
94.131.200.0/24 IPv4 /24 not checked
94.131.201.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 AS59956 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS59956 in AS paths

Observed upstreams
Families
AS48957 NETWORK-LVIV-AS 303 1,165
v4
AS9002 RETN-AS 511 945
v4
AS35297 DATALINE-AS 236 638
v4
AS1299 TWELVE99 57 141
v4
AS44356 EPSILON 7 18
v4
AS9304 HUTCHISON-AS-AP 1 2
v4
AS28917 Fiord-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59956 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 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.