This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud.
As a part of Latency Based Routing, all customer data remains stored in the region their Appian Cloud instance is hosted in. Only Appian product static content is served from a geographic region with lower latency for the end user.
All traffic continues to use end-to-end encryption using industry-standard Transport Layer Security (TLS) encryption.
In a single region routing configuration, Appian Cloud instances must serve all requests from the region it is hosted in. This means that no matter where across the world an end user is connecting from, all requests are routed through the hosting region. Consequently, for end users close to the hosting region, all requests can be speedy and responsive. But for certain end users on the opposite side of the world, some requests will be slower than others due to having to travel such a great distance to the hosting region.
All Appian Cloud instances using the standard appiancloud.com domain already make use of Latency Based Routing.
Any Appian Cloud customers who wish to use a custom Appian Cloud instance domain name can open up a support case with Appian Support to enable the use of a custom instance domain name with your Appian Cloud instances. New configurations will have Latency Based Routing enabled by default. See: Using a Custom Domain in Appian Cloud
For any existing Appian Cloud customers making use of a custom Appian Cloud instance domain name, Appian Support will reach out to you via a support case to enable Latency Based Routing configurations so your Appian Cloud instances can take advantage of Latency Based Routing to provide the best experience for your user base across the world.
On This Page