Qlik Cloud experienced a minor incident on June 22, 2026 affecting Qlik Cloud – AWS – Europe (Ireland), lasting 1h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 22, 2026, 08:00 AM UTC
We're investigating a potential issue with Qlik Cloud – Europe (Ireland) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- investigating Jun 22, 2026, 08:29 AM UTC
We have identified elevated error rates across multiple services in our Europe (Ireland) region. Users may intermittently experience failures when opening apps, errors loading the hub, and issues browsing data files. Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- identified Jun 22, 2026, 08:44 AM UTC
The issue has been identified, and our team is actively working on mitigation and implementing a fix.
- monitoring Jun 22, 2026, 08:53 AM UTC
The issue has been fixed and the team is monitoring the results.
- resolved Jun 22, 2026, 09:18 AM UTC
This issue has been resolved. We apologize for the inconvenience and appreciate your patience.
- postmortem Jun 30, 2026, 01:16 PM UTC
**Summary of Impact:** On June 22, 2026, customers using the Qlik Cloud® – Europe \(Ireland\) region may have experienced intermittent performance degradation affecting Qlik Cloud Analytics applications. Users may have seen intermittent issues opening Qlik Sense applications, loading the hub, or browsing data files. The impact occurred during the following periods: * 07:03–08:41 UTC * 12:03–12:39 UTC * 13:03–13:25 UTC **Root Cause:** A service update caused unexpected behavior in a backend component, which led to temporary resource contention and increased latency. This resulted in a low rate of intermittent errors affecting application access and related services. **Resolution and Remediation:** Qlik Engineering and Operations teams identified the contributing update and performed a rollback to a stable version of the service. This restored consistent system performance. To strengthen resilience and reduce the risk of recurrence, the following improvements are being implemented: * Targeted backend component fixes to prevent resource contention under load * Expanded pre-production performance and regression testing under load * Improved monitoring and alerting for early detection of latency and error-rate anomalies We apologize for any inconvenience caused by these intermittent performance impacts and appreciate your patience throughout the investigation and resolution process.