GLWS · Atlanta / United States
A south-eastern US location. Size compute and transfer separately: a well-placed server still needs enough memory and disk for its workload.
Where it is and who it suits.
LOCATION
Coordinates mark the city centre.
FACILITY
Where your servers in Atlanta run.
Digital Realty
Atlanta’s primary carrier hotel and one of the most connected buildings in the region.
Map data © OpenStreetMap contributors · View larger map (opens in a new tab) · 33.7554, -84.3913
Two things to think through.
Atlanta is a southeastern US reference to compare with eastern and southern locations. Identify where the application visitors and operators connect from, then include the dependencies used by their requests. Choose a location for the workflow rather than only the nearest city on the map.
If the audience expands beyond the original region, measure whether the existing environment is limited by capacity or request distance. A larger memory tier and a second geographic environment solve different problems. Keep that distinction clear when planning the next deployment.
Distances from Atlanta to the closest GLWS locations.
United States
About 670 km away. Physical minimum round trip about 6.7 ms.
United States
About 850 km away. Physical minimum round trip about 8.5 ms.
United States
About 950 km away. Physical minimum round trip about 9.5 ms.
United States
About 980 km away. Physical minimum round trip about 9.8 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 6,310 km from Atlanta.
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 Atlanta 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 Atlanta run at 56 Marietta Street, 56 Marietta Street NW, Atlanta, GA 30303, 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 / TPA
Florida users and a second south-eastern US option.
United States / IAD
East-coast apps and services near Northern Virginia.
United States / CHI
Apps that need to reach users across the whole US.