Qlik incident

Qlik Cloud® Data Integration (QDI) - Europe (Ireland)

Minor Resolved View vendor source →

Qlik experienced a minor incident on June 23, 2026 affecting Qlik Cloud – AWS – Europe (Ireland), lasting 39m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 02:54 PM UTC
Resolved
Jun 23, 2026, 03:34 PM UTC
Duration
39m
Detected by Pingoru
Jun 23, 2026, 02:54 PM UTC

Affected components

Qlik Cloud – AWS – Europe (Ireland)

Update timeline

  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.