Qlik Cloud incident

Qlik Cloud login failure

Notice Resolved View vendor source →

Qlik Cloud experienced a notice incident on July 21, 2025 affecting Qlik Cloud – AWS – Europe (Ireland) and Qlik Cloud – AWS – Europe (London) and 1 more component, lasting 40m. The incident has been resolved; the full update timeline is below.

Started
Jul 21, 2025, 02:48 PM UTC
Resolved
Jul 21, 2025, 03:29 PM UTC
Duration
40m
Detected by Pingoru
Jul 21, 2025, 02:48 PM UTC

Affected components

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)

Update timeline

  1. monitoring Jul 21, 2025, 02:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. monitoring Jul 21, 2025, 03:02 PM UTC

    The issue impacting user logins with Qlik Cloud has been resolved. Users should now be able to log in as expected. We appreciate your patience and apologize for any inconvenience caused during the disruption. Our team will continue diligently monitor it.

  3. resolved Jul 21, 2025, 03:29 PM UTC

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

  4. postmortem Jul 25, 2025, 01:45 PM UTC

    **User login impact - Qlik Cloud®** **Root Cause Analysis:** On July 21st, 2025, starting at approximately 14:11 UTC and lasting up to 17 minutes depending on region, customers may have experienced Qlik Cloud login failures. The incident was caused by a conflict between two backend service changes that required a specific initialization sequence to function correctly. Deploying them at the same time led to an unexpected condition that temporarily prevented the licensing system from processing login requests. This was an isolated scenario. This was not a malicious event, and no customer data was compromised. **Resolution and Remediations:** The resolution involved disabling the two backend changes temporarily, which immediately restored the licensing system. To further enhance platform resiliency, Qlik is expanding validation coverage and optimizing the handling of backend change dependencies. We appreciate your patience and trust as we continue improving the resilience and reliability of our platform.