rixCloud, Inc.: PeeringDB fix list

AS64271 · peeringdb.com/net/16440

PeeringDB

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

Make the changes on rixCloud, Inc.'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 rixCloud, Inc.'s PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Check these entries (3)

In PeeringDB, but on none of the exchange's own lists. If rixCloud, Inc. 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 FCIX Fremont, United States · PeeringDB 2163Not on its website members list
    IPv4206.80.238.29
    IPv62001:504:91::29
    Speed10000 Mbps (10G)

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

  2. United States KCIX Kansas City, United States · PeeringDB 249Not on its IX-F export or website members list
    IPv4206.51.7.89
    IPv62001:504:1b:1::89
    Speed1000 Mbps (1G)
  3. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.237.77
    IPv6–
    Speed1000 Mbps (1G)

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