GLWS · Seattle / United States
A north-western US option. If you run a second copy of an application here, think about how distance affects replication delay and your recovery process.
Where it is and who it suits.
LOCATION
Coordinates mark the city centre.
FACILITY
Where your servers in Seattle run.
Westin Building Exchange
The primary telecommunications hub and internet gateway for the Pacific Northwest, home to the Seattle Internet Exchange.
Map data © OpenStreetMap contributors · View larger map (opens in a new tab) · 47.6144, -122.3389
Two things to think through.
Seattle is a distinct northwestern reference when comparing western US deployment locations. If the project already has a primary environment elsewhere, decide whether the second environment serves users, receives backups or runs a standby application. Each purpose has a different data-transfer and recovery requirement.
A geographically separated copy can introduce delay between writes and their arrival elsewhere. Document how current the copy needs to be and how traffic would be moved during recovery. Measure the actual route before relying on any assumed relationship between two map pins.
Distances from Seattle to the closest GLWS locations.
United States
About 1,130 km away. Physical minimum round trip about 11 ms.
United States
About 1,140 km away. Physical minimum round trip about 11 ms.
United States
About 1,550 km away. Physical minimum round trip about 15 ms.
United States
About 2,700 km away. Physical minimum round trip about 27 ms.
Distances are straight-line between city centres. The minimum round trip assumes light in fibre at about 200,000 km a second and a straight cable. Real routes are longer, so always test from your own audience. For a second site that survives a regional outage, Dublin is about 7,280 km from Seattle.
A nearby server is only one part of your application.
Compare the route from the audience networks you expect to serve. Test real requests, not only a location label.
Count remote APIs, databases, sign-in providers and backup destinations when you plan.
Write down how data is restored and who can do it. A copy in another location only helps if you can recover from it.
Pick a product, then choose Seattle in the configurator.
KVM virtual servers for websites, applications and development.
Whole machines, with regional options.
Rack space, power and connectivity for your own hardware.
Quick answers before you choose.
Servers in Seattle run at Westin Building Exchange (WBX), 2001 Sixth Avenue, Seattle, WA 98121, USA.
Yes, for any product that offers this location. Your choice is saved with your configuration.
Test response times and throughput from representative audience networks. Include application dependencies and measure during periods relevant to your users.
Compare data handling, resource availability, backup arrangements and the practical process for recovery or on-site work.
Other locations in the same region.
United States / SJC
Development teams and apps serving the US west coast.
United States / SLC
Inland western US users and compute-heavy workloads.
United States / LAX
Users on the US west coast and around the Pacific.