Pacific Northwest Gigapop
BGP inherited
Cluster stats
| Netblocks | 26 |
| Registered in | United States (12) · Japan (1) |
| All fragments | 30 blocks across 4 clusters |
| Cluster ID | 213182299 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
26
0 netblocks since 2026-07-05
2026-07-05
peak 26
2026-07-19
IP Ranges (26)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 149.112.96.84/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 149.112.96.85/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 198.32.195.17/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 206.81.80.84/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 206.81.80.85/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 206.83.139.14/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.240.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.241.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.242.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.243.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.245.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 207.231.248.1/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 210.171.225.170/32 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:10::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:11::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:80::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:81::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:88::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:b:89::1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::65/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::85:0:65/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16:1::65/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16:1:0:85:0:65/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:504:9f::14/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:8::101:1/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
| 2620:124:2000::17/128 | Pacific Northwest Gigapop | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Pacific Northwest” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Pacific Northwest Net 2 blocks
- Pacific Northwest University of Health Sciences 1 blocks
- Pacific Northwest Surgical Associates 1 blocks
Network trust
what's this?
RPKI hygiene: B
how networks compare →
84.6%
of checked blocks have valid RPKI ROA coverage
(22 of 26)
No discrepancies found among checked blocks.
NIC Handles
AS101