ConnectIT Marcin Hajka: PeeringDB fix list
AS56783 · peeringdb.com/net/11976
2 things to fix in ConnectIT Marcin Hajka's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on ConnectIT Marcin Hajka'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::94 - In the entry with IPv4 178.216.40.94: set IPv6 to 2001:7f8:5b::94 (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 IPv4 address missing from PeeringDB 89.46.144.246 89.46.144.229 89.46.144.246 IPv6 address missing from PeeringDB none 2001:678:3ac::246 2001:678:3ac::700 Port speed differs 1G 2 × 10G - In the entry with IPv4 89.46.144.246: set IPv6 to 2001:678:3ac::246 (now empty); set Speed to 10000 (10G) (now 1000).
- Add an entry: IPv4 89.46.144.229, IPv6 2001:678:3ac::700, speed 10000 (10G), RS peer yes.
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/56783/: 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.