Qlik Outage History

Qlik major outage View live status →

Qlik had 15 outages in the last 2 years totaling 279h 40m of downtime — averaging 0.6 incidents per month.

There were 15 Qlik outages since September 9, 2025 totaling 279h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.qlikcloud.com

Minor June 26, 2026

Qlik Cloud® – Login

Detected by Pingoru
Jun 26, 2026, 07:14 AM UTC
Resolved
Jun 26, 2026, 08:01 AM UTC
Duration
47m
Affected: Qlik Cloud – AWS – US East (N. Virginia)Qlik Cloud – AWS – Europe (Ireland)Qlik Cloud – AWS – Europe (London)Qlik Cloud – AWS – Europe (Frankfurt)Qlik Cloud – AWS – Asia Pacific (Sydney)Qlik Cloud – AWS – Asia Pacific (Singapore)Qlik Cloud – AWS – Asia Pacific (Tokyo)Qlik Cloud – AWS – Asia Pacific (Mumbai)Qlik Cloud - AWS - Israel (Tel Aviv)Qlik Cloud - AWS - South America (São Paulo)Qlik Cloud - AWS - Europe (Paris)Talend Cloud - AWS - US East (N. Virginia)Talend Cloud - AWS - Europe (Frankfurt)Talend Cloud - AWS - Asia Pacific (Tokyo)Talend Cloud - AWS - Asia Pacific (Sydney)Talend Cloud - AZURE - West US (California)Qlik Cloud - AWS - Canada (Montreal)
Timeline · 4 updates
  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 →

Major May 28, 2026

Qlik Cloud®

Detected by Pingoru
May 28, 2026, 06:53 PM UTC
Resolved
May 28, 2026, 07:42 PM UTC
Duration
48m
Affected: Qlik Cloud – AWS – US East (N. Virginia)Qlik Cloud – AWS – Europe (Ireland)Qlik Cloud – AWS – Europe (London)Qlik Cloud – AWS – Europe (Frankfurt)Qlik Cloud – AWS – Asia Pacific (Sydney)Qlik Cloud – AWS – Asia Pacific (Singapore)Qlik Cloud – AWS – Asia Pacific (Tokyo)Qlik Cloud – AWS – Asia Pacific (Mumbai)Qlik Cloud – AWS – Middle East (UAE)Qlik Cloud - AWS - Israel (Tel Aviv)Qlik Cloud - AWS - South America (São Paulo)Qlik Cloud - AWS - Europe (Paris)Qlik Cloud Government (Fedramp) - AWS – GovCloud (West)Qlik Cloud Government (DOD) - AWS – GovCloud (West)Talend Cloud - AWS - US East (N. Virginia)Talend Cloud - AWS - Europe (Frankfurt)Talend Cloud - AWS - Asia Pacific (Tokyo)Talend Cloud - AWS - Asia Pacific (Sydney)Talend Cloud - AZURE - West US (California)
Timeline · 4 updates
  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 →

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

Read the full incident report →

Minor January 28, 2026

Qlik Cloud® – Ireland

Detected by Pingoru
Jan 28, 2026, 05:01 PM UTC
Resolved
Jan 28, 2026, 08:01 PM UTC
Duration
3h
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 7 updates
  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 →

Minor September 9, 2025

Qlik Cloud® – Reporting Issues

Detected by Pingoru
Sep 09, 2025, 11:59 AM UTC
Resolved
Sep 09, 2025, 02:25 PM UTC
Duration
2h 26m
Affected: Qlik Cloud – AWS – Europe (Ireland)Qlik Cloud – AWS – Europe (Frankfurt)
Timeline · 6 updates
  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 →