ixreport

Nominet Nameservers: PeeringDB fix list

AS43519 · peeringdb.com/net/8280

PeeringDB

5 things to fix in Nominet Nameservers's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on Nominet Nameservers'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 (5)

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 differs2G10G
    • In the entry with IPv4 195.66.231.89: set Speed to 10000 (10G) (now 2000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs2G10G
    • In the entry with IPv4 195.66.236.23: set Speed to 10000 (10G) (now 2000).
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs2G10G
    • In the entry with IPv4 195.66.244.67: set Speed to 10000 (10G) (now 2000).
  4. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777
    ProblemPeeringDB hasThe export has
    Port speed differs2G10G
    • In the entry with IPv4 206.55.196.18: set Speed to 10000 (10G) (now 2000).
  5. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs4G5G
    • In the entry with IPv4 5.57.80.53: set Speed to 5000 (5G) (now 4000).

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