SIX Seattle (Jumbo): operator report
Seattle, United States · PeeringDB 1285 · ixreport.com/ix/1285/report/
Members of SIX Seattle (Jumbo) that PeeringDB has wrong, from its IX-F export (68 networks, read 2026-10-08 20:54 UTC) and its website members list (68 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 5 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 SIX Seattle (Jumbo) to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS7782 Alaska Communications Systems Group, Inc. | IX-F and website | 149.112.96.47 2001:504:16:1::1e66 60G |
No public contact |
| AS63052 Columbia Basin Broadband Corporation | IX-F and website | 149.112.97.91 2001:504:16:1::f64c 10G |
No public contact |
| AS137409 Global Secure Layer | IX-F and website | 149.112.97.146 2001:504:16:1::2:18c1 100G |
No public contact |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 65 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 (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.