Qlik Outage History

Started Sep 02, 2026, 07:27 AM UTC· resolved Sep 02, 2026, 08:08 AM UTC

1. investigating Sep 02, 2026, 07:27 AM UTC

   We're investigating an issue affecting content visibility in the Hub in Qlik Cloud – Europe (Ireland) 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.

2. identified Sep 02, 2026, 07:47 AM UTC

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

3. monitoring Sep 02, 2026, 07:48 AM UTC

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

4. resolved Sep 02, 2026, 08:08 AM UTC

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

Read the full incident report →

Started Jun 26, 2026, 07:14 AM UTC· resolved Jun 26, 2026, 08:01 AM UTC

1. investigating Jun 26, 2026, 07:14 AM UTC

   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.

2. identified Jun 26, 2026, 07:23 AM UTC

   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.

3. monitoring Jun 26, 2026, 07:29 AM UTC

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

4. resolved Jun 26, 2026, 08:01 AM UTC

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

Read the full incident report →

Started Jun 23, 2026, 02:54 PM UTC· resolved Jun 23, 2026, 03:34 PM UTC

1. investigating Jun 23, 2026, 02:54 PM UTC

   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.

2. investigating Jun 23, 2026, 03:00 PM UTC

   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.

3. monitoring Jun 23, 2026, 03:04 PM UTC

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

4. resolved Jun 23, 2026, 03:34 PM UTC

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

5. postmortem Jul 08, 2026, 04:13 PM UTC

   **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.

Read the full incident report →

Started Jun 11, 2026, 10:34 AM UTC· resolved Jun 11, 2026, 11:37 AM UTC

1. investigating Jun 11, 2026, 10:34 AM UTC

   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.

2. identified Jun 11, 2026, 10:51 AM UTC

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

3. monitoring Jun 11, 2026, 10:55 AM UTC

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

4. resolved Jun 11, 2026, 11:37 AM UTC

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

5. postmortem Jun 30, 2026, 01:08 PM UTC

   **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.

Read the full incident report →

Started May 28, 2026, 06:53 PM UTC· resolved May 28, 2026, 07:42 PM UTC

1. investigating May 28, 2026, 06:53 PM UTC

   We're investigating an issue affecting reloads 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.

2. investigating May 28, 2026, 06:55 PM UTC

   We are continuing to investigate this issue.

3. identified May 28, 2026, 07:22 PM UTC

   We have identified the issue affecting reloads in Qlik Cloud and are diligently working to resolve the issue. We apologize for any inconvenience and appreciate your patience.

4. resolved May 28, 2026, 07:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 11, 2026, 10:55 AM UTC· resolved Apr 11, 2026, 11:49 AM UTC

1. investigating Apr 11, 2026, 10:55 AM UTC

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

2. identified Apr 11, 2026, 11:30 AM UTC

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

3. monitoring Apr 11, 2026, 11:34 AM UTC

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

4. resolved Apr 11, 2026, 11:49 AM UTC

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

5. postmortem Apr 28, 2026, 02:29 PM UTC

   **Summary of Impact:** From April 8 to April 11, 2026, customers utilizing the Qlik Cloud US-East-1 \(North Virginia\) region may have experienced intermittent service disruptions. Primary observations included delays in application reloads, login failures, and “Internal Server Error” messages. While these issues were observed in the user interface, backend processes remained functional and executed as expected. **Root Cause:** The investigation attributed the incident to two primary factors: i\) database resource contention that delayed processing of reloads and authentication requests; and ii\) a configuration mismatch impacting tenant accessibility. **Remediation:** Qlik Engineering responded by immediately increasing database capacity and deploying an emergency configuration patch. To ensure long-term stability, we improved database infrastructure segregation to prevent future database resource contention and applied performance optimization enhancements to reduce system latency. We apologize for any inconvenience this disruption may have caused and are committed to delivering the reliable experience our customers expect from Qlik Cloud.

