GLWS · Miami / United States
Another Florida location. Compare external APIs and storage endpoints as well as user latency before you put a whole application stack here.
Where it is and who it suits.
LOCATION
Coordinates mark the city centre.
FACILITY
Where your servers in Miami run.
Equinix
A major internet exchange hub between the Americas, built to withstand Category 5 hurricane winds.
Map data © OpenStreetMap contributors · View larger map (opens in a new tab) · 25.7824, -80.1931
Two things to think through.
Miami can be a useful reference when planning an application whose audience spans the southeastern US and other markets. Identify the actual audience networks and external services involved. Do not turn a geographic association into a promise about routing to another country.
If one request needs data from several regions, record the order and frequency of those calls. A location change may improve one segment while leaving the slowest dependency unchanged. Compare the full action a visitor performs, including authentication and data retrieval.
Distances from Miami to the closest GLWS locations.
United States
About 330 km away. Physical minimum round trip about 3.3 ms.
United States
About 980 km away. Physical minimum round trip about 9.8 ms.
United States
About 1,500 km away. Physical minimum round trip about 15 ms.
United States
About 1,760 km away. Physical minimum round trip about 18 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, São Paulo is about 6,570 km from Miami.
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 Miami 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 Miami run at Equinix MI1 (NAP of the Americas), 50 NE 9th Street, Miami, FL 33132, 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 / ATL
South-eastern US users and regional application traffic.
United States / IAD
East-coast apps and services near Northern Virginia.