Choosing between VPS locations is the one server decision you cannot undo with a resize. CPU and RAM can grow later; the city decides how far every request travels, which laws apply to your data, and how much traffic a monthly plan includes. This guide covers all 14 countries where Cloudj runs cloud servers, what differs between them, and a decision table by audience.
Start with your users, not the server
The most useful question is: where are the people or systems that will talk to this server? Network distance adds round-trip time to every request, and extra vCPU does not fix that. A site for one country belongs in or near that country. An API called by other servers belongs near those servers. A trading bot belongs near the exchange it calls, not near you. A personal VPN or dev box belongs near where you sit, unless you need an IP in a specific country. For a global audience, start where most users are and add a CDN or second region later.
For the measurement side, see choosing a VPS location by latency and testing a VPS with ping and mtr.
All Cloudj VPS locations at a glance
Cloudj runs cloud servers in 14 countries. The table lists each one with its cities and the traffic included on monthly plans.
| Region | Country | City | Traffic on monthly plans |
|---|---|---|---|
| Asia | Singapore | Singapore | 1 TB |
| Asia | Japan | Tokyo | 1 TB |
| Asia | Hong Kong | Hong Kong | 1 TB |
| Oceania | Australia | Sydney | 1 TB |
| Europe | Germany | Frankfurt | 5 TB |
| Europe | Netherlands | Amsterdam | 5 TB |
| Europe | United Kingdom | London | 5 TB |
| Europe | Spain | Madrid | 5 TB |
| Europe | Italy | Milan | 5 TB |
| Europe | Sweden | Stockholm | 5 TB |
| Europe | Romania | Bucharest | 5 TB |
| North America | United States | New York, Los Angeles, Santa Clara, Seattle, Chicago, Dallas, Atlanta, Miami | 5 TB |
| North America | Canada | Toronto | 5 TB |
| Middle East | Israel | Jerusalem, Tel Aviv, Petah Tikva, Rosh Haayin, Haifa | 5 TB |
Cloudj has no cloud servers in Vietnam; for Vietnamese users the nearest locations are Singapore, Hong Kong and Tokyo (see below). The full list also lives on the cloud servers overview. Each region has its own hub article with more detail: VPS in Asia, VPS in Europe and VPS in North America, Australia and Israel.
How traffic allowances differ by region
Traffic is the one spec that changes noticeably with location. Monthly plans in Singapore, Tokyo, Hong Kong and Sydney include 1 TB per month. Every location in Europe, the United States, Canada and Israel includes 5 TB.
What this means in practice:
- For a typical website, API or bot, 1 TB is plenty, because text, JSON and compressed pages are small.
- For media-heavy work such as video, large downloads or off-site backups, the 5 TB regions give more headroom.
- On hourly billing, traffic is charged per GB used instead of coming from an allowance.
Our article on hourly vs monthly VPS billing explains when each model makes sense.
What stays the same in every location
The catalogue is consistent across locations, so you can pick a city for network reasons alone:
- Sizes from 1 vCPU, 1 GB RAM and 20 GB disk up to custom builds of 104 vCPU and 512 GB RAM, with 30 ready-made plans per location or your own mix of vCPU, RAM and disk.
- Three CPU types: shared ("Availability"), general purpose, and dedicated cores for steady, CPU-heavy work. See shared vs dedicated CPU for how to choose.
- Linux images (Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS) and Windows. The OS list can differ by location, so check the list for your location in the console.
- SSH keys or a generated root password, a browser SSH console, CPU/RAM/network metrics, reboot, resize of CPU and RAM, disk growth and saved custom images.
- Billing by the hour from your account balance, or a prepaid term of 1, 3, 6 or 12 months with optional auto-renew.
Decision table: which location fits which audience
| Your main audience or target | Start with | Read next |
|---|---|---|
| Users in Vietnam (no Cloudj servers there) | Singapore, then test Hong Kong and Tokyo | Vietnam vs Singapore VPS |
| Southeast Asia as a whole | Singapore | Best VPS in Singapore |
| Japan, or East Asia edge | Tokyo | Best VPS in Japan |
| Hong Kong and Greater China audiences | Hong Kong | Best VPS in Hong Kong |
| Australia and New Zealand | Sydney | Best VPS in Australia |
| Central Europe, DACH | Frankfurt | Best VPS in Germany |
| Western Europe, Benelux | Amsterdam | Best VPS in the Netherlands |
| UK users, London finance | London | Best VPS in the UK |
| Spain and Portugal | Madrid | Best VPS in Spain |
| Italy and the Mediterranean | Milan | Best VPS in Italy |
| Nordics | Stockholm | Best VPS in Sweden |
| Eastern Europe and the Balkans | Bucharest | Best VPS in Romania |
| US East Coast | New York, Atlanta, Miami | US East vs West VPS |
| US West Coast | Los Angeles, Santa Clara, Seattle | Best VPS in the US |
| Canada | Toronto | Best VPS in Canada |
| Israel and the eastern Mediterranean | Tel Aviv, Jerusalem, Petah Tikva, Rosh Haayin or Haifa | Best VPS in Israel |
For close calls between neighbouring hubs, two comparison posts go deeper: Singapore vs Hong Kong vs Tokyo and Frankfurt vs Amsterdam vs London.
Use-case shortcuts
Some workloads have a natural home:
- Forex and trading. Put the server near the broker's servers. London and New York are the usual choices; see forex VPS in London and forex VPS in New York. A nearby server reduces network delay; it does not make trades profitable.
- Crypto bots. If your exchange runs its matching servers in Asia, a Singapore server is a natural fit; crypto trading bots in Singapore covers that setup.
- Game servers. Place them in the middle of your player base. Minecraft in Germany and game servers in Singapore are two worked examples.
- Self-hosting in Europe. WireGuard in the Netherlands and Nextcloud in Sweden are two examples.
If you only need an IP address in a country, not compute, read VPS vs proxy and the dedicated proxy guide first.
A short checklist before you deploy
- Shortlist two locations from the decision table.
- Deploy a small hourly server in each and measure from real client networks.
- Check that your OS image is listed for that location in the console.
- Compare the traffic allowance with your expected monthly transfer.
- Delete the test server you do not keep. Hourly servers are charged while they exist, even when stopped, because the disk and IP stay reserved.
FAQ
Does Cloudj have a VPS in Vietnam?
No. Cloudj has no cloud servers in Vietnam. For users there, test Singapore first, then Hong Kong and Tokyo, and measure from the Vietnamese ISPs your users use, because any server abroad adds network distance compared with an in-country host. The Asia VPS guide compares the three.
Can I move a server to another location later?
Not by resizing. Location is fixed when the server is created. To move, deploy a new server in the target city and migrate your data; our guide to migrating a website to a new VPS walks through it.
Why do Asian locations include less traffic than European ones?
Monthly plans in Singapore, Tokyo, Hong Kong and Sydney include 1 TB, and Europe, the Americas and Israel include 5 TB. For most web and API workloads 1 TB is enough; heavy media workloads may prefer a 5 TB region.
Are prices the same in every location?
Prices vary by location and size. See live prices on the pricing page; the console also shows the exact price before you deploy.
Pick a city and test it
The right location is the one closest to the people and systems your server talks to. Shortlist two cities, deploy a small hourly server in each from the Cloudj console, measure, and keep the one that performs best for your users.