Qase Status Page

Jul 14, 2026 · resolved Jul 14

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.

Jan 9, 2026 · resolved Jan 9

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

Dec 3, 2025 · resolved Dec 3

## 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.

Sep 16, 2025 · resolved Sep 16

This incident has been resolved.

Apr 2, 2025 · resolved Apr 2

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

Is Qase down right now?

No — Qase is up. All systems operational as of Aug 19, 9:39 PM UTC.

What is Qase's current status?

Qase: All Systems Operational. Alert24 checks Qase's status page continuously and can notify you the moment it changes.

How do I get alerted when Qase goes down?

Alert24 monitors Qase and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.