No One Internet: PeeringDB fix list

AS49375 · peeringdb.com/net/2764

PeeringDB

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

Make the changes on No One 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 (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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G8G
    • In the entry with IPv4 195.66.224.36: set Speed to 8000 (8G) (now 10000).

Check these entries (1)

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

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.236.36
    IPv62001:7f8:4:1::c0df:1
    Speed3000 Mbps (3G)

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