Pacific Northwest Gigapop
AS101 · PNWGP
Tools: Where can I peer with Pacific Northwest Gigapop? · Where should Pacific Northwest Gigapop peer next? · Compare Pacific Northwest Gigapop with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in Pacific Northwest Gigapop's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Pacific Northwest Gigapop's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Pacific Northwest Gigapop's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.83.139.14 IPv6 2001:504:9f::14 Speed Not published RS peer Not published
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 198.32.195.17: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where Pacific Northwest Gigapop's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| JPIX TOKYO Tokyo, Japan | 100G | Both | |
| NWAX Portland, United States | 10G | Both Speed differs | |
| Pacific Wave West Coast, United States | 6 × 400G | PeeringDB | |
| SIX Seattle Seattle, United States | 2 × 100G | Both | |
| SIX Seattle (Jumbo) Seattle, United States | 2 × 100G | Both | |
| SpokaneIX Spokane, United States | Website list only |
These exchanges have a switch in a facility where Pacific Northwest Gigapop lists itself in PeeringDB, but don't have Pacific Northwest Gigapop as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| NetIXSofia, Bulgaria | 204 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| MegaIX SeattleSeattle, United States | 15 |
Facilities (3)
The buildings Pacific Northwest Gigapop lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty Seattle SEA10Seattle | 3 of 5 | |
| PTOR1Portland | 1 of 2 | |
| US Bank BuildingSpokane | 1 of 1 |