What should I watch for when bringing a small office online in Thailand?

November 5, 2026 4 answers
Asked by bramblefax

We are opening a small facility in Thailand and have a few systems that currently seem to need Layer 2 connectivity back to the US. I am looking at private connectivity over internet access, but would appreciate advice on the network and software issues to plan for.

Answers

QZ-17

First, pin down what โ€œneeds Layer 2โ€ actually means. Is it a hard requirement from a device, or just how the current application was built? Stretching a broadcast domain across that distance can add latency and make outages harder to diagnose. Ask the equipment and application owners about supported routed designs, local services, or a cloud deployment before committing to it.

If Layer 2 really is unavoidable, document the required protocols and performance, then test them over the proposed path. Keep the bridged segment as small and isolated as you can, with a clear failure plan.

bramblefax:

It is legacy PLC equipment tied to the ERP setup. I am looking into whether we can change the process and avoid the Layer 2 dependency.

Reply to this answer
teacup@dusk

Work from measured requirements rather than choosing a circuit type first. Check expected bandwidth, latency sensitivity, packet loss, and what happens during an internet or tunnel failure. A path between Thailand and the US will have noticeable latency, so test the actual application workflows, not just basic reachability.

Also decide where traffic exits, how failover works, and who monitors the connection in each time zone. If the site has only one internet provider or one path into the building, that is a bigger availability risk than the choice between two tunnel products.

Reply to this answer
GLITCHY

Plan for the room and local support, not just the diagram. Heat, humidity, power quality, cooling alarms, physical access, and replacement gear all matter for a small site. Confirm that the equipment you plan to deploy can be sourced and supported locally, and keep suitable spares or a realistic replacement process.

Review incident procedures for regional disruptions too. Make sure someone can reach the site, knows how to contact local providers, and can handle a network outage when the US team is offline.

Reply to this answer
tumble.taxi

Your checklist is a good start. Add a pass through every vendor contract and license for use in another country, and check whether any data handling or retention rules affect the systems involved. Those details depend on the product and the data, so get qualified local guidance rather than assuming the US setup carries over unchanged.

For the technical rollout, test Thai language and regional settings, time zone behavior, authentication from the new location, endpoint updates, and logging. Make sure alerts and support documentation still make sense across local hours and language needs.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions