MegaIX Los Angeles: operator report
Los Angeles, United States · PeeringDB 1175 · ixreport.com/ix/1175/report/
Members of MegaIX Los Angeles that PeeringDB has wrong, from its IX-F export (27 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 6 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 (5)
These networks could add MegaIX Los Angeles to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS10310 Yahoo | IX-F | 206.53.172.14 2606:a980:0:5::e |
Technical: email address (needs JavaScript) |
| AS30188 TELEVERGENCE | IX-F | 206.53.172.31 2606:a980:0:5::1f |
No public contact |
| AS31050 Framestore | IX-F | 206.53.172.30 2606:a980:0:5::1e |
No PeeringDB record |
| AS396986 ByteDance | IX-F | 206.53.172.16 206.53.172.21 2606:a980:0:5::10 2606:a980:0:5::15 |
No public contact |
| AS399362 Shift4 Payments | IX-F | 206.53.172.33 2606:a980:0:5::21 |
No PeeringDB record |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 22 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 |
|---|---|---|
| AS3856 PCH AS3856 | 206.53.172.18 2606:a980:0:5::12 1G |
No public contact |