Team Cymru Monitoring: PeeringDB fix list

AS401690 · peeringdb.com/net/39768

PeeringDB

3 things to fix in Team Cymru Monitoring'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 Team Cymru Monitoring'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 differs100M50M
    • In the entry with IPv4 195.66.228.11: set Speed to 50 (50M) (now 100).
  2. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs100M50M
    • In the entry with IPv4 195.66.244.81: set Speed to 50 (50M) (now 100).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Team Cymru Monitoring has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95Not on its website members list
    IPv4210.173.177.185
    IPv62001:7fa:7:1:0:40:1690:1
    Speed100 Mbps (100M)

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

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