ixreport

VSE NET GmbH: PeeringDB fix list

AS9063 · peeringdb.com/net/1918

PeeringDB

3 things to fix in VSE NET GmbH's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on VSE NET GmbH'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 (3)

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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs40G300G
    • In the entry with IPv4 185.1.170.44: set Speed to 300000 (300G) (now 40000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs40G300G
    • In the entry with IPv4 185.1.210.63: set Speed to 300000 (300G) (now 40000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs40G300G
    • In the entry with IPv4 185.1.208.52: set Speed to 300000 (300G) (now 40000).

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