Qase Outage History

Started Jul 14, 2026, 10:30 AM UTC· resolved Jul 14, 2026, 11:20 AM UTC

1. resolved Jul 14, 2026, 03:33 PM UTC

   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.

Read the full incident report →

Started Jan 09, 2026, 11:30 AM UTC· resolved Jan 09, 2026, 11:30 AM UTC

1. resolved Jan 09, 2026, 04:03 PM UTC

   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

Read the full incident report →

Started Dec 03, 2025, 08:50 AM UTC· resolved Dec 03, 2025, 08:50 AM UTC

1. resolved Dec 03, 2025, 12:59 PM UTC

   Duration: Approximately 40m Incident resolved

2. postmortem Dec 03, 2025, 01:00 PM UTC

   ## Summary Earlier today, our platform experienced a period of degraded API performance. The issue was triggered by an unusually large burst of automated traffic that exceeded our expected operational thresholds and highlighted limits in one of our protection layers. ## Impact • Some customers observed elevated error rates or timeouts when calling the API. • The impact was intermittent and limited to a subset of traffic. ## What Happened Our systems received an extremely high volume of repeated requests. While our application includes rate limiting, this surge occurred at a level that prevented the application-layer limiter from fully initializing and applying its rules effectively. As part of our mitigation process, we blocked the traffic at the network level. Once the excessive traffic was filtered out, API performance stabilized and returned to normal. ## What We’re Doing to Prevent This Going Forward To strengthen our resilience, we are implementing the following improvements: * Restoring and Verifying Alerts: We are investigating why automated alerts were not propagated and will ensure the alerting pipeline works as intended. * Adding Ingress-Level Rate Limiting: A new traffic-shaping layer will be introduced at the ingress point to ensure that unusual spikes are controlled before they reach application components. This will protect the system even in scenarios where application-level rate limiting cannot fully activate. ## Current Status All services are operating normally, and we continue to monitor the platform closely. ‌ Thank You We appreciate your patience and understanding as we further strengthen the reliability and stability of our platform.

Read the full incident report →

Started Sep 16, 2025, 10:27 AM UTC· resolved Sep 16, 2025, 10:57 AM UTC

1. investigating Sep 16, 2025, 10:27 AM UTC

   Our website is currently not reachable due to an SSL handshake error. Our team is actively investigating the root cause. Please note that the Qase application, APIs, and reporters are fully operational and not affected.

2. resolved Sep 16, 2025, 10:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 02, 2025, 09:10 AM UTC· resolved Apr 02, 2025, 05:44 PM UTC

1. investigating Apr 02, 2025, 12:20 PM UTC

   We are experiencing delays in processing reports due to increased traffic and issues with our storage layer. Our team is actively investigating the issue. We appreciate your patience and will provide updates as we make progress.

2. investigating Apr 02, 2025, 12:27 PM UTC

   We are continuing to investigate this issue.

3. identified Apr 02, 2025, 05:17 PM UTC

   The issue has been identified and a fix has been implemented.

4. resolved Apr 02, 2025, 05:44 PM UTC

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

Read the full incident report →

Started Apr 02, 2025, 08:24 AM UTC· resolved Apr 02, 2025, 08:24 AM UTC

1. resolved Apr 02, 2025, 09:12 AM UTC

   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.

Read the full incident report →

Started Mar 27, 2025, 02:31 PM UTC· resolved Mar 27, 2025, 06:56 PM UTC

1. monitoring Mar 27, 2025, 02:31 PM UTC

   Degraded performance due to unusually increasing traffic

2. monitoring Mar 27, 2025, 05:48 PM UTC

   We are actively monitoring a significant increase in traffic and scaling our resources accordingly. Our team is implementing changes to improve processing times and restore full performance. We appreciate your patience and will provide updates as we make progress.

3. monitoring Mar 27, 2025, 06:34 PM UTC

   The resource scaling and recent changes have resulted in promising performance improvements. Our team continues to monitor the situation closely to ensure stability. We appreciate your patience and will provide further updates.

4. resolved Mar 27, 2025, 06:56 PM UTC

   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.

Read the full incident report →