Blog / Network reach
How fast is natbox from your country? We measured from 27 cities
17 November 2026 · Update · By Mohammad AlSaraf
All natbox servers are with one provider in the EU. That's great if you and your visitors are in Europe, and something to plan for if they aren't. So before you pick a server for a website, a game server or a VPN, here is how long it actually takes to reach ours from 27 cities on six continents, measured the same way, several times, from the same machines.
How we measured
- We used Globalping, a public network of volunteer-run probes, and always picked the same 27 probes, one per city.
- Each probe opened a TCP connection to port 80 of a server's shared IPv4 address. That takes one round trip, so it's a fair stand-in for "ping" through the same path your visitors use. Some probes also pinged the server's own IPv6 address.
- We measured our three servers one at a time, a minute apart, in a new random order each round: six rounds between 10 November 10:05 and 11 November 15:14 UTC.
- For each city we show two numbers. Best is the fastest result we saw, the route with no waiting. Typical is the median, what you should expect most of the time.
Results

- Europe: 10 to 50 ms from every city we tried, up to about 60 ms from Moscow. Good for anything, including games and voice.
- Middle East and North Africa: 40 to 90 ms from Istanbul, Cairo, Riyadh and Kuwait. Fine for websites, bots and VPNs, playable for most games. Dubai was the exception at about 190 to 260 ms, much slower than its neighbours; we only had one probe there, so that may be its own connection.
- North America: about 90 to 110 ms from the east and the middle, about 150 to 175 ms from Los Angeles. Fine for websites, APIs and bots. You'll notice it in fast games.
- Asia, Australia and South America: 130 to 315 ms (Mexico about 140 to 150 ms). Websites still load fine, especially with a CDN in front, but this is not where to host a game server for players there.
Over IPv6 the numbers were close to IPv4 for the same city, so visitors who reach your server directly over IPv6 aren't any slower than those going through the shared IPv4 address.
The part we haven't explained yet
Our three servers have the same routes: from every city their best times are within a few milliseconds of each other. Their typical times aren't. In five of the six rounds, our first server was about 10 to 20 ms slower at the median than the other two, and results to every server jumped around more from round to round than we'd like, even from nearby cities.
A second test we run between our own servers every minute shows the same thing: the fastest ping between them is a few milliseconds, as you'd expect for servers this close to each other, but the average is much higher and a small share of pings are lost. So the extra time isn't distance. It's packets waiting, either in the virtual machines our servers run on or in our provider's local network. We're collecting more data and will talk to our provider with it. We'll update this post when we know more.
What this doesn't tell you
- The probes sit in data centres. Your home connection, Wi-Fi or mobile network adds its own time on top.
- One probe per city. A single machine can be better or worse connected than its country's average.
- Six rounds over about a day. A longer run would smooth out the differences between our servers.
- We left out one probe that said it was in Pretoria, because it answered faster than light could travel from South Africa to our servers. It was clearly somewhere else.
What this means for your server
If your visitors or players are in Europe, the Middle East or the eastern US, a natbox server in the EU is a good fit. If they're mostly in Asia, Australia or South America, use natbox for things where a few hundred milliseconds don't matter, such as websites behind a CDN, bots, backups and development, and pick a provider closer to them for real-time traffic.
The full method and every number are in our upcoming measurement report. If you'd like us to measure from a city that isn't on the list, tell us at support@natbox.io.
Get new tutorials in Telegram. Follow @natboxio: every new post, plus short server tips.
More from the blog: We tested our backups by restoring them. Here's how long it took, How much do natbox servers really use?, Keeping natbox clean: our first abuse and fraud report. RSS feed.