Lepida: PeeringDB fix list

AS31638 · peeringdb.com/net/5493

PeeringDB

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

Make the changes on Lepida'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 Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export80.81.193.81 80.81.193.20380.81.193.81
    IPv6 address in PeeringDB, not in the export2001:7f8::7b96:0:1 2001:7f8::7b96:0:22001:7f8::7b96:0:2
    Port speed differs2 × 100G100G
    • The entry with IPv4 80.81.193.203, IPv6 2001:7f8::7b96:0:1 isn't in the export: delete it if that connection is gone.
  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G9G
    • In the entry with IPv4 195.66.228.27: set Speed to 9000 (9G) (now 10000).

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