Pawel Kowalski BGCOM: PeeringDB fix list
AS52153 · peeringdb.com/net/12294
2 things to fix in Pawel Kowalski BGCOM's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Pawel Kowalski BGCOM'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:5b::426 - In the entry with IPv4 178.216.41.173: set IPv6 to 2001:7f8:5b::426 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:678:3ac::596 Port speed differs 5G 10G - In the entry with IPv4 89.46.145.216: set IPv6 to 2001:678:3ac::596 (now empty); set Speed to 10000 (10G) (now 5000).
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/52153/: 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.