Qlik Cloud experienced a minor incident on April 10, 2026 affecting Qlik Cloud – AWS – US East (N. Virginia), lasting 11h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 10, 2026, 01:20 PM UTC
We're investigating an issue affecting multiple areas of the platform, including: login failures, opening apps and reloads delays 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.
- investigating Apr 10, 2026, 02:20 PM UTC
We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue as soon as possible. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- investigating Apr 10, 2026, 04:26 PM UTC
We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- investigating Apr 10, 2026, 05:56 PM UTC
We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- investigating Apr 10, 2026, 07:56 PM UTC
We continue to investigate issues with Qlik Cloud and are diligently working to resolve the issue plus putting in mitigation controls. Updates will be provided here as new information becomes available during the resolution process. We apologize for any inconvenience and appreciate your patience.
- identified Apr 10, 2026, 10:02 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 11, 2026, 12:30 AM UTC
This incident has been resolved.