Read the full incident report →

Started Apr 10, 2026, 01:19 PM UTC· resolved Apr 11, 2026, 12:30 AM UTC

1. investigating Apr 10, 2026, 01:19 PM UTC

   We're investigating an issue affecting multiple areas of the platform, including: login failures, opening apps and reloads delays with Qlik Cloud – US East (N. Virginia). Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

2. investigating Apr 10, 2026, 02:20 PM UTC

   We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue as soon as possible. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

3. investigating Apr 10, 2026, 04:25 PM UTC

   We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

4. investigating Apr 10, 2026, 05:55 PM UTC

   We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

5. investigating Apr 10, 2026, 07:56 PM UTC

   We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

6. identified Apr 10, 2026, 10:02 PM UTC

   The issue has been identified and a fix is being implemented.

7. resolved Apr 11, 2026, 12:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 09:39 AM UTC· resolved Apr 08, 2026, 10:59 AM UTC

1. investigating Apr 08, 2026, 09:39 AM UTC

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

2. identified Apr 08, 2026, 09:48 AM UTC

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

3. monitoring Apr 08, 2026, 10:18 AM UTC

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

4. resolved Apr 08, 2026, 10:59 AM UTC

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

5. postmortem Apr 17, 2026, 03:46 PM UTC

   **Summary of Impact:** On April 8, 2026, starting at approximately at 11:20 AM CEST and lasting 26 minutes, the Qlik Cloud® AWS – Europe \(Ireland\) region experienced a partial service disruption. During this window, affected users may have encountered difficulties accessing Qlik Cloud. **Root Cause:** The cause was due to a network component that temporarily became unable to process traffic due to insufficient allocation of resources. **Resolution and Remediation:** Qlik Engineering and Operations teams promptly identified the issue and implemented a solution, successfully restoring services. Following this action, all affected services returned to normal operation. We apologize for any inconvenience this disruption may have caused to your operations

Read the full incident report →

Started Mar 25, 2026, 04:33 AM UTC· resolved Mar 25, 2026, 03:33 PM UTC

1. resolved Mar 25, 2026, 11:25 AM UTC

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

Read the full incident report →

Started Mar 24, 2026, 01:12 PM UTC· resolved Mar 24, 2026, 03:09 PM UTC

1. resolved Mar 24, 2026, 05:35 PM UTC

   We have experienced TMC Talend Cloud flow execution failures in the AWS - Asia Pacific (Sydney) region from 13:12 UTC until 15:09 UTC. If your tasks are still failing, please restart your Remote Engine and re-run your flow. We apologise for any inconvenience this may have caused.

Read the full incident report →

Started Mar 24, 2026, 05:51 AM UTC· resolved Mar 24, 2026, 07:57 AM UTC

1. investigating Mar 24, 2026, 05:51 AM UTC

   We’re investigating an issue impacting the ability to open analytics apps in Qlik Cloud – Ireland 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.

2. investigating Mar 24, 2026, 06:52 AM UTC

   We are continuing to investigate an issue affecting OpenApp in Qlik Cloud. Our engineering teams are actively exploring potential fixes and working to restore normal functionality. We will share updates as more information becomes available.

3. identified Mar 24, 2026, 07:22 AM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Mar 24, 2026, 07:25 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Mar 24, 2026, 07:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 01, 2026, 01:24 PM UTC· resolved Mar 10, 2026, 03:26 PM UTC

1. investigating Mar 01, 2026, 01:24 PM UTC

   We’re investigating a potential issue with Qlik Cloud – “UAE“. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

2. identified Mar 01, 2026, 01:39 PM UTC

   We’ve confirmed that the AWS ongoing issue in me-central-1 (Dubai) region is affecting our customers using Qlik services in Qlik Cloud. Our team continues to diligently work with AWS to mitigate the issue. We will keep you posted on any further updates.

