V4LESS: PeeringDB fix list

AS215250 · peeringdb.com/net/35836

10 things to fix in V4LESS's PeeringDB record, from what its exchanges publish: 10 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on V4LESS'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 (10)

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.

AMS-IX Amsterdam, Netherlands · PeeringDB 26

Problem PeeringDB has The export has

IPv4 address missing from PeeringDB none 80.249.213.30
- In the entry with IPv6 2001:7f8:1:0:a500:21:5250:1: set IPv4 to 80.249.213.30 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:9e:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8::3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX Hamburg Hamburg, Germany · PeeringDB 74

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:3d:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:3f:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX Madrid Madrid, Spain · PeeringDB 1277

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:a0:0:3:48d2:0:2: set Speed to 200000 (200G) (now 100).
DE-CIX Marseille Marseille, France · PeeringDB 1149

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:36:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX Munich Munich, Germany · PeeringDB 248

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:7f8:44:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
DE-CIX New York New York, United States · PeeringDB 804

Problem PeeringDB has The export has

Port speed differs 100M 200G
- In the entry with IPv6 2001:504:36:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64

Problem PeeringDB has The export has

IPv4 address missing from PeeringDB none 193.239.119.167
- In the entry with IPv6 2001:7f8:13::a521:5250:1: set IPv4 to 193.239.119.167 (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	none	80.249.213.30

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
Port speed differs	100M	200G

Problem	PeeringDB has	The export has
IPv4 address missing from PeeringDB	none	193.239.119.167

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