ixreport

vitroconnect GmbH: PeeringDB fix list

AS57353 · peeringdb.com/net/4419

PeeringDB

3 things to fix in vitroconnect GmbH's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on vitroconnect GmbH'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 vitroconnect GmbH's PeeringDB record. Add one entry per connection with these values.

  1. Germany MegaIX Hamburg Hamburg, Germany · PeeringDB 291From its IX-F export
    IPv4193.42.155.44
    IPv62001:7f8:8:10:0:e009:0:1
    SpeedNot published
    RS peerNo

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (2)

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 differs20G100G
    • In the entry with IPv4 185.1.170.208: set Speed to 100000 (100G) (now 20000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 80.81.193.182: set Speed to 100000 (100G) (now 40000).

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