Skip to main content

AS56683

EXNESS-AS

EXNESS LIMITED

Registry

Authoritative registration data

AS number
56683
Name
EXNESS-AS
Organisation
EXNESS LIMITED
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

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

Prefixes announced by AS56683
193.194.116.0/22 IPv4 /22 not checked
102.211.233.0/24 IPv4 /24 not checked
103.72.103.0/24 IPv4 /24 not checked
151.243.233.0/24 IPv4 /24 not checked
193.194.117.0/24 IPv4 /24 not checked
193.194.118.0/24 IPv4 /24 not checked
193.194.119.0/24 IPv4 /24 not checked
45.114.188.0/24 IPv4 /24 not checked
45.133.132.0/24 IPv4 /24 not checked
45.133.133.0/24 IPv4 /24 not checked
45.40.117.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

Internet Exchange memberships listed for AS56683
Address families
Equinix Amsterdam: Equinix IX - AM Metro 10,000 Mbps IPv4 · IPv6
Equinix London: Equinix IX - LD Metro 10,000 Mbps IPv4 · IPv6
JumboIX Cyprus 100 Mbps IPv4

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 AS56683 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS56683 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 248 1,610
v4
AS3257 GTT-BACKBONE 120 391
v4
AS25818 ORG-cA1-AFRINIC 263 349
v4
AS15830 Equinix 183 331
v4
AS41095 144 317
v4
AS42156 239 301
v4
AS6939 HURRICANE 159 227
v4
AS174 COGENT-174 117 155
v4
AS9002 RETN-AS 34 41
v4
AS37497 ORG-NPL3-AFRINIC 33 41
v4
AS140951 23 25
v4
AS286 3 6
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS56683 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.