Choosing an offshore region: latency against distance

There is a trade-off at the centre of this decision that almost no host states plainly: the further you get from the jurisdiction that might come after you, the further you usually get from your users. Both distances are measured in the same geography, and they pull against each other.

Start with who has to be fast

• Interactive web application with European users: Bucharest or Sofia. Roughly twenty to forty milliseconds across most of Europe, with no notice-and-takedown timetable.
• Interactive application with American users: Panama, or Amsterdam if you can accept an EU jurisdiction. Iceland is a reasonable middle for the eastern seaboard.
• Asia-Pacific users: Kuala Lumpur for the safe-harbour tier, Singapore or Tokyo when latency dominates and the jurisdiction genuinely does not matter.
• Bulk distribution, mirrors, seedboxes and archives: latency is nearly irrelevant, throughput is everything. Take the strongest jurisdiction available — Moldova or the Seychelles.
• Anything where a takedown is the primary risk: Chișinău, and put a proxy in front if the latency bothers you.

The pattern that resolves it

Most of the time you do not have to choose, because the two jobs can live in different places. Put the origin — the database, the files, the thing that is hard to move — in the strongest jurisdiction you can tolerate. Put a cache or reverse proxy close to your users. The proxy is stateless and disposable, so if it attracts a complaint you replace it in minutes without touching anything that matters.

Things that are not the deciding factor

Price differences between our regions are small enough to ignore for this decision. Hardware is identical across the tier. Support is the same people regardless of where the machine sits. Do not let a two-dollar monthly difference push you into a jurisdiction you would not otherwise have chosen — you will spend far more than that migrating later.

Moving later

Snapshot the instance and redeploy it in another region from the client area. There is no migration fee and no re-verification, because there was never any verification to redo. Keep the DNS TTL low as a matter of habit and the switch is a couple of minutes.

Published by NoDMCAVPS, an offshore host that files automated DMCA notices instead of forwarding them. What we still remove is listed in the acceptable use policy.