Singapore vs. SF latency from S.Korea

I’m planning to deploy a service where most of the users will be accessing the site from South Korea.

I was about to select the Singapore region, but then I’ve heard rumors that selecting the SF region is the optimal choice regarding latency issues. (I could not find any test results or evidence to back up this claim)

I would like to get your best informed opinion on the subject.

The service will use the LEMP(Ubuntu, MariaDB) stack with Varnish and Memcached. NoSQL will be added to the stack later on.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

There can be times where some providers are routing to the SGP1 datacenter using a suboptimal path. Certain countries are worse than others and I do not recall any tickets from South Korea about latency.

We also have some new peering partners that will be added to SGP1 soon that should help most of the areas where there is repetitive latency.