GLWS · Los Angeles / United States
A good fit when your users are along the Pacific coast of the United States. Match the network path to your audience, not just the city name.
Where it is and who it suits.
LOCATION
Coordinates mark the city centre.
FACILITY
Where your servers in Los Angeles run.
CoreSite
One of the most densely interconnected buildings in the world, with subsea cable landings linking the US West Coast to Asia-Pacific.
Map data © OpenStreetMap contributors · View larger map (opens in a new tab) · 34.0479, -118.2555
Two things to think through.
A project centred on a western US audience should compare Los Angeles with San Jose and Seattle before adding a distant replica. Include calls to the application database and external APIs in the comparison. A server close to the visitor can still wait on another region for the answer.
If the application also serves people across the Pacific, document which requests reach the US environment and which depend on services elsewhere. Use representative audience networks for any real test. Keep the recovery copy outside the working environment and verify how it would be restored.
Distances from Los Angeles to the closest GLWS locations.
United States
About 490 km away. Physical minimum round trip about 4.9 ms.
United States
About 930 km away. Physical minimum round trip about 9.3 ms.
United States
About 1,550 km away. Physical minimum round trip about 15 ms.
United States
About 1,990 km away. Physical minimum round trip about 20 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 8,300 km from Los Angeles.
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 Los Angeles 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 Los Angeles run at CoreSite LA1 (One Wilshire), 624 S. Grand Avenue, Los Angeles, CA 90017, 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 / SEA
Pacific Northwest users, or a replica away from Los Angeles and San Jose.