ixreport

EVO CLOUD

AS43896 · EVO

EVO CLOUD LLC

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
3Using the route servers
3Facilities in PeeringDB

Tools: Where can I peer with EVO CLOUD? · Where should EVO CLOUD peer next? · Compare EVO CLOUD with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list

Nothing to fix: EVO CLOUD's PeeringDB record matches the member lists of the 2 exchanges we could compare (the others publish no list we could read).

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where EVO CLOUD's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 60G across 3 exchanges.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.42.220
185.0.42.221
2 × 10G Yes Both
Ukraine 1-IX UA Kyiv, Ukraine 185.1.213.220
185.1.213.221
2 × 10G Yes Both
Ukraine Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 185.1.63.131
185.1.63.132
2 × 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (11)

These exchanges have a switch in a facility where EVO CLOUD lists itself in PeeringDB, but don't have EVO CLOUD as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands GNM-IXAmsterdam, Netherlands 741 NewTelco Kiev
Russia PITER-IX MoscowMoscow, Russia 243 NewTelco Kiev
Ukraine UA-IXKiev, Ukraine 209 NewTelco Kiev
Ukraine DTEL-IXKiev, Ukraine 204 NewTelco Kiev; BeMobile
Bulgaria NetIXSofia, Bulgaria 204 NewTelco Kiev
Poland Giganet IXN WarsawWarsaw, Poland 49 NewTelco Kiev
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 1-DC EU
Romania Balcan-IXBucharest, Romania 29 NewTelco Kiev
Ukraine Giganet IXN OdesaOdessa, Ukraine 22 NewTelco Kiev
Ukraine Giganet IXN KharkіvKharkiv, Ukraine 13 NewTelco Kiev
United States Global Peer ExchangeWashington, United States 6 NewTelco Kiev
Facilities (3)

The buildings EVO CLOUD lists in PeeringDB, and how many of the exchanges in each it's on.

Ukraine NewTelco KievKyiv 1 of 11
Poland 1-DC EUWarsaw 1 of 2
Ukraine BeMobileKyiv 0 of 1