MegaIX Bay Area: operator report
San Francisco, United States · PeeringDB 4508 · ixreport.com/ix/4508/report/
Members of MegaIX Bay Area that PeeringDB has wrong, from its IX-F export (21 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 3 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 (3)
These networks could add MegaIX Bay Area to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS22369 ONEMIND-01 | IX-F | 206.53.206.134 2606:a980:0:e::6 |
No public contact |
| AS40913 QTS Santa Clara | IX-F | 206.53.206.137 2606:a980:0:e::9 |
No public contact |
| AS499999999 CNS Support | IX-F | 206.53.206.155 2606:a980:0:e::1b |
No PeeringDB record |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 18 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 (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.