View this page in the latest version of Appian. Latency-Based Routing in Appian Cloud Share Share via LinkedIn Reddit Email Copy Link Print On This Page This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud. Overview Latency-based routing dynamically routes user requests to the geographic region nearest to them, improving the responsiveness of Appian Cloud environments. This helps speed up common requests and makes the overall user experience better for the majority of end users, even if their Appian environment or portal is hosted in a different region than where they are located. This page discusses how latency-based routing works in Appian Cloud. Tip: Process Mining does not use latency-based routing. Latency-based routing in Appian Cloud Latency-based routing routes end user requests involving dynamic web content to the geographic region available in Appian Cloud with the lowest latency. Dynamic web content is web content that changes to personalize the experience based on the user who is interacting with a system, as opposed to static content, which displays the same content for all users. Requests that require accessing data stored in a customer's environment are routed to the specific region the Appian Cloud environment is hosted in. All traffic continues to use end-to-end encryption using industry-standard Transport Layer Security (TLS) encryption. Latency-based routing is enabled by default in all supported regions where the service is offered. Note: When looking up the IP address of your Appian Cloud site, geolocation tools may report a location in the United States. This is expected and does not mean your traffic is being routed through the US. The IP addresses used for latency-based routing are registered in the United States, but your traffic still enters the network at the closest available location and is routed to the region with the lowest latency. Feedback Was this page helpful? SHARE FEEDBACK Loading...