Polkomtel: PeeringDB fix list
AS8374 · peeringdb.com/net/2214
One thing to fix in Polkomtel's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 212.91.0.51 212.91.0.51 212.91.0.99 IPv6 address missing from PeeringDB 2001:7f8:60::1:9 2001: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.
From ixreport.com/net/8374/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.