To ensure Qlik Cloud works correctly, you may need to allowlist certain domains and IP addresses in your firewall or proxy. This allows Qlik Cloud services, automations, connectors, and sessions to communicate reliably with your systems.
Traffic from Qlik Cloud to your systems may include:
Connecting to your databases or other data sources
Accessing SMTP servers
Sending webhooks
Traffic from your systems to Qlik Cloud may include:
Making API calls
Using multi-cloud features
Starting Qlik Cloud sessions
You may also need to allowlist external domains to access resources such as fonts, help pages, or integrations.
Qlik Cloud Government noteFor Qlik Cloud Government IP addresses, contact Qlik Support.
Allowlisting traffic from Qlik Cloud
The following tables list the regional static IP addresses that Qlik Cloud services use to communicate with customer systems. IPs are specific to each tenant region.
Add the IPs for your region to your firewall or proxy allowlist to ensure reliable connectivity. You can identify your region from your tenant URL: <tenantname>.<region>.qlikcloud.com
Information noteDetailed information about these IP addresses is not available.
Generally required static IP addresses
These static IP addresses are used by Qlik Cloud services to communicate with customer systems. Add the IPs for your region to your firewall or proxy allowlist. You may also need to add these IPs to your tenant-level allowlist to allow inbound connections to your Qlik Cloud tenant.
IP addresses per region for Qlik Cloud traffic
Region
Analytics and Data Integration
Americas (us)
18.205.71.36 18.232.32.199 34.237.68.254
Ireland (eu)
34.247.21.179 52.31.212.214 54.154.95.18
Frankfurt (de)
3.76.162.169 3.77.162.68 3.122.137.91
London (uk)
13.42.141.246 18.135.245.97 35.179.0.171
Sweden (se)
13.51.129.105 16.170.33.251 16.170.27.83
Singapore (sg)
18.138.163.172 18.142.157.182 54.179.13.251
Australia (ap)
13.210.43.241 13.236.104.42 13.236.206.172
Japan (jp)
54.238.168.131 3.113.68.20 35.73.207.58
India (in)
52.66.18.8 13.201.250.59 15.207.252.34
Middle East (ae)
40.172.103.16 40.172.135.154 40.172.134.184
Israel (il)
51.17.198.2 51.17.227.118 51.84.30.13
Brazil (br)
56.125.3.105 18.231.207.106 54.94.46.71
France (fr)
15.236.44.136 15.188.250.12 35.181.228.177
Static IP addresses required for Qlik Automate
These static IP addresses are used by Qlik Automate to communicate with your systems. Add the IPs for your region to your firewall or proxy allowlist. You may also need to add these IPs to your tenant-level allowlist to allow inbound connections to your Qlik Cloud tenant.
IP addresses per region for Qlik Automate
Region
Qlik Automate
Americas (us)
18.235.133.252 3.217.244.242 18.214.8.201
Ireland (eu)
54.216.156.88 3.248.156.131 52.213.44.55
Frankfurt (de)
3.69.132.138 3.69.222.86 3.72.136.160
London (uk)
18.168.120.199 18.169.91.38 13.42.135.168
Sweden (se)
13.53.211.145 13.50.63.235 13.60.101.12
Singapore (sg)
54.169.84.213 13.213.173.37 13.213.113.162
Australia (ap)
54.206.158.27 3.104.137.20 3.24.52.178
Japan (jp)
35.77.238.13 13.115.58.233 35.74.220.230
India (in)
3.109.34.226 15.206.64.196 3.6.11.209
Middle East (ae)
40.172.75.127 40.172.171.244 40.172.92.216
Israel (il)
51.84.43.188 51.17.145.45 51.84.44.145
Brazil (br)
54.207.174.200 54.207.184.180 54.94.103.110
France (fr)
35.181.235.154 13.38.237.231 13.37.77.179
Static IP addresses required for SaaS connectors in Data Integration
These IP addresses are used by Qlik Cloud SaaS connectors to communicate with your tenant. Add the IPs for your region to your firewall or proxy allowlist. Tenant-level allowlisting is not required for SaaS connectors.
IP addresses per region for SaaS connectors in Data Integration
Region
SaaS connectors in Data Integration
Americas (us)
23.21.238.161 34.232.203.146 44.212.174.31
Ireland (eu)
52.211.180.19 52.48.201.148 54.247.165.17
Frankfurt (de)
3.74.21.144 35.157.50.219 3.75.166.31/32
London (uk)
13.42.85.5 18.168.59.160 13.42.139.68
Sweden (se)
51.21.123.49 13.50.254.253 51.21.139.3
Singapore (sg)
46.137.230.180 13.228.215.246 13.250.148.59
Australia (ap)
52.63.245.121 13.210.87.204 13.237.124.90
Japan (jp)
35.76.22.32 43.206.71.15 54.92.37.71
India (in)
13.202.192.86 43.205.184.187 13.233.6.79
Middle East (ae)
40.172.104.210 40.172.44.255 40.172.29.37
Israel (il)
51.17.142.170 51.17.144.48 51.17.177.88
Brazil (br)
18.231.16.63 54.232.67.215 18.231.66.252
France (fr)
51.44.129.69 15.237.170.173 13.37.75.163
Allowlisting traffic from your systems to Qlik Cloud
The table below lists the regional static IP addresses required for API calls, multi-cloud features, and Qlik Cloud sessions. IPs are specific to each tenant region.
Add the IPs for your region to your firewall or proxy allowlist to ensure reliable connectivity. You can identify your region from your tenant URL: <tenantname>.<region>.qlikcloud.com
Traffic may pass through a load balancer and use dynamic source IPs. To prevent blocked connections, allow Qlik Cloud static IPs for your region as destination addresses.
Static IP addresses required for traffic to Qlik Cloud
IP addresses per region for traffic to Qlik Cloud
Region
IP address
Americas (us)
3.233.118.242 34.234.80.90 44.215.23.130
Ireland (eu)
99.81.122.190 108.128.157.152 108.129.46.246
Frankfurt (de)
3.67.51.47 18.193.162.245 52.58.113.105
London (uk)
13.41.125.158 18.168.223.169 18.169.70.63
Sweden (se)
16.171.102.151 51.20.24.0 51.20.149.100
Singapore (sg)
3.1.207.89 18.138.83.27 52.74.26.118
Australia (ap)
13.54.144.196 13.55.228.248 52.64.134.232
Japan (jp)
13.115.5.27 18.179.235.68 52.69.157.151
India (in)
3.108.106.180 3.6.57.94 65.1.6.215
Middle East (ae)
40.172.175.160 40.172.175.4 40.172.51.16
Israel (il)
51.16.223.21 51.84.154.171 51.84.163.93
Brazil (br)
52.67.104.212 54.232.175.93 56.125.17.93
France (fr)
15.188.225.140 35.180.171.215 35.181.3.153
Tenant-level allowlisting
Tenant-level allowlisting is configured within your Qlik Cloud tenant. It controls which external services or IP addresses can directly access your tenant. This is different from allowlisting in your network firewall or proxy, which controls traffic between your systems and Qlik Cloud.
If you use Qlik Automate, toolkits, gateways, or other external services, review the next section.
No allowlisting required, unless webhooks are used from the Qlik Cloud Services connector. In that case, allowlist the source region's generally required static IPs.
Qlik Automate – out-tenant connectors
(for example, Qlik Platform Operations, Call URL, API key, OAuth)
Not applicable. These cannot connect to a Qlik Cloud tenant.
Information noteIn case of a disaster recovery (DR) event, Qlik Cloud IP addresses will change. Update the tenant-level allowlist for any tenants using Qlik connector packages in the affected region. New IP addresses will be published by Qlik.
Domain allowlisting
Some Qlik Cloud resources are hosted on external domains and CDNs. Allowlisting these domains ensures full functionality, including fonts, help pages, and integrations.
Allowlist domains for Qlik Cloud services
Category
Domain
Purpose
Authentication
cdn.auth0.com
Required for users authenticating via Qlik Account.
Authentication
cdn.myqlik.qlik.com
Required for users authenticating via Qlik Account.
Authentication
login.qlik.com
Required for users authenticating via Qlik Account.
Authentication
myqlik.qlik.com
Required for users authenticating via Qlik Account.
Authentication
qlikidp-prod.guardian.auth0.com
Required for users authenticating via Qlik Account and using MFA.
Authentication
unpkg.com
Required for users authenticating via Qlik Account.
Account management
www.zuora.com
Required for digital purchase subscriptions.
Features & telemetry
app.launchdarkly.com
Required for feature enablement and telemetry on the tenant.
Features & telemetry
api.qlikdataengineering.com
Provides Qlik with telemetry used for feature development, anomaly detection, and issue detection.
Features & telemetry
api.rollbar.com
Provides Qlik with telemetry used for feature development, anomaly detection, and issue detection.
Features & telemetry
events.launchdarkly.com
Required for feature enablement and telemetry on the tenant.
Features & telemetry
*.fullstory.com
Provides Qlik with telemetry used for feature development, anomaly detection, and issue detection.
Features & telemetry
sqs.us-east-1.amazonaws.com
Provides Qlik with telemetry used by data engineering to capture UI events.
Features & telemetry
www.google-analytics.com
Provides Qlik with telemetry used for feature development, anomaly detection, and issue detection.
General
*.qlikcloud.com
Required for core user experience and API calls from all user interfaces.
Resource center & notifications
cdn.pendo.io
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
Resource center & notifications
help.qlik.com
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
Resource center & notifications
i.ytimg.com
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
Resource center & notifications
www.qlik.com
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
Resource center & notifications
www.youtube-nocookie.com
Required for serving notification content such as What's new, Learn, Help, support chats, and some other feature and deprecation related UI notifications.
User interface
cdnjs.cloudflare.com
Serves resources and frameworks for the user interface.
User interface
fonts.googleapis.com
Serves fonts for the user interface.
User interface
fonts.gstatic.com
Serves fonts for the user interface.
User interface
gravatar.com
Serves the profile icon for the logged in user.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!
