MegaIX Miami: operator report
Miami, United States · PeeringDB 4362 · ixreport.com/ix/4362/report/
Members of MegaIX Miami that PeeringDB has wrong, from its IX-F export (10 networks, read 2026-10-08 21:25 UTC), against PeeringDB as of 2026-10-08 21:35 UTC. 2 networks to follow up.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (1)
These networks could add MegaIX Miami to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS11767 QTS Miami | IX-F | 206.53.168.16 2606:a980:0:b::10 |
No public contact |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 9 networks in both. Either the network's PeeringDB record or the export is out of date.
None: every network's addresses and port speed match.
In PeeringDB, not on your lists (1)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
| Network | In PeeringDB | Contact |
|---|---|---|
| AS42 PCH AS42 | 206.53.168.10 2606:a980:0:b::a |
No public contact |