ixreport

Zen Internet: PeeringDB fix list

AS13037 · peeringdb.com/net/100

PeeringDB

2 things to fix in Zen Internet's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Zen Internet'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 LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 200G
    • In the entry with IPv4 195.66.224.158: set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 195.66.227.74: set Speed to 200000 (200G) (now 100000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G2 × 100G
    • In the entry with IPv4 5.57.80.48: set Speed to 100000 (100G) (now 40000).
    • In the entry with IPv4 5.57.80.49: set Speed to 100000 (100G) (now 40000).

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