MegaIX Chicago: operator report
Chicago, United States · PeeringDB 4507 · ixreport.com/ix/4507/report/
Members of MegaIX Chicago that PeeringDB has wrong, from its IX-F export (13 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 2 networks to follow up; 1 with a public PeeringDB contact.
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 Chicago to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS394968 QTS Chicago | IX-F | 206.53.206.14 2606:a980:0:d::e |
No public contact |
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 12 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS395505 iManage | IPv6 address missing from PeeringDB | none | 2606:a980:0:d::d | NOC: email address (needs JavaScript) +13126677000 |
In PeeringDB, not on your lists (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.