3. identified Mar 01, 2026, 03:16 PM UTC

   The issue remains related to the third-party service provider. We are continuing to work closely with them and are actively monitoring their progress. For the most up-to-date information, customers may also refer to the provider’s status page. We will share further updates here as they become available.

4. identified Mar 01, 2026, 05:04 PM UTC

   The third-party service provider continues to work towards recovery. We are continuing to work closely with them and are actively monitoring their progress. We will share further updates here as they become available.

5. identified Mar 01, 2026, 06:59 PM UTC

   We are continuing to monitor our third-party vendor's progress toward recovery. We will provide updates as soon as additional information becomes available.

6. identified Mar 01, 2026, 11:43 PM UTC

   Our third-party vendor continues working to resolve the root cause and service availability continues to improve. We are monitoring progress closely and collaborating to apply updates. We will provide further updates between 4-8 hours from now or when additional relevant information becomes available or if there is a substantial reverse of the situation.

7. identified Mar 02, 2026, 04:30 AM UTC

   Our third-party vendor continues to work toward resolving the root cause, and service availability is improving. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 4 hours, or sooner when there is any new additional information available.

8. identified Mar 02, 2026, 08:29 AM UTC

   Our third-party vendor continues to work toward resolving the root cause. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 4 hours, or sooner when there is any new additional information available.

9. identified Mar 02, 2026, 12:30 PM UTC

   According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. The latest information from AWS is available at https://health.aws.amazon.com/health/status. AWS continues to work toward resolving the issues. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 4 hours, or sooner when there is any new additional information available.

10. identified Mar 02, 2026, 04:36 PM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. The latest information from AWS is available at https://health.aws.amazon.com/health/status. AWS has indicated that recovery may take at least a day. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 12 hours, or sooner when there is any new additional information available.

11. identified Mar 03, 2026, 02:00 AM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. The latest information from AWS is available at https://health.aws.amazon.com/health/status. AWS indicates that recovery will be prolonged because of physical damage sustained by the multiple availability zones. AWS continues to work parallel paths to restore physical facilities and also to create software-based mitigations with the goal to restore as much customer access as possible as quickly as possible. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 12 hours, or sooner when there is any new additional information available.

12. identified Mar 03, 2026, 01:57 PM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. The latest information from AWS is available at https://health.aws.amazon.com/health/status. AWS continues to work toward resolving the issues. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 12 hours, or sooner when there is any new additional information available.

13. identified Mar 04, 2026, 01:42 AM UTC

    We are continuing to work on a fix for this issue.

14. identified Mar 04, 2026, 01:45 AM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. AWS continues to work toward resolving the issues. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 24 hours, or sooner when there is any new additional information available.

15. identified Mar 05, 2026, 01:48 AM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. AWS continues to work toward resolving the issues. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided within 24 hours, or sooner when there is any new additional information available.

16. identified Mar 06, 2026, 01:40 AM UTC

    According to AWS, multiple Availability Zones in me-central-1 (UAE) are experiencing outages. AWS continues to work toward resolving the issues. We are actively monitoring progress and collaborating on recovery efforts. The next update will be provided when there is any new additional information available.

17. resolved Mar 10, 2026, 03:26 PM UTC

    As this incident is expected to continue for an extended period of time, we are moving to a more targeted communication model. Going forward, updates will be provided directly to affected customers via Email and Support Cases. Customers who require assistance related to this incident are encouraged to open a Support case or contact your Qlik representative for escalation. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started Jan 28, 2026, 05:01 PM UTC· resolved Jan 28, 2026, 08:01 PM UTC

1. investigating Jan 28, 2026, 05:01 PM UTC

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

2. investigating Jan 28, 2026, 05:33 PM UTC

   We’ve confirmed that the AWS ongoing issue is affecting our customers using Qlik services in Qlik Cloud. Our team continues to diligently work with AWS to mitigate the issue. We will keep you posted on any further updates.

3. identified Jan 28, 2026, 06:20 PM UTC

   AWS has identified the issue and is now showing signs of progressive recovery. Any further updates will be posted to this site. Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further developments.

