Pacific Northwest Gigapop

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks27 · 4,109 IPv4 addresses
IPv6 13 prefixes (largest 2001:504:16:1:0:85:0:65/128)
Registered in United States (13) · Japan (1)
All fragments 31 blocks across 4 clusters
Cluster ID214582058
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
27 +1 netblocks since 2026-07-05
2026-07-05 peak 27 2026-07-26

IP Ranges (27)

⬇ 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
209.124.176.0/20 Pacific Northwest Gigapop ARIN DIRECT ALLOCATION ● low

IPv6 ranges (13)

CIDR
2001:504:16:1:0:85:0:65/128
2001:504:16:1::65/128
2001:504:16::65/128
2001:504:16::85:0:65/128
2001:504:9f::14/128
2001:504:b:10::1/128
2001:504:b:11::1/128
2001:504:b:80::1/128
2001:504:b:81::1/128
2001:504:b:88::1/128
2001:504:b:89::1/128
2001:de8:8::101:1/128
2620:124:2000::17/128

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.2% of checked blocks have valid RPKI ROA coverage (23 of 27)
Possible discrepancies (1)

These blocks are registered to Pacific Northwest Gigapop but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

209.124.176.0/20 /20 authorized for AS101 — University of Washington

NIC Handles

AS101 PNG-4 PNGN-ARIN PNGN-ARIN PNGN-ARIN UW-NOC-ARIN