ixreport

linefinity networks: PeeringDB fix list

AS203440 · peeringdb.com/net/22968

PeeringDB

4 things to fix in linefinity networks's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on linefinity networks'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 (3)

On the exchange's own member list, but not in linefinity networks's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.196.192
    IPv62001:7f8::3:1ab0:0:1
    Speed2000 Mbps (2G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.211
    IPv62001:7f8:3d:0:3:1ab0:0:1
    Speed1000 Mbps (1G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.26
    IPv62001:7f8:44:0:3:1ab0:0:1
    Speed2000 Mbps (2G)
    RS peerYes

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 KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 250M250M

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

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