ixreport

Nova86: PeeringDB fix list

AS401538 · peeringdb.com/net/38031

PeeringDB

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

Make the changes on Nova86'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 (3)

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

  1. United States HOUIX Houston, United States · PeeringDB 2835From its IX-F export and website members list
    IPv4206.83.136.66
    IPv62001:504:9e::66
    Speed10000 Mbps (10G)
    RS peerNot published
  2. United States MICE Minneapolis, MN, United States · PeeringDB 446From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.98
    IPv62001:504:98::98
    Speed10000 Mbps (10G)
    RS peerNot published

Correct these entries (1)

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 States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.51.7.186: set Speed to 10000 (10G) (now 1000).

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