Welcome to the gateway of enhanced performance. This guide helps you elevate your Exium SASE experience by strategically choosing the Preferred Server β the SASE cloud node, or Cybernode β closest to your users and connecting locations within the CyberMesh.
TL;DR β Closer Cybernode = lower latency + higher throughput. When in doubt, run a quick speed test to the nearest few nodes and let the numbers decide.
Step into the future with Exium's Intelligent Cybersecurity Mesh β a cloud-scale security platform that seamlessly connects and safeguards your apps, data, devices, and users on a global scale, all built on a foundation of Zero Trust.

When creating a workspace for your client organization, the key decision is selecting the Preferred Server in Exium's portal. Optimal performance comes from choosing the server closest to your users and connecting locations β this guarantees lower latency and higher throughput.[1]
If the choice isn't obvious, run throughput and latency tests directly to our CyberMesh from the devices and locations you intend to secure.
Before testing, turn off any VPN or proxy β they can skew the results and lead to the wrong server selection.
Latency and throughput vary with the time of day and network conditions. Treat these tests as a guiding light, weighed alongside the geographic proximity of the Preferred Server, to make a well-informed choice.
| Cybernode | Latency & Throughput Test |
|---|---|
| Ashburn, Virginia | http://172.111.38.5:3000/ |
| Atlanta | http://23.92.73.35:3000/ |
| Chicago | http://64.29.176.240:3000/ |
| Dallas | http://64.29.177.240:3000/ |
| Denver | http://69.50.95.208:3000/ |
| Detroit, Michigan ==NEW== π | Endpoint to be provided |
| Las Vegas | http://76.164.192.194:3000/ |
| Los Angeles | http://64.29.179.240:3000/ |
| New York | http://64.29.178.240:3000/ http://23.227.200.229:3000/ |
| Phoenix | http://23.158.200.249:3000/ |
| Portland, Oregon | http://208.115.255.70:3000/ |
| Salt Lake City, Utah | http://173.231.10.174:3000/ |
| San Francisco | http://23.157.40.110:3000/ |
| Seattle | http://91.191.218.46:3000/ |
| Tampa, Florida | http://209.133.195.194:3000/ |
| Cybernode | Latency & Throughput Test |
|---|---|
| Montreal | http://23.162.56.32:3000/ |
| Toronto | http://67.220.94.217:3000/ |
| Vancouver | http://158.51.123.45:3000/ |
| Cybernode | Latency & Throughput Test |
|---|---|
| Frankfurt | http://66.206.24.110:3000/ |
| London | http://64.29.181.240:3000/ |
| Paris | http://45.128.134.214:3000/ |
| Dublin, Ireland ==NEW== π | Endpoint to be provided |
| Dubai | http://139.185.34.199:3000/ |
| Johannesburg, South Africa | http://129.151.186.125:3000/ |
| Cybernode | Latency & Throughput Test |
|---|---|
| Tokyo, Japan ==NEW== π | Endpoint to be provided |
| Taipei, Taiwan ==NEW== π | Endpoint to be provided |
| Hyderabad, India | http://144.24.144.34:3000/ |
| Mumbai, India | http://64.29.182.240:3000/ |
| Singapore | http://107.155.95.30:3000/ |
| Sydney | http://217.79.246.67:3000/ |
Pick your region, locate the Cybernode nearest you, and open its endpoint to launch the test. Endpoints now use direct IP addresses for the speed-test servers.
In every region listed above, Exium operates multiple Cybernodes to accommodate capacity demand, enable seamless failover, and deliver high availability β so your users stay protected and performant even if a single node is taken out of rotation.
You can benchmark Secure Private Access (SPA) latency and performance with a simple test against the speed-test server running on the internal network inside the Cyber gateways.
For the SPA test to work, you must be connected to Exium β either with the Exium client running on your device, or from a location secured by Exium's Cyber gateway.
Steps:

Want to learn more about implementing SASE for your organization and explore tailored solutions for your unique requirements?
Contact Exium at hello@exium.net for a consultation or demonstration.
Results reflect the path from your test device to the speed-test server running inside the chosen Cyber gateway. Re-run the test a few times to smooth out transient network noise. β©οΈ