Vodafone Germany: PeeringDB fix list

AS3209 · peeringdb.com/net/319

PeeringDB

3 things to fix in Vodafone Germany's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Vodafone Germany'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 (2)

On the exchange's own member list, but not in Vodafone Germany's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.146
    IPv62001:7f8:9e::c89:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  2. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.17
    IPv62001:7f8:44::c89:0:1
    Speed100000 Mbps (100G)
    RS peerYes

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.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 600G
    • In the entry with IPv4 80.81.192.117: set Speed to 600000 (600G) (now 100000).
    • In the entry with IPv4 80.81.193.117: set Speed to 600000 (600G) (now 100000).

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