I run a community forum where the majority of users are in the Pacific Northwest. We are looking for a new dedicated server and I'm wondering if it is worth it to locate the server as close to the PNW as possible. We do have visitors from all around the world, but the vast majority of our returning traffic is in the PNW.

What are the reasons why this would not be a wise idea?

  • If you're in the PNW, Amazon EC2 has a Seattle datacenter.
    – ceejayoz
    Sep 13, 2012 at 16:28

1 Answer 1


Actually, in general it's a very good idea. However, it won't solve all your performance problems.

There's a nice big data center in Seattle (more than one, actually) that's very well connected, and if you are located there you'll have very short latency to most places in the Pacific Northwest. Though not all of them. The network doesn't always correspond exactly to geography; the shortest path between two points sometimes goes to unexpected places. But for the most part it does.

For traffic in the US, though, this probably won't buy you more than 100ms (I'm assuming you're currently colocated in Florida, about the longest path available that's still in the US) for your Pacific Northwest audience, and will make latency longer for a small percentage of your users.

In short, it'll help for most of your users, and make things worse for a very small fraction.

  • The company I'm looking at has their servers in the Westin building in downtown Seattle which is as far as I'm aware the best possible place to be as it sits right on a peering point. Sep 13, 2012 at 17:44
  • Been there. I don't think you can do better for peering in Seattle. Sep 13, 2012 at 17:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.