How to choose a server location

Pick a data center location based on where your users, broker or team are, confirm it with ping tests, and weigh the legal and latency points that come with each choice.

  • Beginner
  • All
  • 4 min read

By RunRacks Team · Published

Where your server lives affects how fast it feels to everyone who uses it. A server close to your users answers quickly; one on the other side of the world adds a delay to every click, page load and trade. This guide shows you how to pick a location, how to test it with ping, and which legal and practical points to weigh.

Before you start

Answer one question: who or what talks to this server the most?

  • Website or app: your visitors or customers.
  • Trading: your broker's trading server.
  • Remote desktop: you and your team.
  • Game server: your players.
  • Bots and APIs: the services the bot talks to, such as Discord or a data provider.

The location you need is the one closest to that answer. The locations RunRacks offers are listed when you choose a plan on Pricing.

Why distance matters

Data travels through fibre at a large fraction of the speed of light, but over thousands of kilometres that still adds up. Every request also passes through routers along the way. The delay for a round trip is called latency, measured in milliseconds (ms) with the ping command. Our guide to latency explains it in more detail.

Rules of thumb:

  • Same city or region: usually a very low ping.
  • Same continent: moderate.
  • Across an ocean: noticeably higher, and every round trip pays it.

A web page may need many round trips to load, so latency multiplies.

Choose by use case

Websites and online shops

Pick the location nearest your main audience. If visitors are spread worldwide, choose the region with the most customers and add a CDN to serve static files from locations near everyone else.

Trading

Pick the location nearest your broker's trading server, not your home. Brokers usually say where their servers are in their documentation or support pages. Your order travels from the VPS to the broker, so that is the trip to shorten.

Remote desktop

Pick the location nearest you. Remote Desktop sends every keystroke and screen update over the network, so high latency makes typing and scrolling feel sluggish. For a team, pick the region where most people work.

Game servers

Pick the location nearest most of your players. If they are split across regions, a location between them can be fairer than one that suits only one group.

Bots and APIs

Latency matters less unless the bot reacts in real time. Nearer to the APIs it calls is a sensible default.

  • Data protection: if you store personal data of customers in a particular region, laws such as the GDPR may set rules on where and how it is processed. Check what applies to you, and get advice if unsure.
  • Content and service rules: what is allowed can differ by country. Read the RunRacks terms of service as well.
  • Your clients' requirements: some contracts state where data must be stored.

Check it works

Before you order, test latency from where your users are. If a test IP address or a looking-glass page is available for a location, ping it from your own computer:

Terminal
ping -c 10 203.0.113.10

On Windows:

PowerShell
ping -n 10 203.0.113.10

Look at the average time in the summary. Lower is better, and steady numbers matter as much as low ones. For trading, compare with your broker's server address if they publish one. After ordering, run the same test against your real server IP.

Troubleshooting

  • Ping is higher than expected for the distance: routing between your ISP and the data center may take a long path. Test with tracert on Windows or mtr on Linux to see where the delay is added.
  • Ping times jump around: that is jitter, often caused by Wi-Fi or a busy home connection. Test on a wired connection.
  • Ping does not reply at all: some servers block ping. Test a known open port instead.
  • You chose the wrong location: ask support through a ticket about your options. Moving usually means a new server and migrating your data.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Getting started

Edit files with nano: a beginner's guide

Open, edit, search and save files with the nano text editor on a Linux server, including cutting and pasting lines, showing line numbers and safely editing system config files with sudo.

  • Beginner
  • Linux VPS
  • 5 min read

Getting started

Your first hour with a new RunRacks server

A step-by-step roadmap for the first hour after your RunRacks server is delivered, from finding your login details to changing the password, updating the OS and picking your next guides.

  • Beginner
  • All
  • 5 min read

Getting started

Use the built-in OpenSSH client in Windows Terminal

Connect to your Linux VPS from Windows 10 or 11 with the built-in ssh command, create and store keys in your .ssh folder, and add a Windows Terminal profile that opens your server in one click.

  • Beginner
  • Linux VPS
  • 5 min read