Qlik Cloud Outage History

Started Oct 26, 2026, 06:36 PM UTC· resolved Oct 26, 2026, 07:59 PM UTC

1. investigating Oct 26, 2026, 06:36 PM UTC

   We’re investigating an issue impacting the ability to open analytics apps 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 Oct 26, 2026, 07:31 PM UTC

   We’ve confirmed that the issue is affecting opening analytics applications in Qlik Cloud. Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further updates.

3. resolved Oct 26, 2026, 07:59 PM UTC

   This issue has been resolved. We apologize for the inconvenience and appreciate your patience. If you see issues creating new tenants in Qlik Cloud please contact Customer Support and they will assist with mitigation to resolve the issue.

4. postmortem Oct 27, 2026, 05:24 PM UTC

   **Summary of Impact:** On October 26, 2026, between approximately 17:30 UTC and 19:45 UTC, customers in all regions experienced issues accessing Qlik Cloud applications. Affected users saw a “User allocation required” error when opening apps, and some scheduled reloads failed during this period. Customers creating new seat-based entitlement tenants may also have been affected. **Root Cause:** A recent update to licensing configuration data caused a required attribute to be missing from some customers’ entitlement records. As a result of the missing entitlement, the licenses service denied access to affected applications. **Resolution and Remediation:** The team temporarily relaxed the related validation check, rolled back the configuration change, restored the missing attribute, and refreshed the affected entitlements. Access was restored for affected customers, and reloads that failed during the incident will complete on their next scheduled run. To prevent recurrence, we are continuing to investigate why the update removed this attribute. We will strengthen safeguards and monitoring around licensing configuration changes before the validation check is re-enabled. We apologize for any inconvenience this disruption may have caused to your operations.

Read the full incident report →

Started Oct 08, 2026, 02:10 PM UTC· resolved Oct 08, 2026, 02:10 PM UTC

1. resolved Oct 08, 2026, 02:10 PM UTC

   We experienced a service impact with Talend Cloud – AWS - US East (N. Virginia) which was resolved at 14:07 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started Sep 10, 2026, 02:36 PM UTC· resolved Sep 10, 2026, 02:36 PM UTC

1. resolved Sep 10, 2026, 02:36 PM UTC

   We experienced a service impact with Qlik Cloud Government (Fedramp) - AWS – GovCloud (West) which was resolved at 14:36 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

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

1. investigating Sep 02, 2026, 07:28 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.

5. postmortem Sep 07, 2026, 01:38 PM UTC

   **Summary of Impact:** On September 2, 2026, from approximately 06:27AM to 07:53 AM UTC, a subset of Qlik Cloud users with tenants in the EU West \(Ireland\) region encountered service degradation. This event impacted the Hubs and Spaces; although it did not prevent user access or cause service failures, it resulted in response delays while navigating the platform and opening applications. **Root Cause:** The issue was caused by elevated read/write latency in a caching layer responsible for authentication and session data in the EU West region. As traffic patterns evolved, the caching layer’s resource limits did not scale accordingly. Under increased load, it became unable to process requests efficiently, causing degraded performance in certain Hubs and Spaces in the region. **Resolution and Remediation:** The Qlik Engineering team traced the elevated latency to the caching layer and increased cashing layer resources. This restored response times to normal levels for affected customers. To help prevent recurrence, the team is reviewing capacity planning for the caching layer to proactively address future scaling needs, enhancing automated alerting to detect resource-limit issues earlier, and strengthening monitoring across dependent services to reduce time-to-detection for similar issues. We apologize for any inconvenience the delays in service may have caused and are committed to delivering the reliable experience our customers expect from Qlik Cloud.

Read the full incident report →

Started Aug 10, 2026, 01:45 PM UTC· resolved Aug 10, 2026, 01:45 PM UTC

1. resolved Aug 10, 2026, 01:45 PM UTC

   We experienced a service impact with Qlik Talend Cloud - AZURE - West US (California) which was resolved at 13:36 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started Jun 26, 2026, 07:16 AM UTC· resolved Jun 26, 2026, 08:02 AM UTC

1. investigating Jun 26, 2026, 07:16 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:28 AM UTC

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

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

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

Read the full incident report →

Started Jun 24, 2026, 01:00 PM UTC· resolved Jun 24, 2026, 01:00 PM UTC

1. resolved Jun 24, 2026, 01:00 PM UTC

   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.

Read the full incident report →

Started Jun 23, 2026, 02:54 PM UTC· resolved Jun 23, 2026, 03:33 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:33 PM UTC

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

5. postmortem Jul 08, 2026, 04:15 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 22, 2026, 08:00 AM UTC· resolved Jun 22, 2026, 09:18 AM UTC

1. investigating Jun 22, 2026, 08:00 AM UTC

   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.

2. investigating Jun 22, 2026, 08:29 AM UTC

   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.

