Qlik incident

Qlik Cloud®

Major Resolved View vendor source →

Qlik experienced a major incident on May 28, 2026 affecting Qlik Cloud – AWS – US East (N. Virginia) and Qlik Cloud – AWS – Europe (Ireland) and 1 more component, lasting 48m. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 06:53 PM UTC
Resolved
May 28, 2026, 07:42 PM UTC
Duration
48m
Detected by Pingoru
May 28, 2026, 06:53 PM UTC

Affected components

Qlik Cloud – AWS – US East (N. Virginia)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)Qlik Cloud - AWS - Israel (Tel Aviv)

Update timeline

  1. investigating May 28, 2026, 06:53 PM UTC

    We're investigating an issue affecting reloads in Qlik Cloud 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. investigating May 28, 2026, 06:55 PM UTC

    We are continuing to investigate this issue.

  3. identified May 28, 2026, 07:22 PM UTC

    We have identified the issue affecting reloads in Qlik Cloud and are diligently working to resolve the issue. We apologize for any inconvenience and appreciate your patience.

  4. resolved May 28, 2026, 07:42 PM UTC

    This incident has been resolved.