ixreport

ETOP Sp z o.o.

AS20853 · Datahouse.pl

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
7Facilities in PeeringDB

Tools: Where can I peer with ETOP Sp z o.o.? · Where should ETOP Sp z o.o. peer next? · Compare ETOP Sp z o.o. with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in ETOP Sp z o.o.'s PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on ETOP Sp z o.o.'s PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs400G1.2T
    • In the entry with IPv4 80.81.193.185: set Speed to 1200000 (1.2T) (now 400000).

Exchanges over time

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

Map

Where ETOP Sp z o.o.'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 920G across 8 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.185 2001:7f8::5175:0:1 400G 97 routes Both Speed differs
Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.249 2001:7f8:5b::249 100G Yes Both
Poland EPIX.Warszawa Warsaw, Poland 89.46.144.172 2001:678:3ac::172 100G Yes Both
Poland Equinix Warsaw Warsaw, Poland 195.182.219.23 2001:7f8:42::a502:853:1 10G Yes PeeringDB
Ukraine Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 185.1.62.136 2001:7f8:6c::136 100G Yes PeeringDB
Poland Giganet IXN Warsaw Warsaw, Poland 185.1.196.96 2001:7f8:6c:4::96 100G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.0.195 2001:7f8:60::2:853:1 100G Both
Poland TPIX PL Warsaw, Poland 195.149.232.42 2001:7f8:27::2:853:2 10G Yes Both

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

These exchanges have a switch in a facility where ETOP Sp z o.o. lists itself in PeeringDB, but don't have ETOP Sp z o.o. 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.

Facilities (7)

The buildings ETOP Sp z o.o. lists in PeeringDB, and how many of the exchanges in each it's on.

Poland Equinix WA1 - Warsaw, Centrum LIMWarsaw 6 of 13
Poland LIM WarsawWarsaw 5 of 11
Poland ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)Warsaw 5 of 8
Poland 4 Data CenterKatowice 3 of 7
Poland Equinix WA2 - WarsawWarsaw 3 of 4
Poland Datahouse WarsawWarsaw No exchange
Poland Orange Polska / Warsaw św. Barbary 10Warsaw No exchange