Qase Outage History

Qase is up right now

Qase had 6 outages in the last 2 years totaling 13h 28m of downtime — averaging 0.2 incidents per month.

There were 6 Qase outages since March 27, 2025 totaling 13h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.qase.io

Notice January 9, 2026

WEB UI and Public API unavailability

Detected by Pingoru
Jan 09, 2026, 04:03 PM UTC
Resolved
Jan 09, 2026, 11:30 AM UTC
Duration
Timeline · 1 update
  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 →

Critical September 16, 2025

Website Unreachable

Detected by Pingoru
Sep 16, 2025, 10:27 AM UTC
Resolved
Sep 16, 2025, 10:57 AM UTC
Duration
29m
Affected: Website
Timeline · 2 updates
  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 →

Major April 2, 2025

Infinite reloading

Detected by Pingoru
Apr 02, 2025, 09:12 AM UTC
Resolved
Apr 02, 2025, 08:24 AM UTC
Duration
Timeline · 1 update
  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 →

Minor April 2, 2025

Delayed processing

Detected by Pingoru
Apr 02, 2025, 09:10 AM UTC
Resolved
Apr 02, 2025, 05:44 PM UTC
Duration
8h 33m
Affected: WebsiteAPIApplication
Timeline · 4 updates
  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 →

Minor March 27, 2025

Degraded performance due to unusually increasing traffic

Detected by Pingoru
Mar 27, 2025, 02:31 PM UTC
Resolved
Mar 27, 2025, 06:56 PM UTC
Duration
4h 25m
Affected: WebsiteAPIApplication
Timeline · 4 updates
  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 →