Gamma: PeeringDB fix list

AS31655 · peeringdb.com/net/4043

PeeringDB

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

Make the changes on Gamma'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. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G2 × 100G
    • In the entry with IPv4 195.66.244.113: set Speed to 100000 (100G) (now 20000).
    • In the entry with IPv4 195.66.244.20: set Speed to 100000 (100G) (now 20000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G + 40G
    • In the entry with IPv4 5.57.80.176: set Speed to 40000 (40G) (now 100000).

    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/31655/: 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.