LWLcom: PeeringDB fix list

AS50629 · peeringdb.com/net/4961

PeeringDB

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

Make the changes on LWLcom'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 (4)

On the exchange's own member list, but not in LWLcom'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.10
    IPv62001:7f8:9e::c5c5:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.22
    IPv62001:7f8:3d::c5c5:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.13
    IPv62001:7f8:44::c5c5:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  4. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.39
    IPv62001:7f8:33::a105:629:1
    Speed2500 Mbps (2.5G)
    RS peerYes

    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 (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 BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 193.178.185.11: set Speed to 10000 (10G) (now 100000).

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

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

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

  3. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.20.137: set Speed to 12500 (12.5G) (now 100000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If LWLcom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany Community-IX Berlin, Frankfurt, Germany · PeeringDB 1329Not on its website members list
    IPv4185.1.74.19
    IPv62001:7f8:a5::5:629:2
    Speed100000 Mbps (100G)
    IPv4185.1.74.30
    IPv62001:7f8:a5::5:629:3
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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