Hello Peplink InConrtol2 Team,
Regional IC2 Instances are something that was raised (again) at the 2025 Peplink Tech Summit; it is more around:
- The perceived speed/response time of InControl2
- Regional data sovereignty, and also that by having a globally distributed load of InControl2
Opening this up to the community for contribution.
Marcus 
3 Likes
+1 for the geographic hosting option.
I’ve not personally found that as someone accessing Ic2 mostly from Europe or North America that there is much of a performance difference, but I can certainly see for people in APAC it might be less than ideal.
Data sovereignty is a tricky one when the hosting platform is ultimately owned and controlled by an organisation headquartered in the USA (a lot of Ic2 is hosted in AWS I believe).
2 Likes
Hi, @WillJones
Peplink have a SFC at Sao Paulo (Brazil) and works very well.
Maybe at AWS, maybe not… I don’t know.
But your suggestion to have a IC2 servers, here at Brazil, will be great for us!
AWS, have a lot of firewall… but look below.
ping incontrol2.peplink.com
PING ic2-800928670.us-west-2.elb.amazonaws.com (52.42.150.224) 56(84) bytes of data.
^C
— ic2-800928670.us-west-2.elb.amazonaws.com ping statistics —
6 packets transmitted, 0 received, 100% packet loss, time 5108ms
So… any connection from Brazil to EUA have a latency around of 120ms.
1 Like
Also the maintenance time. Incontrol2 maintenance always ends up being 11am on Monday morning in Australia, which is… not my preferred time.
1 Like
Great point @bryn.loftus,
That’s where a distributed global load could reduce the impact and timing of updates; the current time for updates impacts the entire APEC region during regular business hours.
Have a great week,
Marcus 