MegaIX Seattle: operator report
Seattle, United States · PeeringDB 1174 · ixreport.com/ix/1174/report/
Members of MegaIX Seattle that PeeringDB has wrong, from its IX-F export (13 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 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 (0)
These networks could add MegaIX Seattle to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
None.
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 13 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS58580 Fastrack Technology | IPv6 address missing from PeeringDB | none | 2606:a980:0:4::12 | No public contact |
In PeeringDB, not on your lists (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.