4. identified Jan 28, 2026, 07:13 PM UTC

   AWS continues to work towards full recovery, estimating in the next 60 - 120 minutes. Any further updates will be posted to this site. Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further developments.

5. monitoring Jan 28, 2026, 07:27 PM UTC

   The issue has been fixed by AWS and we are monitoring the results.

6. resolved Jan 28, 2026, 08:01 PM UTC

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

7. postmortem Jan 29, 2026, 05:42 PM UTC

   **Summary of Impact:** On January 28th, 2026, starting at approximately 16:08 UTC and lasting until around 18:41 UTC, Qlik Cloud® – AWS – Europe \(Dublin\) customers experienced issues in login failures and platform unavailability due to an AWS service disruption in its eu-west-1 region. AWS experienced a localized failure in the eu-west-1 region, attributed to network change propagation. This service disruption prevented Qlik Cloud from providing services which led to the observed connectivity timeouts. **Resolution and Remediation:** Qlik Engineering and Operations teams immediately identified the connectivity loss and engaged with AWS Support to track the mitigation of the underlying failure. Once AWS stabilized the region's network change propagation, Qlik services automatically recovered. We apologize for any inconvenience this disruption may have caused to your operations.

Read the full incident report →

Started Oct 20, 2025, 07:53 AM UTC· resolved Oct 21, 2025, 08:55 AM UTC

1. investigating Oct 20, 2025, 07:53 AM UTC

   We’re investigating an issue affecting multiple areas of the platform, including: Login, API and open App with Qlik Cloud – US East (N. Virginia). Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

2. investigating Oct 20, 2025, 08:25 AM UTC

   An AWS issue in the US-EAST-1 region is currently impacting our Cloud infrastructures. We've identified that additional functionality is now affected as part of this ongoing issue — specifically: Talend Cloud TMC executions. Check live status updates here: https://status.qlikcloud.com/

3. monitoring Oct 20, 2025, 09:41 AM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Oct 20, 2025, 11:24 AM UTC

   AWS is still experiencing issues related to insufficient compute capacity errors, which may impact the ability to open your Qlik Cloud app. We suggest retrying to open the app, as systems are still recovering.

5. monitoring Oct 20, 2025, 02:33 PM UTC

   AWS is still experiencing issues, which may affect your ability to open Qlik Cloud apps. We recommend retrying to open the app, and we will keep you updated with any further information.

6. monitoring Oct 20, 2025, 06:15 PM UTC

   AWS is currently deploying a patch and resolving the queued up global requests. Qlik will continue to monitor to declare our systems recovered when we see this occur

7. monitoring Oct 20, 2025, 07:51 PM UTC

   We’ve confirmed that the AWS ongoing issue is affecting our customers using Qlik services in Qlik Cloud or Talend Cloud. Our team continues to diligently work with AWS to mitigate the issue. We will keep you posted on any further updates.

8. monitoring Oct 21, 2025, 02:05 AM UTC

   We continue to actively monitor the situation related to the earlier AWS outage. Several third-party service providers we depend on are still in the process of resolving residual issues stemming from that event. Our team remains engaged in monitoring and mitigation efforts to minimize any potential impact. We will provide additional updates as more information becomes available.

9. resolved Oct 21, 2025, 08:55 AM UTC

   This incident has been resolved.

