ixreport

Quicktel

AS57945

Quicktel Sp. z o.o.

2Exchanges
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
1To fix in PeeringDB
1Facility in PeeringDB

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

Make the changes on Quicktel'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
    IPv4 address in PeeringDB, not in the export178.216.40.80 178.216.41.189178.216.40.80
    IPv6 address in PeeringDB, not in the export2001:7f8:5b::80 2001:7f8:5b::4582001:7f8:5b::80
    Port speed differs2 × 10G10G
    • The entry with IPv4 178.216.41.189, IPv6 2001:7f8:5b::458 isn't in the export: delete it if that connection is gone.

    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 Quicktel'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 30G across 2 exchanges.

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.80
178.216.41.189
2001:7f8:5b::80
2001:7f8:5b::458
2 × 10G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs
Poland TPIX PL Warsaw, Poland 195.149.234.71 10G Yes Both

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

These exchanges have a switch in a facility where Quicktel lists itself in PeeringDB, but don't have Quicktel 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 (1)

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

Poland 4 Data CenterKatowice 2 of 7