Which server region should I choose if my customers are in Colombia, Mexico or Peru?

Dongee Cloud has 11 locations: for customers in Mexico, use the Mexico location; for Colombia and Peru, test nearby regions like Miami, Dallas, Santiago or São Paulo and measure latency before deciding.

Dongee Cloud has 11 locations, and finding the best server region Latin America has to offer depends on where your users are. For Mexico, the Mexico location is the natural choice. Colombia and Peru have no in-country location, so test Miami, Dallas or Mexico for Colombia and Santiago, São Paulo or Miami for Peru, then measure latency before deciding. In this guide we explain what changes when you pick a region, how to measure in six steps and which mistakes to avoid.

Updated on November 21, 2026 · Dongee Team

What really changes when you choose your server's region?

The region is the physical data center where your server runs. Choosing it well mainly affects two things:

  • Latency: the time it takes a packet to travel from your user's browser to the server and back. It doesn't depend only on distance on the map: the routes of internet carriers, traffic exchange points and the way each internet provider in your country routes connections also matter. That's why two cities that look equally close can give very different results.
  • Data residency: some companies, by contract or because of the rules of their industry, must store data in a specific country or jurisdiction. If that's your case, review the requirement with your legal advisor before choosing a region, because it can rule out options that are technically good.

There's a third, less visible factor: the region where the services your app talks to are running, such as an external API, a payment gateway or a third-party managed database. If your server is close to the user but every request has to travel to another continent and back, the advantage is lost.

Which location should you test based on your customers' country?

This table doesn't tell you which one is fastest (you'll only know that by measuring from your users' network). It tells you where to start testing.

Where your users areCandidate locations to testNotes
ColombiaMiami, Dallas, MexicoThere's no location in Colombia. Compare at least two from Bogotá, Medellín or the city where most of your traffic comes from.
MexicoMexicoIt's the natural choice. If you have many users in northern Mexico or in the US, add Dallas to the test.
PeruSantiago, São Paulo, MiamiThere's no location in Peru. International routes vary by carrier, so measure from Lima and from your users' mobile connections.
Rest of Central and South AmericaMiami, Mexico, Santiago, São PauloFor Central America and the Caribbean, start with Miami or Mexico. For the Southern Cone, start with Santiago or São Paulo.
Customers in the USAtlanta, Miami, New York, DallasChoose based on the coast or area where your users are concentrated.
Customers in SpainMadridIf you also serve the rest of Europe, compare Madrid with Frankfurt, London or Amsterdam.

If your audience is spread across several countries, choose the location that gives an acceptable result for the largest group and check how the others do. If the gap is large, you can run servers in two regions behind your own load balancer (Nginx or HAProxy). Dongee doesn't sell a managed load balancer, so you configure that layer yourself.

How do you measure latency before deciding?

A test server for a few days gives you real data for little money. On Dongee Cloud, deployment takes less than 3 minutes, and the smallest plan, Cloud 1, costs 17 USD/month. This is the procedure:

  1. Create a test server in two candidate locations. For Colombia, for example, one in Miami and another in Mexico. If you want to fine-tune resources, with Cloud On Demand you choose vCPU, RAM and disk (17 USD/month minimum). To estimate the final cost, follow the guide to calculate the price of a custom cloud server.
  2. Measure with ping and mtr from your users' city. Do it from a real home or office connection, not from another server. Run ping -c 50 SERVER_IP and mtr -rwc 100 SERVER_IP against each server, at different times of day. If you can, ask a colleague or customer in another city or on another carrier to repeat the test. In mtr, look at packet loss and at the hops where the time spikes.
  3. Run a load test with your real app. Install the application on both servers (if you don't connect through a terminal yet, here's how to connect to a cloud server via SSH from Windows or Mac). Measure time to first byte, full load of your key pages and behavior with several simultaneous users. Ping tells you what the network is like; this test tells you what the user is going to feel.
  4. Decide with data. Compare medians and peaks, not a single result. If both locations come out very close, break the tie with the rest of your architecture: where your external APIs, your database or your other servers are.
  5. Take a snapshot of the winning server. All Dongee Cloud plans include incremental snapshots and disk backup. Take a snapshot before any big change so you can roll back.
  6. Migrate and delete the server you won't use. Move your project to production in the chosen location, update the DNS records and shut down the test server so it stops generating costs. If you're coming from another provider, Dongee Cloud includes assisted migration, and 24/7 human support in your language (the platform translates on the fly) helps you review it.

When does the region matter less?

In some projects the server location is barely noticeable:

  • Static sites behind a CDN: if your website is HTML, CSS and image files served by a content delivery network, the user downloads them from a nearby node and the origin server carries little weight.
  • Apps whose bottleneck is an AI model's API: if every response waits several seconds for the model to generate text, gaining a few milliseconds of network doesn't change the experience. What matters most is the model, streaming and how you display the response as it arrives.
  • Background processes: scheduled tasks, queues or nightly reports that don't serve a user in real time.

Which Dongee products don't let you choose a region?

Choosing a location applies to Dongee Cloud. Dongee shared hosting and Dongee Business Hosting run on servers in Canada, and Dongee AI Router (a prepaid gateway to access AI models through a single API) has its data center in Canada. In those products you don't choose a region: if location is a critical requirement for your project, the way to go is Cloud. To compare managed and self-managed options, see this guide on cloud servers for businesses with support in your language.

What mistakes should you avoid when choosing a region?

  • Choosing by closeness on the map without measuring. Internet routes don't follow straight lines. A location that looks far away may have better connectivity with your country than a closer one, or the other way around. Always measure.
  • Splitting the app and the database across different regions. Every database query crosses the network between regions, and a page with dozens of queries piles up that delay. Keep the app and the database in the same location and, if you use several servers, connect them over the private network, which has no cost.
  • Measuring only once. Latency changes by time of day and carrier. Repeat the tests at different times.
  • Measuring only from office fiber. If a good share of your users come in from their phones, include mobile connections in the tests.
  • Forgetting external services. Check where your APIs, your payment gateway or your external database are before deciding.

Frequently asked questions

Does Dongee Cloud have servers in Colombia or Peru?

No. The 11 locations are Atlanta, Miami, New York, Dallas, Mexico, São Paulo, Santiago, Frankfurt, Madrid, London and Amsterdam. For Colombia, it's worth testing Miami, Dallas or Mexico, and for Peru, Santiago, São Paulo or Miami.

What's the fastest location for Colombia?

It depends on the carrier and the city where your users are, so there's no single answer. Create test servers in two locations and measure with ping, mtr and a load test of your app from your customers' real network.

Can I change regions after signing up?

Yes, but it means creating a server in the new location, moving the project and updating DNS. Take a snapshot or backup first, and if you have questions, 24/7 support helps you review it.

Can I have servers in several regions at once?

Yes. You can create servers in different locations and set up your own load balancer with Nginx or HAProxy. Dongee doesn't offer a managed load balancer, so that configuration is up to you.

Does shared hosting let me choose a region?

No. Dongee shared hosting and Dongee Business Hosting are on servers in Canada. If you need to choose the location, the option is Dongee Cloud.

In short: for users in Mexico, use the Mexico location. For Colombia and Peru, pick two nearby candidates, measure for a few days with your real app and keep the one that gives you the best data. If you want to start testing, check the Dongee Cloud plans. 24/7 human support in your language (the platform translates on the fly) is available by chat or WhatsApp, even before you sign up.

Comenta lo que quieras

Unete a la charla
Solo ingresa tu email