SpokaneIX: operator report
Spokane, United States · PeeringDB 3090 · ixreport.com/ix/3090/report/
Members of SpokaneIX that PeeringDB has wrong, from its website members list (15 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 4 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 (4)
These networks could add SpokaneIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS101 Pacific Northwest Gigapop | website | 206.83.139.14 2001:504:9f::14 |
No public contact |
| AS17193 AS17193 | website | 206.83.139.1 206.83.139.2 2001:504:9f::1 2001:504:9f::2 |
No PeeringDB record |
| AS30340 TierPoint Spokane | website | 206.83.139.7 2001:504:9f::7 |
No public contact |
| AS396040 Inland Cellular | website | 206.83.139.16 2001:504:9f::16 |
No public contact |
Addresses or port speeds that differ (0)
SpokaneIX publishes no IX-F export we could read, so addresses and port speeds can't be compared.
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.