Global Datacenter Network

Which server location should you choose?

Start with where your visitors, players or staff actually are, then pick the closest datacentre that sells the product you need. The second half of that sentence matters. Not every product is offered in every city, so the right answer is sometimes a small compromise. Here is how it usually works out, audience by audience.

• Customers mostly in India. Start with our India locations, but note that they are not all one city. SSD VPS in India is hosted in New Delhi, our dedicated servers in India are in a Mumbai datacentre, and the NVMe VPS India page is labelled India (Mumbai) in our menu. There are also Cloud VPS, Storage VPS and web hosting pages for India.
• Southeast Asia and the wider Asia-Pacific region. Singapore is the usual choice, and it is a sensible second location for an Indian business that has started selling across Asia. Options are SSD VPS, NVMe VPS, dedicated servers and cPanel web hosting.
• Japan. Tokyo has SSD VPS and Storage VPS. That is the full list for Japan today, so if you need NVMe or a dedicated machine, you will be choosing a different country.
• Australia and New Zealand. Sydney covers SSD VPS, NVMe VPS and dedicated servers.
• Europe. Germany, France, the UK and Poland all have NVMe VPS and Cloud VPS pages, for example Germany and the UK. France also has dedicated servers.
• North America. Canada has NVMe VPS and dedicated servers. For the USA we offer SSD VPS in USA East, USA Central and USA West.

If your audience is split, go where most of your revenue or your most impatient users are, and put a CDN in front for everyone else. If you can't decide between two places, order the smaller plan in each and measure (the testing section further down shows how). And if a law or a client contract dictates where data must live, that decision is already made for you. Read the data location section below before you shop on price.

How server location affects speed, SEO and compliance

Server location is one of the few hosting choices you can't casually undo later, so before you compare datacentre locations it is worth understanding what the choice changes and what it doesn't.

Distance, hops and the first byte

Every request travels from the visitor's device to your server and back. The further apart they are, and the more networks the traffic has to cross on the way, the longer each round trip takes. A page needs many round trips before it appears: a DNS lookup, a secure connection, the HTML itself, then stylesheets, scripts and images. A server in the same country or region as your visitors usually answers faster than one on another continent, and that gap shows up first in time to first byte, the wait before the browser receives anything at all.

What a CDN can and can't do

A CDN keeps copies of your static files, such as images, CSS and JavaScript, on servers near your visitors. It helps a lot. But the HTML of a WooCommerce cart, a logged-in dashboard or an API response is generated fresh, and that work still happens on your origin server. If the origin is on the other side of the planet, every dynamic request pays the distance, however good the CDN is. Put the origin near your audience first, then add a CDN for the static weight.

Does server location for SEO matter?

Indirectly, yes, and mostly through speed. Search engines such as Google look at how pages perform for real visitors, not only in a lab test, so a slow first byte for your actual audience can hold back your results and your conversions at the same time. Where the server sits is a weak country signal on its own. Stronger signals are a country-specific domain, the language and currency of your content, hreflang tags if you run several regional versions, and local links. Don't move servers hoping to rank in a country if none of those are in place.

Country targeting and compliance

Choosing a location is the easiest way to keep data inside a particular country, but it is not the same as being compliant. Rules usually follow the people whose data you hold, and the business that collects it, rather than the postcode of a rack. We cover this in general terms in the data location section further down.

What location does not fix

A nearby server will not rescue an unoptimised site. Uncompressed hero images, forty plugins, a database with no indexes and a theme that loads six font files will be slow in Mumbai and in Frankfurt alike. Check the basics first: caching, image sizes, slow queries. The WordPress speed guide is a good place to start. Location is the finishing touch, and also the first thing people blame.

Server locations in India and Asia-Pacific

India

We are an Indian company, and India is the best-covered country in our network: SSD VPS, NVMe VPS, Cloud VPS, Storage VPS, dedicated servers and web hosting all have India pages. Mumbai is one of India's main internet gateways, and that is where our dedicated servers sit. SSD VPS in India is in New Delhi instead. If you serve customers across the country, the difference between the two cities is small next to the difference between India and anywhere overseas, so choose by product first. Support is 24x7 in English, Hindi and Marathi, and IST stays at UTC+5:30 all year with no daylight saving, which keeps scheduling simple.