10. postmortem Oct 30, 2025, 04:12 PM UTC

    **Root Cause Analysis:** On October 20th, 2025, starting at approximately 06:48 UTC customers began experiencing issues across Qlik Cloud and Talend Cloud due to an AWS outage in its us-east-1 region. Customers in Qlik Cloud – AWS – US East \(N. Virginia\), may have experienced login failures, difficulty opening apps, or issues with reload, reporting, prediction and automation functionalities. At approximately 09:41 UTC, when AWS applied its first mitigation, the major issues were resolved for most customers. However, due to continued AWS EC2 capacity shortages, we were unable to obtain sufficient resources to meet demand, which resulted in ongoing intermittent difficulty opening apps, or issues with reloads, reporting, prediction, and automation functionalities. Customers in Talend Cloud – AWS – US East \(N. Virginia\), might have experienced login issues, or issues with APIs or Talend Management Console \(TMC\) functionalities between 06:48 UTC and 09:41 UTC. The incident was caused by a region-wide outage in the AWS us-east-1 region. This was not a malicious event, and no customer data was compromised. **Resolution and Remediations:** Once AWS resolved its underlying infrastructure issues, Qlik platforms services recovered. To further enhance platform reliability and resiliency, Qlik is evaluating additional safeguards for partner related outages. We appreciate your patience and trust as we continue improving the resilience and reliability of our platform.

Read the full incident report →

Started Sep 09, 2025, 11:59 AM UTC· resolved Sep 09, 2025, 02:25 PM UTC

1. investigating Sep 09, 2025, 11:59 AM UTC

   We're investigating an issue impacting the ability to use reporting functionalities in Qlik Cloud – “AWS – Europe (Ireland) & (Frankfurt)” Region 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.

2. identified Sep 09, 2025, 12:32 PM UTC

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

3. monitoring Sep 09, 2025, 12:49 PM UTC

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

4. identified Sep 09, 2025, 01:14 PM UTC

   Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further updates.

5. monitoring Sep 09, 2025, 01:51 PM UTC

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

6. resolved Sep 09, 2025, 02:25 PM UTC

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

Read the full incident report →

Started Jul 21, 2025, 02:45 PM UTC· resolved Jul 21, 2025, 03:29 PM UTC

1. monitoring Jul 21, 2025, 02:45 PM UTC

   A fix has been implemented and we are monitoring the results.

2. monitoring Jul 21, 2025, 03:01 PM UTC

   The issue impacting user logins with Qlik Cloud has been resolved. Users should now be able to log in as expected. We appreciate your patience and apologize for any inconvenience caused during the disruption. Our team will continue diligently monitor it.

3. resolved Jul 21, 2025, 03:29 PM UTC

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

4. postmortem Jul 25, 2025, 01:54 PM UTC

   **User login impact - Qlik Cloud®** **Root Cause Analysis:** On July 21st, 2025, starting at approximately 14:11 UTC and lasting up to 17 minutes depending on region, customers may have experienced Qlik Cloud login failures. The incident was caused by a conflict between two backend service changes that required a specific initialization sequence to function correctly. Deploying them at the same time led to an unexpected condition that temporarily prevented the licensing system from processing login requests. This was an isolated scenario. This was not a malicious event, and no customer data was compromised. **Resolution and Remediations:** The resolution involved disabling the two backend changes temporarily, which immediately restored the licensing system. To further enhance platform resiliency, Qlik is expanding validation coverage and optimizing the handling of backend change dependencies. We appreciate your patience and trust as we continue improving the resilience and reliability of our platform.

Read the full incident report →

Started Jun 13, 2025, 02:59 PM UTC· resolved Jun 13, 2025, 03:08 PM UTC

1. investigating Jun 13, 2025, 02:59 PM UTC

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

2. investigating Jun 13, 2025, 02:59 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 13, 2025, 03:01 PM UTC

   The issue has been fixed and the team is monitoring the results. You may be forced to clean your browser cache.

4. resolved Jun 13, 2025, 03:08 PM UTC

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

Read the full incident report →

Started May 22, 2025, 07:34 PM UTC· resolved May 22, 2025, 08:05 PM UTC

1. resolved May 22, 2025, 08:54 PM UTC

   We experienced a service impact with Qlik Cloud Government for 31 minutes and resolved it at 20:05 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started May 20, 2025, 09:18 PM UTC· resolved May 20, 2025, 10:39 PM UTC

