Renesys: PeeringDB fix list

AS34135 · peeringdb.com/net/21

PeeringDB

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

Make the changes on Renesys'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 Renesys 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 Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
    IPv4206.72.210.34
    IPv62001:504:13::210:34
    Speed1000 Mbps (1G)

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.194.211
    IPv62001:7f8::fc55:0:1
    Speed1000 Mbps (1G)
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.225.224
    IPv62001:7f8:4::fc55:1
    Speed1000 Mbps (1G)

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