ixreport

DE-CIX Munich Route Servers: PeeringDB fix list

AS47228 · peeringdb.com/net/6979

PeeringDB

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

Make the changes on DE-CIX Munich Route Servers'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.

  1. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.208.252 185.1.209.252185.1.208.66 185.1.208.252 185.1.209.252
    IPv6 address missing from PeeringDB2001:7f8:44::b87c:0:1 2001:7f8:44::b87c:0:22001:7f8:44::b87c:0:1 2001:7f8:44::b87c:0:2 2001:7f8:44::b87c:42:1
    Port speed differs2 × 1G3 × 20G
    • In the entry with IPv4 185.1.208.252: set Speed to 20000 (20G) (now 1000).
    • In the entry with IPv4 185.1.209.252: set Speed to 20000 (20G) (now 1000).
    • Add an entry: IPv4 185.1.208.66, IPv6 2001:7f8:44::b87c:42:1, speed 20000 (20G), RS peer no.

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