Merula Limited: PeeringDB fix list

AS16353 · peeringdb.com/net/3764

PeeringDB

3 things to fix in Merula Limited's PeeringDB record, from what its exchanges publish: 3 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Merula Limited's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (3)

In PeeringDB, but on none of the exchange's own lists. If Merula Limited 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 LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.224.143
    IPv62001:7f8:4::3fe1:1
    Speed10000 Mbps (10G)
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.236.143
    IPv62001:7f8:4:1::3fe1:1
    Speed10000 Mbps (10G)
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
    IPv4195.66.244.44
    IPv62001:7f8:4:2::3fe1:1
    Speed10000 Mbps (10G)

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