IGN GmbH: PeeringDB fix list
AS48484 · peeringdb.com/net/2596
One thing to fix in IGN GmbH's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on IGN GmbH'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 IPv6 address differs 2001:7f8:44::bd64:0:1 2001:7f8:44::bd64:0:2 IPv4 address missing from PeeringDB none 185.1.208.46 - In the entry with IPv6 2001:7f8:44::bd64:0:1: set IPv4 to 185.1.208.46 (now empty); set IPv6 to 2001:7f8:44::bd64:0:2 (now 2001:7f8:44::bd64:0:1).
From ixreport.com/net/48484/: 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.