Vimexx: PeeringDB fix list

AS206281 · peeringdb.com/net/12906

One thing to fix in Vimexx's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Vimexx'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.

NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:7f8:13::a520:6281:1
- In the entry with IPv4 193.239.118.27: set IPv6 to 2001:7f8:13::a520:6281:1 (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:7f8:13::a520:6281:1

From ixreport.com/net/206281/: 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.