Singapore

Singapore is a major connectivity hub for Southeast Asia, which makes it the natural second location for many Indian businesses. It has more of our product range than any other overseas location: SSD, NVMe, Cloud and Storage VPS, dedicated servers and shared web hosting. Singapore time is UTC+8, two and a half hours ahead of India. Sale seasons like 11.11 and 12.12 bring big traffic spikes across the region, which is a good reason to have the origin close to the shoppers.

Japan

Tokyo is Japan's capital and largest city, and it is where our Japan servers are. You can get SSD VPS or Storage VPS there, nothing else for now. Japan time is UTC+9. If your audience is Japanese, a local server is worth having, particularly for anything interactive such as game or app backends. Golden Week brings a predictable burst of traffic, so size accordingly.

Australia

Sydney is Australia's biggest city and the distance to the rest of the world is long, so serving Australian visitors from a European or Asian server is noticeable. We offer SSD VPS, NVMe VPS, Cloud VPS, Storage VPS and dedicated servers. Sydney runs on UTC+10, or UTC+11 during daylight saving, roughly October to April, so schedule maintenance windows with that shifting offset in mind. Trading peaks such as Boxing Day and the end of the financial year on 30 June are worth planning for.

Server locations in Europe and North America

Europe

We offer servers in Germany, France, the UK, Poland and Italy. Germany and the UK have the widest VPS choice, with SSD VPS (Germany, UK), NVMe VPS, Cloud VPS and Storage VPS pages. In France there are NVMe VPS, Cloud VPS, dedicated servers and web hosting. Poland has NVMe VPS and Cloud VPS. Italy is part of our network and shown on the map above, but none of our product pages lists Italy today, so ask us through the contact page before you plan around it. A European location suits European audiences, and also works as a mid-point if your visitors are split between Europe and India.

North America

Canada has NVMe VPS, Cloud VPS, dedicated servers and web hosting. The USA is covered by SSD VPS and Storage VPS in three places: USA East (New York), USA Central (Kansas City) and USA West (Los Angeles). A server in the middle of the country gives a reasonable compromise for coast-to-coast traffic, while East or West suits an audience concentrated on one side. Check the plan page for the location you pick to see exactly what is offered there.

Whatever you pick, the plan page remains the source of truth for what is in stock. We update stock and pricing there, and the table in the next section is only a map to find the right page quickly.

What is offered where

This table lists the published pages for each of our data centre locations. The VPS locations make up most of it, while dedicated server locations are fewer: India, Singapore, Australia, Canada and France. A dash means we have no page for that product there. The plan page shows live stock, so a link here is not a promise that every plan is available today.

Not sure which product family you need? The VPS overview and the dedicated servers overview compare them side by side, and web hosting has its own overview. Italy shows dashes only because we have no product page for it yet, not because it is missing from the network.

Choosing a location by workload

Different projects hurt in different places. Here is how we would think about the usual ones.

Online store

Shoppers abandon slow checkouts, and checkout pages can't be cached. Put the origin where most of your buyers are. For an Indian store that means an India location, and it matters most in sale weeks. Diwali traffic arrives all at once, so give yourself headroom and test before the festival, not during it.

SaaS and APIs

Think about who calls the API. If the callers are browsers, locate near your users. If they are other servers, such as a payment gateway or a partner system, locate near them, and keep the database in the same place as the application. A fast app server talking to a faraway database is slower than both being in one spot.

Game servers

Players feel distance as ping, so the location should be where most of your players live: Singapore for Southeast Asia, Sydney for Australia, Tokyo for Japan. The Singapore and Australia dedicated pages list gaming-oriented plans, including Standard Gaming 1, if you want a whole machine.

Media, downloads and large files

Put a CDN in front of anything large and public, and keep the master copies on a server with plenty of disk. Storage VPS pages exist in India, Singapore, Germany, the UK, Japan, Australia and the three USA locations.

Agencies and resellers

Locate each client's site near that client's audience rather than putting everything in one place. Staging sites can live anywhere cheap and convenient, since nobody visits them.

Backups and disaster recovery

A snapshot on the same server is not a backup. Follow the 3-2-1 idea: three copies, two kinds of storage, one off-site. Make the off-site copy a different location from the primary. A store in India with copies in Singapore survives a bad day in one city.