1. investigating May 20, 2025, 09:18 PM UTC

   We're investigating an issue affecting multiple areas of the platform, including: Login and API requests with Talend Cloud - AWS - US East (N. Virginia). We'll provide new information as it becomes available while the issue is being addressed. We apologize for any inconvenience and appreciate your patience.

2. investigating May 20, 2025, 10:04 PM UTC

   Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further updates.

3. identified May 20, 2025, 10:18 PM UTC

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

4. monitoring May 20, 2025, 10:23 PM UTC

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

5. resolved May 20, 2025, 10:39 PM UTC

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

Read the full incident report →

Started May 05, 2025, 04:13 PM UTC· resolved May 05, 2025, 06:44 PM UTC

1. investigating May 05, 2025, 04:13 PM UTC

   We're investigating user login impact with Qlik Cloud and are diligently working to resolve the issue as soon as possible. We'll provide new information as it becomes available while the issue is being addressed. We apologize for any inconvenience and appreciate your patience.

2. investigating May 05, 2025, 05:14 PM UTC

   We are continuing to investigate an issue affecting user logins to Qlik Cloud. Our engineering teams are actively exploring potential fixes and working to restore normal functionality. We will share updates as more information becomes available. We appreciate your patience and apologize for the inconvenience.

3. monitoring May 05, 2025, 05:39 PM UTC

   We have applied a fix, and the user login are being restored as we currently observe signs of improvement. We'll continue monitoring the results to ensure that Qlik Cloud is fully operational and functioning correctly.

4. resolved May 05, 2025, 06:44 PM UTC

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

5. postmortem May 12, 2025, 04:08 PM UTC

   **Root Cause Analysis:** On May 5, 2025, starting at approximately 15:33 UTC, customers, primarily in Qlik Cloud - US, may have experienced login failures, difficulty opening apps, browsing in the Hub, or issues with reload and automation functionality. This incident was triggered by a license validation check, which caused an unexpected increase in traffic. Upon reverting the change in the Qlik Cloud - US region, Qlik encountered a traffic-related untested race condition that significantly extended the duration of the impact and inhibited restoration of service. Other regions were briefly affected, but did not encounter this condition, resulting in rapid service restoration outside the U.S. This was not a malicious event, and no customer data was compromised. **Resolution and Remediations:** The resolution involved restoring the previous version of the service, recycling impacted nodes, and scaling up capacity to stabilize operations. To further enhance platform resiliency, Qlik is expanding validation coverage and optimizing the handling of cross-cluster license checks. Deployment testing is also being refined to increase visibility into potential edge-case behaviors. We appreciate your patience and trust as we continue improving the resilience and reliability of our platform.

Read the full incident report →

Started Apr 23, 2025, 07:02 AM UTC· resolved Apr 23, 2025, 03:29 PM UTC

1. identified Apr 23, 2025, 07:02 AM UTC

   For Qlik Cloud tenants hosted in the US East (North Virginia) region, a planned Qlik Application Automation maintenance window is taking longer than expected. Most automations are back up and running but some customers may experience issues with continued delays in scheduled automations. We are working on recovering all schedules, but meanwhile you can manually run an automation in the UI.

2. identified Apr 23, 2025, 07:52 AM UTC

   We have applied a fix, and the automation services are being restored as we currently observe signs of improvement. We'll continue monitoring the results to ensure that Qlik Cloud is fully operational and functioning correctly.

3. monitoring Apr 23, 2025, 08:40 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 23, 2025, 03:29 PM UTC

   All automations have now recovered and should be back up and running. Please note that automations that have run during the April 22nd 16:49 UTC to 4:14 UTC window will have run as expected but the runs might no longer be shown in the run history.

Read the full incident report →

Started Mar 06, 2025, 10:30 PM UTC· resolved Mar 06, 2025, 11:06 PM UTC

