- Detected by Pingoru
- May 06, 2026, 07:58 PM UTC
- Resolved
- May 06, 2026, 07:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 06, 2026, 07:58 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 →
- Detected by Pingoru
- May 06, 2026, 01:06 PM UTC
- Resolved
- May 05, 2026, 10:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 06, 2026, 01:06 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 →
- Detected by Pingoru
- Apr 10, 2026, 01:20 PM UTC
- Resolved
- Apr 11, 2026, 12:30 AM UTC
- Duration
- 11h 10m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 7 updates
-
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.
-
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.
-
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.
-
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.
-
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.
-
identified Apr 10, 2026, 10:02 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Apr 11, 2026, 12:30 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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.
-
monitoring Apr 08, 2026, 10:17 AM UTC
The issue has been fixed and the team is monitoring the results.
-
resolved Apr 08, 2026, 10:59 AM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
-
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 →
- Detected by Pingoru
- Mar 25, 2026, 04:33 AM UTC
- Resolved
- Mar 25, 2026, 03:33 PM UTC
- Duration
- 11h
Timeline · 1 update
-
resolved Mar 25, 2026, 11:24 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 →
- Detected by Pingoru
- Mar 24, 2026, 05:32 PM UTC
- Resolved
- Mar 24, 2026, 05:32 PM UTC
- Duration
- —
Affected: Talend Cloud - AWS - Asia Pacific (Sydney)
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 24, 2026, 05:49 AM UTC
- Resolved
- Mar 24, 2026, 07:56 AM UTC
- Duration
- 2h 6m
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 5 updates
-
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.
-
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.
-
identified Mar 24, 2026, 07:23 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 24, 2026, 07:25 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 24, 2026, 07:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 01:22 PM UTC
- Resolved
- Mar 10, 2026, 03:28 PM UTC
- Duration
- 9d 2h
Affected: Qlik Cloud - AWS - Middle East (UAE)
Timeline · 16 updates
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 01:00 PM UTC
- Resolved
- Feb 24, 2026, 01:00 PM UTC
- Duration
- —
Timeline · 2 updates
-
resolved Feb 24, 2026, 01:01 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.
-
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 →
- Detected by Pingoru
- Feb 18, 2026, 05:36 PM UTC
- Resolved
- Feb 18, 2026, 09:52 PM UTC
- Duration
- 4h 15m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 4 updates
-
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.
-
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.
-
monitoring Feb 18, 2026, 06:35 PM UTC
The issue has been fixed and the team is monitoring the results.
-
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 →
Critical February 7, 2026 - Detected by Pingoru
- Feb 07, 2026, 08:59 AM UTC
- Resolved
- Feb 07, 2026, 11:28 AM UTC
- Duration
- 2h 28m
Affected: Talend Cloud - AZURE - West US (California)
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 10:15 AM UTC
- Resolved
- Feb 04, 2026, 11:27 AM UTC
- Duration
- 1h 12m
Affected: Qlik Cloud – AWS – Europe (Ireland)Qlik Cloud – AWS – Europe (Frankfurt)Qlik Cloud – AWS – Asia Pacific (Tokyo)
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 05:02 PM UTC
- Resolved
- Jan 28, 2026, 08:02 PM UTC
- Duration
- 3h
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 7 updates
-
investigating Jan 28, 2026, 05:02 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.
-
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.
-
identified Jan 28, 2026, 06:21 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.
-
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.
-
monitoring Jan 28, 2026, 07:28 PM UTC
The issue has been fixed by AWS and we are monitoring the results.
-
resolved Jan 28, 2026, 08:02 PM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
-
postmortem Jan 29, 2026, 05:44 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 →
- Detected by Pingoru
- Oct 20, 2025, 07:53 AM UTC
- Resolved
- Oct 21, 2025, 08:55 AM UTC
- Duration
- 1d 1h
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2025, 12:00 PM UTC
- Resolved
- Sep 09, 2025, 02:27 PM UTC
- Duration
- 2h 27m
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)
Timeline · 6 updates
-
investigating Sep 09, 2025, 12:00 PM 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.
-
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.
-
monitoring Sep 09, 2025, 12:50 PM UTC
The issue has been fixed and the team is monitoring the results.
-
identified Sep 09, 2025, 01:16 PM UTC
Our team is continuing to diligently work on resolving the issue. We will keep you posted on any further updates.
-
monitoring Sep 09, 2025, 01:51 PM UTC
The issue has been fixed and the team is monitoring the results.
-
resolved Sep 09, 2025, 02:27 PM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2025, 07:25 AM UTC
- Resolved
- Aug 26, 2025, 01:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 26, 2025, 07:25 AM UTC
We experienced a service impact with Qlik Cloud – “AWS – Europe (Frankfurt)” which was resolved at 07:00 AM UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2025, 02:48 PM UTC
- Resolved
- Jul 21, 2025, 03:29 PM UTC
- Duration
- 40m
Affected: 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)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jul 12, 2025, 02:06 AM UTC
- Resolved
- Jul 12, 2025, 12:45 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 12, 2025, 02:06 AM UTC
We experienced a service impact with Qlik Talend Cloud – Asia Pacific (Tokyo) which was resolved at 01:27 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2025, 01:08 PM UTC
- Resolved
- Jun 25, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 25, 2025, 01:08 PM UTC
We experienced a service impact with Talend Cloud – AWS - Europe (Frankfurt) which was resolved it at 12:50 UTC. All services are working as expected again. We apologize for the inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- May 22, 2025, 08:45 PM UTC
- Resolved
- May 22, 2025, 07:34 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 22, 2025, 08:45 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 →
- Detected by Pingoru
- May 20, 2025, 09:16 PM UTC
- Resolved
- May 20, 2025, 10:40 PM UTC
- Duration
- 1h 23m
Affected: Talend Cloud - AWS - US East (N. Virginia)
Timeline · 5 updates
-
investigating May 20, 2025, 09:16 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.
-
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.
-
identified May 20, 2025, 10:19 PM UTC
The issue has been identified, and our team is actively working on mitigation and implementing a fix.
-
monitoring May 20, 2025, 10:23 PM UTC
The issue has been fixed and the team is monitoring the results.
-
resolved May 20, 2025, 10:40 PM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- May 05, 2025, 04:40 PM UTC
- Resolved
- May 05, 2025, 06:44 PM UTC
- Duration
- 2h 3m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 07:01 AM UTC
- Resolved
- Apr 23, 2025, 03:19 PM UTC
- Duration
- 8h 17m
Affected: Qlik Cloud – AWS – US East (N. Virginia)
Timeline · 4 updates
-
identified Apr 23, 2025, 07:01 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.
-
identified Apr 23, 2025, 07:51 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.
-
monitoring Apr 23, 2025, 08:40 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 23, 2025, 03:19 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 →
- Detected by Pingoru
- Mar 07, 2025, 12:00 AM UTC
- Resolved
- Mar 06, 2025, 10:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2025, 09:45 AM UTC
- Resolved
- Feb 25, 2025, 11:30 AM UTC
- Duration
- 1h 45m
Affected: Qlik Cloud – AWS – Europe (Ireland)
Timeline · 5 updates
Read the full incident report →