Qlik Cloud®

Update timeline

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.