QTS Miami: PeeringDB fix list
AS11767 · peeringdb.com/net/11614
2 things to fix in QTS Miami's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on QTS Miami'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 QTS Miami's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.53.168.16 IPv6 2606:a980:0:b::10 Speed Not published RS peer Yes 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 (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.
-
Problem PeeringDB has The export has Port speed differs 10G 100G + 10G
From ixreport.com/net/11767/: 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.