Two locations at once

Running in two places is useful when your audience truly spans regions, but it brings real work: keeping the database in sync, deciding which copy wins in a conflict and handling failover. Many teams do better with one well-run primary and a CDN, and add a second region only when the evidence says so.

How to test a location before you commit

Guessing is cheap, measuring is better. Run these from the places your visitors really are. A laptop on home broadband, a colleague's phone in another city, or a small server in the target region will all do.

# Connect time, time to first byte and total time for one page
curl -o /dev/null -s -w 'connect %{time_connect}  first byte %{time_starttransfer}  total %{time_total}\n' https://example.com/

# Route and packet loss from your network to a server
mtr -rwc 50 203.0.113.10

Run the curl line a few times and take the typical result, not the best one. For your own site, the number to watch is the first byte, since that is where distance and slow code both show up. With mtr, look for loss that continues to the final line (loss on one middle hop that vanishes later is usually just a router deprioritising replies) and for a route that detours through a far-off country. On Windows, tracert does a rougher version of the same thing.

For a proper comparison, order the smallest plan in each shortlisted location, put a copy of your site on it, and measure with the same tools. Remember that SSD VPS is delivered within 2-3 days, so order ahead if you are working to a launch date.

Data location, privacy and compliance basics

This section is general information, not legal advice. Check your own situation with your own adviser. One principle applies everywhere: hosting in a country does not by itself make you compliant with that country's rules, and being compliant does not always require a server in that country.

India

The Digital Personal Data Protection Act, 2023 (DPDP Act) covers digital personal data of people in India. Some regulated sectors, payments being a common example, have their own rules about where data must be stored. If you handle card or payment data, the responsibility for checking those rules is yours, so read them before you choose a location.

Singapore

The Personal Data Protection Act 2012 (PDPA) sets rules for how organisations collect, use, protect and transfer personal data. A Singapore server helps if you want data close to Singapore customers, but the PDPA is about how you handle the data.

Japan

The Act on the Protection of Personal Information (APPI) governs how personal information is handled, including rules for providing data to parties outside Japan. If you run a Japanese service, ask your adviser how that applies to backups and support access.

Australia

The Privacy Act 1988 and the Australian Privacy Principles include rules on disclosing personal information overseas, and the Notifiable Data Breaches scheme covers what happens after a breach. Where your servers sit and where your backups sit can both be relevant.

Europe

The GDPR applies based on whose data you handle, not only where the server is. A UK or German server doesn't make you GDPR-ready, and an Indian server doesn't exempt you if you serve people in Europe.

For other countries, we haven't listed rules on this page. Ask your adviser rather than assuming. If a contract, auditor or client asks for specific paperwork about the datacentre, raise it with us before you buy, not after you have migrated.

Moving a project to another location

You pick the datacentre when you order, so changing location in practice means ordering a server in the new place and moving across. It is routine work, and a quiet afternoon is enough for a small site. The steps below are general advice rather than a description of one specific setup.

1. Lower your DNS TTL. A day or two before the move, drop the TTL on the records you will change to something short, such as 300 seconds. Visitors then pick up the new address quickly at cut-over.
2. Build the new server. Install the same stack and versions: PHP, Node, database, web server. Match the old server's configuration files first, then improve things later.
3. Copy the files. rsync -avz over SSH transfers only what changed, so you can run it several times. Database dumps with mysqldump or pg_dump work for most sites, restored on the new server.
4. Test before DNS changes. Point your own computer to the new IP with a hosts file entry and click through the site, checkout, login and forms.
5. Freeze writes and sync again. For a store, pause orders for a short time, repeat the rsync, and take a final database dump so nothing is lost.
6. Switch DNS. Update the record to the new IP. Watch both servers' logs for a few hours.
7. Keep the old server a few days. Once traffic has settled, raise the TTL back and take a last backup before cancelling.

If you are on a Singapore shared plan, our web hosting includes free website migration, so you may not need to do any of this by hand. For a VPS or dedicated move, take a snapshot or backup of the old machine first. And if the move is a big or business-critical one, talk to our team through the contact page before you start; that is cheaper than a failed cut-over.