Skip to main content

AS43896

EVO

EVO CLOUD LLC

Registry

Authoritative registration data

AS number
43896
Name
EVO
Organisation
EVO CLOUD LLC
Country
—
RIR
RIPE
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 AS43896
185.86.57.0/24 IPv4 /24 not checked
185.86.58.0/24 IPv4 /24 not checked
193.242.216.0/24 IPv4 /24 not checked
193.34.168.0/24 IPv4 /24 not checked
193.34.169.0/24 IPv4 /24 not checked
91.195.215.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 AS43896
Address families
1-IX EU 20,000 Mbps IPv4
1-IX UA 20,000 Mbps IPv4
Giganet IXN: Global exchange 20,000 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 AS43896 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS43896 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS43896 in AS paths

Observed downstreams
Families
AS204283 PROM-OFFICE 29 34
v4

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 42
v4
AS209823 ENKI-AS 3 7
v4
AS48919 UA-CITY-AS 2 6
v4
AS34927 iFog-GmbH 1 5
v4
AS198150 SIACOM-AS 1 5
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.