3. identified Jun 22, 2026, 08:44 AM UTC

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

4. monitoring Jun 22, 2026, 08:53 AM UTC

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

5. resolved Jun 22, 2026, 09:18 AM UTC

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

6. postmortem Jun 30, 2026, 01:16 PM UTC

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

Read the full incident report →

Started Jun 11, 2026, 10:33 AM UTC· resolved Jun 11, 2026, 11:38 AM UTC

1. investigating Jun 11, 2026, 10:33 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:52 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:38 AM UTC

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

5. postmortem Jun 30, 2026, 01:13 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 Jun 03, 2026, 09:30 AM UTC· resolved Jun 03, 2026, 09:30 AM UTC

1. resolved Jun 03, 2026, 09:30 AM UTC

   We experienced a service impact with Qlik Cloud – Europe (London), Asia Pacific (Singapore), Asia Pacific (Sydney) which was resolved at 09:30 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

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

1. investigating May 28, 2026, 06:54 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. identified May 28, 2026, 07:23 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.

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

   This incident has been resolved.

Read the full incident report →

Started May 06, 2026, 07:00 PM UTC· resolved May 06, 2026, 07:00 PM UTC

1. resolved May 06, 2026, 07:00 PM UTC

   The issue impacting the ability to open analytics applications in Qlik Cloud – US East (N. Virginia) has been mitigated. Service has been restored, and our teams are continuing to monitor the environment to ensure stability. We will share further updates if needed. We apologize for any inconvenience and appreciate your patience.

Read the full incident report →

Started May 05, 2026, 10:30 PM UTC· resolved May 05, 2026, 10:30 PM UTC

1. resolved May 05, 2026, 10:30 PM UTC

   We experienced a service impact with Talend Cloud – AZURE - West US (California) which was resolved at 12:51 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

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:34 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:20 PM UTC· resolved Apr 11, 2026, 12:30 AM UTC

1. investigating Apr 10, 2026, 01:20 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:26 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: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.

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 09, 2026, 07:41 PM UTC· resolved Apr 10, 2026, 01:16 AM UTC

1. investigating Apr 09, 2026, 07:41 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 09, 2026, 08:46 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 09, 2026, 10:22 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. monitoring Apr 10, 2026, 12:20 AM UTC

   We continue to work to improve this situation. We implemented fixes and continue to monitor the situation. Please open a support case if you see any additional issues.

5. resolved Apr 10, 2026, 01:16 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:17 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:49 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, 03:33 PM 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:32 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:49 AM UTC· resolved Mar 24, 2026, 07:56 AM UTC

1. investigating Mar 24, 2026, 05:49 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:53 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:23 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:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2026, 12:30 PM UTC· resolved Mar 17, 2026, 12:30 PM UTC

1. resolved Mar 17, 2026, 12:30 PM UTC

   We experienced a service impact with Qlik Cloud – AWS – US East (N. Virginia) which was resolved at 12:30 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started Mar 01, 2026, 01:22 PM UTC· resolved Mar 10, 2026, 03:28 PM UTC

1. investigating Mar 01, 2026, 01:22 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, 07:00 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:44 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:28 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:31 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:37 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:01 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:58 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:47 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.

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

15. identified Mar 06, 2026, 01:41 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.

16. resolved Mar 10, 2026, 03:28 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 Feb 24, 2026, 01:00 PM UTC· resolved Feb 24, 2026, 01:15 PM UTC

1. resolved Feb 24, 2026, 01:00 PM UTC

   We experienced a UI degradation with Qlik Cloud across all regions which was resolved at 12:51 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.

2. postmortem Feb 27, 2026, 08:33 AM UTC

   **Summary of Impact:** On February 24th, 2026, starting at approximately 12:36 UTC and lasting for 15 minutes, Qlik Cloud customers experienced rendering issues on some Qlik Cloud UI pages. **Root Cause:** A system update incorrectly decommissioned a software library required for rendering portions of the Qlik user interface \(UI\). This resulted in an application error when users attempted to use the catalog view, sheet analytics, and charting modules. Other aspects of the UI were not impacted. **Resolution and Remediation:** Qlik Engineering and Operations teams promptly identified the issue and reverted the release. Following this action, services were restored, and customers could render the Qlik Cloud UI. We apologize for any inconvenience this disruption may have caused to your operations.

Read the full incident report →

Started Feb 18, 2026, 05:36 PM UTC· resolved Feb 18, 2026, 09:52 PM UTC

1. investigating Feb 18, 2026, 05:36 PM UTC

   We're investigating an issue affecting user login in Qlik Cloud – US East 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 Feb 18, 2026, 06:01 PM UTC

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

3. monitoring Feb 18, 2026, 06:35 PM UTC

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

4. resolved Feb 18, 2026, 09:52 PM UTC

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

Read the full incident report →