Latency from Boise to Seattle, Portland, Salt Lake City and more

This section answers one question: how long it takes a packet to get from our servers in Boise to the people using them. We publish the figures we’ve measured and explain what they mean for workloads where milliseconds show up, like game servers, VoIP, video calls and VPNs.

What latency do you get from a server in Boise?

These are our measured figures:

  • Treasure Valley businesses: under 5 ms (same network and building as IDACORE Boise)
  • Salt Lake City: 14 ms
  • Portland: 22 ms
  • Seattle: 23 ms

Our servers sit in the IDACORE Boise datacenter. Our own network uses two upstreams, Lumen (AS3356) and Cogent (AS174), with Cisco routers, an Arista switch fabric and every hypervisor bonded across two switches. ServerVerify gives it a network grade “A”. If those routes match where your users are, see our Boise VPS hosting plans.

What will you find in this section?

Guides to reading and using these numbers. Expect plain explanations of round-trip time, why jitter matters as much as the average for voice and games, and how to test the path from your own network with ping, mtr and traceroute. We’ll also cover picking a server location when your players, callers or team are split between the Treasure Valley, Salt Lake City, Portland and Seattle. Every figure about ADTAQ here comes from our measured list, never an estimate.

Part of Boise.

All Latency guides

No guides here yet. Meanwhile, browse everything in Boise.

Frequently asked questions.

We measure 23 ms of latency from Boise to Seattle. On the same list of routes, Portland is 22 ms and Salt Lake City is 14 ms from our servers in the IDACORE Boise datacenter. Your own result depends on your ISP and the path your traffic takes, so run ping or mtr from your connection to see the route you'll use.

A Boise VPS sits between Salt Lake City and Portland. We measure 14 ms to Salt Lake City and 22 ms to Portland, plus 23 ms to Seattle. When a group of players or callers is spread across the region, a server near the middle keeps everyone on a similar footing. Test from each person's connection before you commit, because home ISPs route differently.

Our servers run on the same network and in the same building as IDACORE Boise, which reaches Treasure Valley businesses in under 5 ms. For a local office, a server that close keeps VoIP phones, remote desktops and a self-hosted VPN feeling near to a machine on the office network, without the long round trip to a distant cloud region.