GoCodeIT AS835: PeeringDB fix list

AS835 · peeringdb.com/net/30339

PeeringDB

4 things to fix in GoCodeIT AS835's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on GoCodeIT AS835'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 (2)

On the exchange's own member list, but not in GoCodeIT AS835'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.62
    IPv62001:504:9e::62
    Speed40000 Mbps (40G)
    RS peerNot published
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.95
    IPv62001:504:98::95
    Speed40000 Mbps (40G)
    RS peerNot published

Correct these entries (2)

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 DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 206.82.104.5: set Speed to 100000 (100G) (now 40000).
  2. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777
    ProblemPeeringDB hasThe export has
    Port speed differs100G30G
    • In the entry with IPv4 206.55.196.66: set Speed to 30000 (30G) (now 100000).

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