Qase Outage History

On July 14, 2026, between approximately 10:30 and 11:20 UTC, Qase experienced degraded performance and elevated error rates. Intermittent slow responses and timeouts began around 10:30 UTC, with the most significant impact between 11:00 and 11:17 UTC, during which some requests to the web application and API failed with 5xx errors. Service was restored at 11:13 UTC, and normal operation was confirmed by 11:20 UTC. Failed requests can be safely retried. The root cause has been identified, and a permanent fix is being rolled out in stages - the first stage is already live.

During a planned database migration, a schema change took significantly longer than expected and did not complete successfully. While the migration was in progress, the table was locked, causing requests dependent on this table to queue. As a result, the backend was temporarily unable to process incoming requests, leading to service disruption. Duration: Approximately 20m Incident resolved

This incident has been resolved.

Some customers experienced an issue where the application entered an infinite reload loop for a few minutes. The problem was quickly identified and resolved. We apologize for any inconvenience this may have caused.

All systems are operating normally. Our teams keep monitoring closely to ensure stability and performance. Thank you for your patience and understanding.

Performance has fully recovered, and all systems are operating normally. Our teams have closely monitored stability, and everything is back to normal. Thank you for your patience and understanding.