Is Qlik Cloud down?

We're investigating an issue affecting user login in Qlik Cloud and are diligently working to resolve the issue as soon as possible. Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

The issue is related to a third-party service provider. We are working with the provider to resolve the problem as quickly as possible. We will keep you posted on any further updates.

The issue has been fixed by the vendor and the team is monitoring the results.

This issue has been resolved. We apologize for the inconvenience and appreciate your patience.

We experienced a service impact with Qlik Cloud – Europe (Ireland) which was resolved at 13:20 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

We're investigating a potential issue with Qlik Cloud Data Integration (QDI) – Europe (Ireland) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

We’ve identified that additional functionality is affected as part of this ongoing issue — specifically: Reload failures with Direct Access Gateway and Data Gateway movement. Any further updates will be posted to this site.

The issue has been fixed and the team is monitoring the results.

This issue has been resolved. We apologize for the inconvenience and appreciate your patience.

**Summary of Impact:**  On June 23, 2026, beginning at approximately 13:00 UTC, a subset of Qlik Cloud customers in the eu-west-1 region experienced data gateway issues, both on Qlik Cloud® Data Integration and Qlik Cloud Analytics®. This caused intermittent failures in reloads and data movement. Qlik applied an initial fix within approximately two hours, restoring service stability. The issue recurred on June 24th at around 12:50 UTC, and it was promptly resolved within 27 minutes.  **Root Cause:**  The routine upgrade of a Kubernetes component led to inaccurate metrics concerning the number of connected gateways, causing the system to scale down to a minimum number of replicas. The recurrence resulted from an incorrect assessment of the metrics, resulting in an insufficient number of replicas that did not fully resolve the underlying issue, leading to the same behavior.  **Resolution and Remediation:**  Once the root cause was fully identified, Qlik mitigated the issue by temporarily increasing the minimum number of replicas for the gateway service to a level to ensure system stability. Qlik repeated this action the following day based on the correct metrics.  To prevent recurrence, Qlik is implementing the following long-term actions: increasing the number of replicas in the most active regions; implementing a more resilient scaling strategy that does not rely solely on the connected gateway metrics; and enhancing internal alerting.

We're investigating a potential issue with Qlik Cloud – Europe (Ireland) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

We have identified elevated error rates across multiple services in our Europe (Ireland) region. Users may intermittently experience failures when opening apps, errors loading the hub, and issues browsing data files. Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

The issue has been identified, and our team is actively working on mitigation and implementing a fix.

The issue has been fixed and the team is monitoring the results.

This issue has been resolved. We apologize for the inconvenience and appreciate your patience.

**Summary of Impact:**  On June 22, 2026, customers using the Qlik Cloud® – Europe \(Ireland\) region may have experienced intermittent performance degradation affecting Qlik Cloud Analytics applications. Users may have seen intermittent issues opening Qlik Sense applications, loading the hub, or browsing data files. The impact occurred during the following periods:  * 07:03–08:41 UTC  * 12:03–12:39 UTC  * 13:03–13:25 UTC  **Root Cause:**  A service update caused unexpected behavior in a backend component, which led to temporary resource contention and increased latency. This resulted in a low rate of intermittent errors affecting application access and related services.  **Resolution and Remediation:**  Qlik Engineering and Operations teams identified the contributing update and performed a rollback to a stable version of the service. This restored consistent system performance. To strengthen resilience and reduce the risk of recurrence, the following improvements are being implemented:  * Targeted backend component fixes to prevent resource contention under load  * Expanded pre-production performance and regression testing under load  * Improved monitoring and alerting for early detection of latency and error-rate anomalies  We apologize for any inconvenience caused by these intermittent performance impacts and appreciate your patience throughout the investigation and resolution process.

We're investigating a potential issue with Qlik Cloud – Europe (Frankfurt) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

The issue has been identified, and our team is actively working on mitigation and implementing a fix.

The issue has been fixed and the team is monitoring the results.

This issue has been resolved. We apologize for the inconvenience and appreciate your patience.

**Summary of Impact:**  On June 11, 2026, between approximately 09:56 UTC and 10:32 UTC, a limited subset of Qlik Cloud customers experienced intermittent disruptions affecting tenant access and navigation, application opening, reload execution, automation runs, Talend Cloud task execution, and report delivery. Some actions during the impact window may have been delayed or required retry.  **Root Cause:**  The issue was traced to a platform access-control configuration update which temporarily affected certain backend service operations. As a result, multiple dependent services were temporarily unable to complete normal processing, which led to customer-facing disruptions across tenant access, application opening, reloads, automations, and reporting workflows.  **Resolution and Remediation:**  The Qlik Engineering team promptly identified the root cause and rolled back the configuration update, after which services began recovering. Additional operational recovery actions were completed to stabilize impacted services and restore normal processing. To prevent recurrence, Qlik is strengthening its pre-production validation procedures for access-control configuration changes before production rollout and enhancing monitoring and recovery handling for service dependency failures and cascading impact scenarios.