Cross-border networking and collaboration
Headquarters, overseas offices and cloud resources join one SD-WAN network; cross-border traffic rides our own backbone and critical applications go first.
The challenge
- 01Overseas offices find headquarters ERP, files and internal systems slow and unreliable.
- 02Intercontinental video calls stutter and drop.
- 03Every new site means rebuilding the network and security policy from scratch.
Reference architecture
How it rolls out
- 01
Map sites and apps
List offices, factories and data centres and the apps that matter between them: video, ERP, files.
- 02
Connect with SD-WAN
Put an SD-WAN device at each site, or connect through a cloud access point — usually within days.
- 03
Route by application
Video and ERP take optimised paths while ordinary browsing breaks out locally.
- 04
Keep watching
Watch latency and loss per link in the console; if something goes wrong, we tell you first.
How a customer uses it
A parts maker headquartered in Dongguan with plants in Japan and Vietnam
- Before
- ERP from the Vietnam plant to head office kept freezing, half of every call with the Japan team went on reconnecting, and big files travelled by courier on hard drives.
- After
- Three sites on SD-WAN, with Japan landing through SoftBank. ERP is instant again, calls are steady, and design files sync online.
−80%
Packet loss
3 days
To bring three sites online
1 invoice
Links and cloud billed together
Design notes
Start with one link
Connect the most painful cross-border link first, see the difference, then bring other sites in step by step.
Rank your applications
Put meetings and ERP first and schedule backups and large syncs off-peak; the same bandwidth goes further.
Plan network and cloud together
Deploy applications in the region nearest your offices and connect them directly for the lowest latency and cost.