Network Advisors: PeeringDB fix list
AS17303 · peeringdb.com/net/14782
3 things to fix in Network Advisors's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Network Advisors'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 Network Advisors's PeeringDB record. Add one entry per connection with these values.
-
SpringIX Springfield, MO, United States · PeeringDB 3195From its IX-F export and website members listIPv4 149.112.4.8 IPv6 2001:504:100::8 Speed 100000 Mbps (100G) RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G + 10G - In the entry with IPv4 206.51.7.21: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 200G 100G - In the entry with IPv4 206.83.12.120: set Speed to 100000 (100G) (now 200000).
From ixreport.com/net/17303/: 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.