Opiquad: PeeringDB fix list

AS19754 · peeringdb.com/net/4608

PeeringDB

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

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

  1. United States SLIX - Salt Lake City Internet Exchange Salt Lake City, United States · PeeringDB 829From its IX-F export and website members list
    IPv4149.112.13.34
    IPv62001:504:105::34
    Speed10000 Mbps (10G)
    RS peerYes

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Opiquad 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 FD-IX - St. Louis St. Louis, MO, United States · PeeringDB 1519Not on its website members list
    IPv4206.71.10.26
    IPv62001:504:45:10::26
    Speed50000 Mbps (50G)

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

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