ixreport

INTERTELL

AS208041 · INTERTELL

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

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

Make the changes on INTERTELL'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. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G2 × 40G
    • In the entry with IPv4 178.216.42.77: set Speed to 40000 (40G) (now 20000).
    • In the entry with IPv4 178.216.42.78: set Speed to 40000 (40G) (now 20000).

    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

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

Map

Where INTERTELL'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 70G across 4 exchanges.

Poland CIX KR Krakow, Poland 93.159.151.77 10G Yes PeeringDB
Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.42.77
178.216.42.78
2001:7f8:5b::635
2001:7f8:5b::636
2 × 20G Yes Both Speed differs
Poland Equinix Warsaw Warsaw, Poland 195.182.219.149 2001:7f8:42::20:8041:1 10G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.1.30 10G Yes Both

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

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

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

Poland 4 Data CenterKatowice 2 of 7