ixreport

Polkomtel

AS8374 · Plus

Polkomtel Sp. z o.o.

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Polkomtel'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 THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB212.91.0.51212.91.0.51 212.91.0.99
    IPv6 address missing from PeeringDB2001:7f8:60::1:92001:7f8:60::1:9 2001:7f8:60::8374:b
    • In the entry with IPv4 212.91.0.51: set IPv4 to (empty) (now 212.91.0.51).
    • Add an entry: IPv4 212.91.0.51, IPv6 –, speed 400000 (400G).
    • Add an entry: IPv4 –, IPv6 2001:7f8:60::8374:b, speed 400000 (400G).
    • Add an entry: IPv4 212.91.0.99, IPv6 –, speed 400000 (400G).

    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

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

Map

Where Polkomtel'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 1.1T across 5 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.200 2001:7f8::20b6:0:1 100G 60 routes Both
Poland Equinix Warsaw Warsaw, Poland 195.182.218.6 2001:7f8:42::a500:8374:1 200G Yes PeeringDB
Poland POZIX Poznan, Poland 185.1.4.40 2001:7f8:4b::28 20G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.0.51 2001:7f8:60::1:9 400G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Poland TPIX PL Warsaw, Poland 195.149.232.103
195.149.232.231
2001:7f8:27::8374:1
2001:7f8:27::8374:2
2 × 200G Yes Both

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

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

Facilities (3)

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

Poland Equinix WA1 - Warsaw, Centrum LIMWarsaw 3 of 13
Poland LIM WarsawWarsaw 3 of 11
Poland ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)Warsaw 2 of 8