ixreport

eDial

AS43495 · eDial

eDial Internet Sp. z o.o.

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

Tools: Where can I peer with eDial? · Where should eDial peer next? · Compare eDial 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 eDial's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on eDial'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
    IPv6 address missing from PeeringDBnone2001:7f8:5b::45
    Port speed differs10G40G
    • In the entry with IPv4 178.216.40.45: set IPv6 to 2001:7f8:5b::45 (now empty); set Speed to 40000 (40G) (now 10000).

    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
    Port speed differs10G40G
    • In the entry with IPv4 89.46.145.193: set Speed to 40000 (40G) (now 10000).

    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

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 eDial'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 20G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.45 10G Yes Both IPv6 not in PeeringDBSpeed differs
Poland EPIX.Warszawa Warsaw, Poland 89.46.145.193 2001:678:3ac::598 10G Yes Both Speed differs
Poland TPIX PL Warsaw, Poland 195.149.234.47 Both

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

These exchanges have a switch in a facility where eDial lists itself in PeeringDB, but don't have eDial 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 4 Data Center
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 4 Data Center
Poland THINX WarsawWarsaw, Poland 194 4 Data Center
Netherlands Global-IXAmsterdam, Netherlands 138 4 Data Center
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 4 Data Center
Facilities (2)

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

Poland 4 Data CenterKatowice 2 of 7
Poland DCENTER.PL - FT21Warsaw No exchange