ixreport

NuCDN: PeeringDB fix list

AS23393 · peeringdb.com/net/311

PeeringDB

3 things to fix in NuCDN's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-10-08 18:53 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in NuCDN's PeeringDB record. Add one entry per connection with these values.

  1. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297From its IX-F export and website members list
    IPv4188.93.170.33
    IPv62001:7f8:4c::5b61:1
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (2)

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

  1. United States FL-IX Miami, United States · PeeringDB 954Not on its IX-F export or website members list
    IPv4206.41.108.32
    IPv62001:504:40:108::1:32
    Speed10000 Mbps (10G)
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.237.105
    IPv62001:7f8:4:1::5b61:1
    Speed10000 Mbps (10G)

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