How to choose a country for your server
Put the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
A server country comes down to three questions, and the first two are usually enough. Where do the people who will open the site or connect to the server live? Does the site handle personal data, such as sign-ups, orders with names and addresses, or contact forms, and whose data is it? Only then, if two options are equal, comes the question of where it is cheaper and how it is easier to pay.
Below I go through each question, show what the same server costs in different countries, and how to measure in ten minutes which country is closer to your users, not on the map but over the network.
Every thousand kilometres costs 10 ms
A signal in optical fibre travels about 200 km per millisecond. Ping measures the round trip, so every 100 km in a straight line adds about 1 ms, and a real cable is always longer than the straight line. Hence these rough figures:
| Server in | From London | From Frankfurt | From New York |
|---|---|---|---|
| London | 1–5 ms | 12–18 ms | 70–80 ms |
| Amsterdam | 5–10 ms | 7–10 ms | 75–85 ms |
| Frankfurt | 12–18 ms | 1–5 ms | 85–95 ms |
| Helsinki | 35–40 ms | 25–30 ms | 100–110 ms |
| US East Coast | 70–80 ms | 85–95 ms | 1–10 ms |
| US West Coast | 135–150 ms | 145–160 ms | 60–70 ms |
| Singapore | 160–180 ms | 150–170 ms | 220–240 ms |
| Tokyo | 220–240 ms | 230–250 ms | 160–180 ms |
| Sydney | 250–280 ms | 260–290 ms | 200–220 ms |
These are guidelines, not a promise. The route between two networks can go through a third country and double the delay, so check your candidates yourself, as shown below.
What does this mean for a website? On the first visit the browser exchanges three or four round trips with the server before it gets the first byte of the page: the connection, encryption, the request itself. The difference between a ping of 10 and 50 ms turns into 0.12–0.16 seconds on the first load. For a blog that is barely noticeable. For a shop where a page loads data with several requests, it is. And for a game server or a remote desktop, the difference between 20 and 120 ms is felt in every mouse movement.
In a big country the city matters more than the country
If your visitors are in California and the server is in New York, they are 60–70 ms away, almost as far as New York is from London. For a site with an audience across the whole United States, the East Coast (New York, Virginia) or the centre of the country (Chicago, Dallas) is a sensible middle ground, because the main backbones of all large networks meet there. If nearly all your customers are on one coast, look for a data centre on that coast: VPS in the USA.
Europe works the other way round: it is compact, and Frankfurt, Amsterdam and London are within 30–40 ms of most of the continent. For a European audience any of these hubs will do, and the choice comes down to the host and the price: VPS in Europe.
Personal data: where it sits and who is responsible
Personal data is not only passport numbers. A name and phone number in an order form, an email address at sign-up, a delivery address, even an IP address in your logs all count. Wherever the server is, three things apply to almost any site that collects such data:
- Know where the data physically sits. The database, the backups and the logs are all on servers in a specific country, and that country's law applies to them. Write it down: you will need it for the privacy policy and if a customer asks.
- Publish a privacy policy. It should say what data you collect, why, how long you keep it and who you share it with, including your hosting provider.
- The host is your processor. It stores the data on your behalf, so the contract with it matters. Reputable hosts publish a data processing agreement (DPA) that sets out how they protect data and when they can access it.
GDPR if you have users in the EU
If the site serves people in the EU, the GDPR applies to you even if your company is outside the EU. The regulation does not require the server to be in Europe, but it does require that personal data sent outside the EU and EEA is protected to the same level.
The simplest option is to host in the EU or EEA, for example in Germany, the Netherlands or Finland, and sign the host's DPA. Then the data does not leave Europe and there is no transfer question. If you choose a host outside the EU, you need a DPA plus a legal basis for the transfer: the destination country is covered by an EU adequacy decision, or the host signs the standard contractual clauses. Most large international hosts offer both, but check before you put customer data on the server.
A blog without forms, comments or sign-ups has far less to worry about. This is not legal advice: if you are not sure what data you handle or which rules apply to you, ask a lawyer. It costs less than a fine.
What the same server costs in different countries
I took VPS plans from the accsly catalog of 27 October 2026, picked servers with 2 and 4 GB of memory in each country and found the median monthly price, counting only countries with at least 40 such plans. The catalog stores prices in roubles, so the dollar figures are converted and rounded.
| Country | 2 GB | 4 GB |
|---|---|---|
| Turkey | $8 | $14 |
| Russia | $9 | $15 |
| Finland | $10 | $16 |
| Germany | $10 | $18 |
| USA | $11 | $19 |
| Netherlands | $11 | $20 |
| Poland | $11 | $20 |
| France | $12 | $22 |
| United Kingdom | $15 | $23 |
| Singapore | $20 | $32 |
| Japan | $19 | $37 |
| Australia | $21 | $37 |
From the table the Netherlands looks 10–15% dearer than Germany. But that is a difference between markets, not between countries. The Netherlands has many hosts with expensive cloud platforms, while other markets have a larger share of low-cost plans. It is fairer to compare the same plan at the same host. I found 849 cases where a host sells an identical configuration in several countries as separate plans. Germany, the Netherlands, Russia, Finland and France cost the same at the median of this sample, and the US is only 7% dearer than Germany. Singapore is 38% dearer than Germany, Australia 47%, India 53% and Japan 57%.
The conclusion is simple. Within Europe and the US you do not choose a country by price, you choose a host. Take a server in Asia or Australia only if your users are there: you will pay about one and a half times as much for the same memory.
Payment and support depend on the country too
International hosts take Visa and Mastercard almost everywhere, and many also accept PayPal. If you are an EU customer, expect VAT to be added at checkout unless you enter a valid VAT number for your business; compare prices including tax. Most hosts bill monthly, and many give a discount for a year paid in advance. Take the annual plan only after you have tested the host for a month or two.
Support in your language and your time zone also costs money, it is just not written in the plan. If the server goes down at 3 a.m. your time, an answer within an hour and an answer when the working day starts in California are two very different nights.
Tasks where the country is already chosen
- Telegram bot. A server in Europe: Telegram's servers are in Amsterdam, and from Europe a bot responds quickly and reliably. Details in the article VPS for a Telegram bot.
- Remote desktops for an office. The same city where the staff work, or the nearest large hub: RDP VPS.
- Game server. As close as possible to most of the players; latency matters more than anything else here: VPS for game servers.
- A site for a specific region. For Europe, the Netherlands, Germany or Finland; for North America, the USA; for South-East Asia, Singapore.
- Backups. Not in the same data centre as the main server. A fire or an outage at one site should not take both the site and its copy. Selection: VPS for backups.
How to measure latency to candidate countries from your city
Pick two or three hosts in each country and find their test IP addresses or looking glass page, usually in the "Network" or "Data centres" section. Where to find them and how to read each tool is covered in detail in the article how to check VPS ping and speed before paying. Here is a short routine for comparing countries.
Step 1. Measure from your computer. On Linux and macOS, put in the candidates' addresses and run:
for h in 203.0.113.10 198.51.100.20 192.0.2.30; do
echo "== $h"; ping -c 20 -q $h | tail -2
done
The last line for each address shows the minimum, average and maximum. On Windows, run ping -n 20 address for each address and look at the "Average" line. Use a cable rather than Wi-Fi: a wireless network adds milliseconds of its own.
Step 2. The route to the two finalists.
mtr -rwc 50 203.0.113.10
If the delay jumps at some hop and stays high to the end, the hop names show where the traffic takes a detour. It happens that packets to a server in Finland go via Frankfurt, and then Finland is no longer closer.
Step 3. Measure from your users' cities. Your computer is one point. If your visitors are spread across a country or a continent, use the free Globalping service: it runs ping from hundreds of probes at different providers. On the service's website you can do it in the browser, and from the console like this:
globalping ping 203.0.113.10 from London,Chicago,Singapore
Step 4. Decide. Write down the average for each city and country pair. If the candidates differ by less than 20 ms, choose by price, payment and host. If the difference is 50 ms or more, take the country that serves the largest group of your users best. And look at the worst city, not only your own.
Country traps in a plan
The IP address "lives" in another country. IP geolocation services sometimes show the country where the host's network is registered rather than where the server stands. For visitors this means little, but services that choose a language or region by IP can get it wrong. Check the assigned address in two or three such services on the first day. If the country is wrong, write to the host: the databases are usually corrected at its request.
"Europe" without a city. If a plan just says "Europe" or "USA", ask for the exact city before paying. A server on the US West Coast is 70–80 ms further from a European audience than one on the East Coast.
Expecting the server country to lift the site in search. Search engines barely look at where the server is. Google works out a site's target region from its language, domain, hreflang tags and links. Choose the country for the speed it gives people, not for the crawlers.
You can filter plans by country and city in the VPS search. Regional selections: VPS in Europe, VPS in Asia.