Qlik Outage History

Qlik major outage View live status →

There were 9 Qlik outages since February 4, 2026 totaling 249h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.qlikcloud.com

Minor April 11, 2026

Qlik Cloud® – US East (N. Virginia)

Detected by Pingoru
Apr 11, 2026, 10:55 AM UTC
Resolved
Apr 11, 2026, 11:49 AM UTC
Duration
54m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 5 updates
  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 →

Minor April 10, 2026

Qlik Cloud® – AWS – US East (N. Virginia)

Detected by Pingoru
Apr 10, 2026, 01:19 PM UTC
Resolved
Apr 11, 2026, 12:30 AM UTC
Duration
11h 10m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 7 updates
  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 →

Minor April 8, 2026

Qlik Cloud® – AWS – Europe (Ireland)

Detected by Pingoru
Apr 08, 2026, 09:39 AM UTC
Resolved
Apr 08, 2026, 10:59 AM UTC
Duration
1h 19m
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 5 updates
  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 →

Notice March 25, 2026

Qlik Cloud – AWS - Europe (Ireland)

Detected by Pingoru
Mar 25, 2026, 04:33 AM UTC
Resolved
Mar 25, 2026, 03:33 PM UTC
Duration
11h
Timeline · 1 update
  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 →

Notice March 24, 2026

Talend Cloud - AWS - Asia Pacific (Sydney) - Flow failures between 13:12 UTC and 15:09 UTC

Detected by Pingoru
Mar 24, 2026, 05:35 PM UTC
Resolved
Mar 24, 2026, 05:35 PM UTC
Duration
—
Affected: Talend Cloud - AWS - Asia Pacific (Sydney)
Timeline · 1 update
  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 →

Minor March 24, 2026

Qlik Cloud® – Ireland (eu-west-1)

Detected by Pingoru
Mar 24, 2026, 05:51 AM UTC
Resolved
Mar 24, 2026, 07:57 AM UTC
Duration
2h 5m
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 5 updates
  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 →

Critical March 1, 2026

Qlik Cloud - UAE

Detected by Pingoru
Mar 01, 2026, 01:24 PM UTC
Resolved
Mar 10, 2026, 03:26 PM UTC
Duration
9d 2h
Affected: Qlik Cloud – AWS – Middle East (UAE)
Timeline · 17 updates
  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 →

Minor February 18, 2026

Qlik Cloud® – Login

Detected by Pingoru
Feb 18, 2026, 05:38 PM UTC
Resolved
Feb 18, 2026, 09:51 PM UTC
Duration
4h 13m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 5 updates
  1. investigating Feb 18, 2026, 05:38 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. monitoring Feb 18, 2026, 06:36 PM UTC

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

  5. resolved Feb 18, 2026, 09:51 PM UTC

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

Read the full incident report →

Minor February 4, 2026

Qlik Cloud®

Detected by Pingoru
Feb 04, 2026, 10:16 AM UTC
Resolved
Feb 04, 2026, 11:27 AM UTC
Duration
1h 11m
Affected: Qlik Cloud – AWS – Europe (Ireland)Qlik Cloud – AWS – Europe (Frankfurt)Qlik Cloud – AWS – Asia Pacific (Tokyo)
Timeline · 6 updates
  1. investigating Feb 04, 2026, 10:16 AM UTC

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

  2. investigating Feb 04, 2026, 10:33 AM UTC

    We're investigating an issue affecting multiple areas of the platform, including: opening apps in Qlik Cloud across multiple regions. Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

  3. identified Feb 04, 2026, 11:02 AM UTC

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

  4. monitoring Feb 04, 2026, 11:12 AM UTC

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

  5. resolved Feb 04, 2026, 11:27 AM UTC

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

  6. postmortem Feb 06, 2026, 01:59 PM UTC

    **Summary of Impact:** On February 4, 2026, between approximately 09:51 AM UTC and 10:49 AM UTC, Qlik Cloud® customers across all regions may have experienced intermittent issues affecting multiple functionalities, including opening Qlik analytics apps, running Automations, delayed reloads, and other operations. Customers whose tenants are hosted in the AWS Asia Pacific \(Tokyo\) region experienced a full service outage during this period. **Root Cause:** The incident was caused by a Kubernetes admission controller that impacted the ability of new application instances to start correctly. The same issue with the admission controller caused a routine after-hours failover maintenance activity in the Tokyo region to fail, resulting in an outage only in that region. **Resolution and Remediation:** Once the issue with the admission controller was identified, a corrected version was deployed, allowing new application instances to start normally. The messaging cluster in the Tokyo region completed its failover successfully, and all affected services across regions returned to normal operation. To further enhance platform resiliency, Qlik is continuing to optimize operational procedures, and increase overall reliability. Additional testing and validation will be conducted to ensure similar issues are mitigated more effectively in the future. We apologize for any inconvenience this disruption may have caused to your operations.

Read the full incident report →

Looking to track Qlik downtime and outages?

Pingoru polls Qlik's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Qlik reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Qlik alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Qlik for free

5 free monitors · No credit card required