Qlik incident

Qlik Cloud® – US East (N. Virginia)

Minor Resolved View vendor source →

Qlik experienced a minor incident on April 11, 2026 affecting Qlik Cloud – AWS – US East (N. Virginia), lasting 54m. The incident has been resolved; the full update timeline is below.

Started
Apr 11, 2026, 10:55 AM UTC
Resolved
Apr 11, 2026, 11:49 AM UTC
Duration
54m
Detected by Pingoru
Apr 11, 2026, 10:55 AM UTC

Affected components

Qlik Cloud – AWS – US East (N. Virginia)

Update timeline

  1. investigating Apr 11, 2026, 10:55 AM UTC

    We're investigating a potential issue with Qlik Cloud – US East (N. Virginia) Updates will be provided as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.

  2. identified Apr 11, 2026, 11:30 AM UTC

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

  3. monitoring Apr 11, 2026, 11:34 AM UTC

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

  4. resolved Apr 11, 2026, 11:49 AM UTC

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

  5. postmortem Apr 28, 2026, 02:29 PM UTC

    **Summary of Impact:** From April 8 to April 11, 2026, customers utilizing the Qlik Cloud US-East-1 \(North Virginia\) region may have experienced intermittent service disruptions. Primary observations included delays in application reloads, login failures, and “Internal Server Error” messages. While these issues were observed in the user interface, backend processes remained functional and executed as expected. **Root Cause:** The investigation attributed the incident to two primary factors: i\) database resource contention that delayed processing of reloads and authentication requests; and ii\) a configuration mismatch impacting tenant accessibility. **Remediation:** Qlik Engineering responded by immediately increasing database capacity and deploying an emergency configuration patch. To ensure long-term stability, we improved database infrastructure segregation to prevent future database resource contention and applied performance optimization enhancements to reduce system latency. We apologize for any inconvenience this disruption may have caused and are committed to delivering the reliable experience our customers expect from Qlik Cloud.