Slow connection to Qlik Cloud: test your network latency towards AWS

[Daniele_Purrone]

Long access times to Qlik Cloud or when performing reloads using the Direct Access Gateway may be caused by high network latency between your location and the AWS datacenter hosting the affected tenant. 

A possible browser test to check the network connection from a computer to AWS can be found at AWS Latency Test.

This test does not concern Qlik Cloud's platform, and can therefore be used to determine if there are purely network-related issues.

1. Find the correct AWS region for your tenant. You can do so by cross-referencing regions and IP addresses as documented in Allowlisting domains and IP addresses.
   
   For instance, the region for .de tenants is in Frankfurt:
   
   
   
   
2. On the AWS Latency Test, select your region and a couple of other ones to compare results
   
   
   
   
3. Wait for the test results to be returned:
   
   
   
   
4. In case of immediate apparent problems, involve your network team to discuss possible remediations

This is just a first-step tool, not a conclusive one. A latency of 300ms or more might still not affect user experience in Qlik Cloud, but it's still worth using the tool quickly for a first assessment.

Related Content

How to verify and measure transfer speed from Direct Access gateway to Qlik Cloud

Environment

• Qlik Cloud Analytics