Devcat: PeeringDB fix list

AS216182 · peeringdb.com/net/34381

PeeringDB

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

Make the changes on Devcat'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 (4)

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:4c76:1
    SpeedNot published
    RS peerYes
  2. United States FREMIX Fremont, United States · PeeringDB 3685From its website members list
    IPv4149.112.29.108
    IPv62001:504:125:e0::108
    SpeedNot published
    RS peerNot published
  3. United States NVIX Ashburn, United States · PeeringDB 4462From its website members list
    IPv4149.112.60.107
    IPv62001:504:125:e2::107
    SpeedNot published
    RS peerNot published
  4. Canada ONIX Toronto, Canada · PeeringDB 4059From its IX-F export and website members list
    IPv4149.112.50.109
    IPv62001:504:125:e1::109
    Speed1000 Mbps (1G)
    RS peerYes

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

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