Columbia Colocation is an ISP-operated edge node in Quincy, WA — at the fiber crossroads of the Pacific Northwest. 10–20ms from Seattle. Sub-5ms across Grant County. Dedicated hardware and colocation for latency-sensitive workloads that can't afford the round-trip to us-west-2. No egress fees. No cloud margin. Direct fiber.
Columbia Colocation is lower latency to Seattle than AWS Oregon — with no egress fees and dedicated hardware.
Edge compute in the PNW context means dedicated hardware physically closer to your users and endpoints than a us-west-2 region — with ISP-level connectivity and no cloud margin baked in.
Columbia Colocation is operated by Crescent Bar Internet, LLC — an ISP on Grant County PUD's fiber. Your hardware connects through our routers directly onto the PUD network, not through a third-party data center with uplink contracts. That's as close to the fiber as you can get without being the ISP.
Quincy, WA sits at a major PNW fiber interconnection point. Long-haul routes connecting Seattle, Spokane, Portland, and beyond pass through Central Washington. Grant PUD's network rides this infrastructure — not a leased last-mile connection.
Edge workloads that need consistent performance can't share a hypervisor with noisy neighbors. Our bare metal is dedicated — one customer per server, full hardware access including iDRAC, no CPU credit games, no storage IOPS throttling.
Edge nodes that have to pay per-GB egress aren't really edge — they're just another cloud region with a latency sticker on it. Bandwidth on PUD fiber is unmetered. Move data between your edge node and your users without counting bytes.
Grant County businesses, utilities, agriculture, and government have essentially no good local compute option between them and Seattle data centers — or AWS Oregon. We're the local edge for all of Central Washington.
Bring your own hardware and colocate it — full control, your software stack. Or rent dedicated bare metal and deploy your workload without managing physical hardware. Both options, same network, same latency profile.
Technical buyers want real specs, not marketing language. Here's the honest breakdown of the infrastructure.
The buyers who get the most value from a Quincy edge node are generally dealing with one or more of these situations.
Gaming infrastructure, multiplayer servers, WebRTC applications, live video processing, financial data feeds, and any application where the round-trip to Oregon (20–35ms) is the bottleneck. A Quincy edge node cuts that in half for Seattle-area users.
Healthcare systems, utilities, agriculture tech, and municipal services in Central Washington that need local compute — not a 165-mile round-trip to Seattle for every database query. Sub-5ms latency within Grant County changes what's architecturally feasible.
Engineering teams that have identified predictable, high-egress workloads that are costing disproportionately in AWS or Azure. Moving a compute-heavy, bandwidth-intensive service to a dedicated edge node — flat rate, no egress billing — changes the economics significantly.
Teams building distributed systems that need a PNW-native node — for CDN origin, data locality, regional failover, or geographic redundancy from a us-west-2 primary. Quincy provides genuine geographic separation from AWS Oregon at a fraction of the cost of a second cloud region.
Bare metal at $99/mo flat. Colocation from $85/mo founder. No egress fees on any service. Full pricing details on our colocation page.
Tell us about your architecture and latency requirements — we'll talk through whether Quincy fits your edge strategy and what the right configuration looks like.