Qlik Cloud experienced a minor incident on June 11, 2026 affecting Qlik Cloud – AWS – Europe (Frankfurt), lasting 1h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2026, 10:33 AM UTC
We're investigating a potential issue with Qlik Cloud – Europe (Frankfurt) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- identified Jun 11, 2026, 10:52 AM UTC
The issue has been identified, and our team is actively working on mitigation and implementing a fix.
- monitoring Jun 11, 2026, 10:55 AM UTC
The issue has been fixed and the team is monitoring the results.
- resolved Jun 11, 2026, 11:38 AM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
- postmortem Jun 30, 2026, 01:13 PM UTC
**Summary of Impact:** On June 11, 2026, between approximately 09:56 UTC and 10:32 UTC, a limited subset of Qlik Cloud customers experienced intermittent disruptions affecting tenant access and navigation, application opening, reload execution, automation runs, Talend Cloud task execution, and report delivery. Some actions during the impact window may have been delayed or required retry. **Root Cause:** The issue was traced to a platform access-control configuration update which temporarily affected certain backend service operations. As a result, multiple dependent services were temporarily unable to complete normal processing, which led to customer-facing disruptions across tenant access, application opening, reloads, automations, and reporting workflows. **Resolution and Remediation:** The Qlik Engineering team promptly identified the root cause and rolled back the configuration update, after which services began recovering. Additional operational recovery actions were completed to stabilize impacted services and restore normal processing. To prevent recurrence, Qlik is strengthening its pre-production validation procedures for access-control configuration changes before production rollout and enhancing monitoring and recovery handling for service dependency failures and cascading impact scenarios.