ixreport

EPIX.EPINET

AS201925

Stowarzyszenie e-Poludnie

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
SelectivePeering policy
2Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with EPIX.EPINET? · Where should EPIX.EPINET peer next? · Compare EPIX.EPINET with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in EPIX.EPINET's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on EPIX.EPINET'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 (2)

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. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.216.40.188 178.216.41.252178.216.40.62 178.216.40.188 178.216.41.252
    IPv6 address missing from PeeringDB2001:7f8:5b::188 2001:7f8:5b::5072001:7f8:5b::62 2001:7f8:5b::188 2001:7f8:5b::507
    Port speed differs2 × 100G200G + 20G + 10G
    • In the entry with IPv4 178.216.40.188: set Speed to 10000 (10G) (now 100000).
    • In the entry with IPv4 178.216.41.252: set Speed to 200000 (200G) (now 100000).
    • Add an entry: IPv4 178.216.40.62, IPv6 2001:7f8:5b::62, speed 20000 (20G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB89.46.144.19889.46.144.168 89.46.144.198 89.46.145.12
    IPv6 address missing from PeeringDB2001:678:3ac::1982001:678:3ac::168 2001:678:3ac::198 2001:678:3ac::367
    Port speed differs100G200G + 2 × 20G
    • In the entry with IPv4 89.46.144.198: set Speed to 200000 (200G) (now 100000).
    • Add an entry: IPv4 89.46.144.168, IPv6 2001:678:3ac::168, speed 20000 (20G), RS peer yes.
    • Add an entry: IPv4 89.46.145.12, IPv6 2001:678:3ac::367, speed 20000 (20G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

Map

Where EPIX.EPINET'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 300G across 2 exchanges.

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.188
178.216.41.252
2001:7f8:5b::188
2001:7f8:5b::507
2 × 100G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Poland EPIX.Warszawa Warsaw, Poland 89.46.144.198 2001:678:3ac::198 100G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs

EPIX.EPINET lists no facilities in PeeringDB.