1. resolved Mar 06, 2025, 11:59 PM UTC

   We've experienced an issue with QlikID which may have impacted logins to Qlik Cloud or Qlik Customer Portal which lasted for 36m. Customers with their own IDP were not affected logging into Qlik Cloud. The issue has been identified, the fix has been applied, and the services have been restored. QlikID is now fully operational and logins are functioning correctly in Qlik Cloud and across all services. We apologize for the inconvenience and appreciate your patience.

2. postmortem Mar 20, 2025, 10:02 PM UTC

   **Root Cause Analysis:** On March 6, 2025, starting around 22:33pm UTC and lasting for 36 minutes, customers may have experienced login issues due to the unavailability of the QlikID service, impacting logins for Qlik Cloud, Talend Cloud, Customer Portal, My Qlik, and other platforms requiring a QlikID. Existing user sessions and logins using other providers were not affected. Qlik promptly mitigated the incident, by rolling back a deployment error restoring full login capabilities. This was not a malicious attack and no customer data was compromised. **Root Cause Summary and Remediation:** This incident was triggered by an undetected error in part of the deployment of the QlikID service. As part of a planned deployment, a code change was introduced that led to a failure in properly rendering QlikID’s login page. Once deployed, Qlik was able to identify the issue and revert to a stable state, where QlikID’s login page was rendering properly again. We appreciate your patience and trust as we continuously enhance the performance and stability of our platform. To prevent similar occurrences, Qlik is enhancing validations before each deployment and further optimizing detection and mitigations processes.

Read the full incident report →

Started Feb 25, 2025, 09:45 AM UTC· resolved Feb 25, 2025, 11:29 AM UTC

1. investigating Feb 25, 2025, 09:45 AM UTC

   We’re currently experiencing a performance degradation issue at Qlik Cloud - Europe (Ireland) region. Customers may experience slowdown and intermittent failures when connecting to Qlik Cloud applications.

2. identified Feb 25, 2025, 10:05 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 25, 2025, 10:05 AM UTC

   Qlik Cloud Service have all recovered, we will continue to monitor to confirm it is restored fully and we will update the status accordingly.

4. resolved Feb 25, 2025, 11:29 AM UTC

   This issue has been resolved. Your patience and support has been greatly appreciated!

5. postmortem Mar 03, 2025, 06:13 PM UTC

   **Root Cause Analysis** On February 25, 2024, from 09:16 to 09:58 UTC, our platform experienced an incident due to a traffic surge, which led to critical services reaching their scaling limits. This resulted in performance degradation for users in Qlik Cloud - Europe \(Ireland\) attempting to browse the hub to open their apps. Qlik promptly initiated mitigation efforts to scale up impacted areas, restoring system stability. **Root Cause Summary and Remediation** The incident was triggered by a sudden increase in traffic that exceeded expected operational thresholds, requiring additional scaling. While automated scaling mechanisms were in place, certain bottlenecks prevented immediate expansion, necessitating manual intervention. Once scaling was applied, stability was restored, and further optimization was performed to enhance long-term resilience. We appreciate your patience and trust as we continuously enhance the performance and stability of our platform. To prevent similar occurrences, we have strengthened our monitoring and alerting capabilities for earlier detection, rescaled and optimized key bottleneck areas, and refined our scaling strategies to improve system resilience under high load conditions.

Read the full incident report →

Started Feb 14, 2025, 12:09 AM UTC· resolved Feb 14, 2025, 04:03 AM UTC

1. investigating Feb 14, 2025, 12:09 AM UTC

   AWS is reporting an outage affecting Qlik Sense Services running in Stockholm, which may impact some functionality, including anonymous access. Our team is actively working with our partner to resolve the issue as quickly as possible. We will keep you updated on any further developments.

2. monitoring Feb 14, 2025, 12:45 AM UTC

   Qlik Cloud Service have all recovered, we will continue to monitor to confirm it is restored fully and we will update the status accordingly.

3. resolved Feb 14, 2025, 05:48 AM UTC

   This incident has been resolved.

Read the full incident report →