Distinct New Media: PeeringDB fix list
AS48067 · peeringdb.com/net/17059
One thing to fix in Distinct New Media's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Distinct New Media'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 missing from PeeringDB none 2001:7f8:64:225:0:4:8067:1 Port speed differs 1G 100M - In the entry with IPv4 86.104.125.116: set IPv6 to 2001:7f8:64:225:0:4:8067:1 (now empty); set Speed to 100 (100M) (now 1000).
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/48067/: 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.