Qlik Cloud incident

Qlik Cloud® – Europe (Ireland)

Minor Resolved View vendor source →

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

Started
Sep 02, 2026, 07:28 AM UTC
Resolved
Sep 02, 2026, 08:08 AM UTC
Duration
40m
Detected by Pingoru
Sep 02, 2026, 07:28 AM UTC

Affected components

Qlik Cloud – AWS – Europe (Ireland)

Update timeline

  1. investigating Sep 02, 2026, 07:28 AM UTC

    We're investigating an issue affecting content visibility in the Hub in Qlik Cloud – Europe (Ireland) and are diligently working to resolve the issue as soon as possible. Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

  2. identified Sep 02, 2026, 07:47 AM UTC

    The issue has been identified, and our team is actively working on mitigation and implementing a fix.

  3. monitoring Sep 02, 2026, 07:48 AM UTC

    The issue has been fixed and the team is monitoring the results.

  4. resolved Sep 02, 2026, 08:08 AM UTC

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

  5. postmortem Sep 07, 2026, 01:38 PM UTC

    **Summary of Impact:** On September 2, 2026, from approximately 06:27AM to 07:53 AM UTC, a subset of Qlik Cloud users with tenants in the EU West \(Ireland\) region encountered service degradation. This event impacted the Hubs and Spaces; although it did not prevent user access or cause service failures, it resulted in response delays while navigating the platform and opening applications. **Root Cause:** The issue was caused by elevated read/write latency in a caching layer responsible for authentication and session data in the EU West region. As traffic patterns evolved, the caching layer’s resource limits did not scale accordingly. Under increased load, it became unable to process requests efficiently, causing degraded performance in certain Hubs and Spaces in the region. **Resolution and Remediation:** The Qlik Engineering team traced the elevated latency to the caching layer and increased cashing layer resources. This restored response times to normal levels for affected customers. To help prevent recurrence, the team is reviewing capacity planning for the caching layer to proactively address future scaling needs, enhancing automated alerting to detect resource-limit issues earlier, and strengthening monitoring across dependent services to reduce time-to-detection for similar issues. We apologize for any inconvenience the delays in service may have caused and are committed to delivering the reliable experience our customers expect from Qlik Cloud.