ixreport

WP SYSTEM

AS57101 · WadowiceNET Sp. z o.o.

Integrator Systemow Informatycznych WP SYSTEM S.C

1Exchange
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
0Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with WP SYSTEM? · Where should WP SYSTEM peer next? · Compare WP SYSTEM with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in WP SYSTEM's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If WP SYSTEM has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491Not on its IX-F export
    IPv4178.216.41.184
    IPv6–
    SpeedNot published

Exchanges over time

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

Map

Where WP SYSTEM'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

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.41.184 PeeringDB only

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

These exchanges have a switch in a facility where WP SYSTEM lists itself in PeeringDB, but don't have WP SYSTEM 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 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Poland EPIX.WarszawaWarsaw, Poland 483 Equinix WA1 - Warsaw, Centrum LIM
Poland TPIX PLWarsaw, Poland 480 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 Equinix WA1 - Warsaw, Centrum LIM
Poland Equinix WarsawWarsaw, Poland 242 Equinix WA1 - Warsaw, Centrum LIM
Bulgaria NetIXSofia, Bulgaria 204 Equinix WA1 - Warsaw, Centrum LIM
Poland THINX WarsawWarsaw, Poland 194 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Netherlands Global-IXAmsterdam, Netherlands 138 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Poland Giganet IXN WarsawWarsaw, Poland 49 Equinix WA1 - Warsaw, Centrum LIM
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 Equinix WA1 - Warsaw, Centrum LIM; 4 Data Center
Ukraine Giganet IXN OdesaOdessa, Ukraine 22 Equinix WA1 - Warsaw, Centrum LIM
Ukraine Giganet IXN KharkіvKharkiv, Ukraine 13 Equinix WA1 - Warsaw, Centrum LIM
Facilities (2)

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

Poland Equinix WA1 - Warsaw, Centrum LIMWarsaw 0 of 13
Poland 4 Data CenterKatowice 1 of 7

Recent changes Search them

  • Nov 4, 2026 [IXF] AS57101 WP SYSTEM dropped from EPIX.Katowice's IX-F list (still in PeeringDB)