Zalando: PeeringDB fix list
AS201026 · peeringdb.com/net/13134
2 things to fix in Zalando's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Zalando's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Zalando's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.81.196.221 IPv6 2001:7f8::3:1142:0:1 Speed 200000 Mbps (200G) RS peer Yes
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 Address belongs to another network in PeeringDB 80.81.196.221 is AS270711 Cloud Telecom LTDA 80.81.196.221 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/201026/: 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.