Freifunk Nordwest: PeeringDB fix list

AS206313 · peeringdb.com/net/13125

PeeringDB

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

Make the changes on Freifunk Nordwest'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 (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 differs1G10G
    • In the entry with IPv4 185.1.170.88: set Speed to 10000 (10G) (now 1000).
  2. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    Port speed differs10G100M
    • In the entry with IPv4 193.189.82.211: set Speed to 100 (100M) (now 10000).

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Freifunk Nordwest 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.37
    IPv62001:7f8:a5::20:6313:2
    Speed10000 Mbps (10G)
    IPv4185.1.74.38
    IPv62001:7f8:a5::20:6313:3
    Speed10000 Mbps (10G)

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

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