SonarQube incident

SonarQube Cloud:

Major Resolved View vendor source →

SonarQube experienced a major incident on August 4, 2025 affecting Automatic Analysis and Automatic Analysis and 1 more component, lasting 6d 22h. The incident has been resolved; the full update timeline is below.

Started
Aug 04, 2025, 02:05 PM UTC
Resolved
Aug 11, 2025, 12:56 PM UTC
Duration
6d 22h
Detected by Pingoru
Aug 04, 2025, 02:05 PM UTC

Affected components

Automatic AnalysisAutomatic AnalysisCI-based AnalysisCI-based Analysis

Update timeline

  1. investigating Aug 04, 2025, 02:05 PM UTC

    We are experiencing an issue causing sporadic failure of Automatic and CI-based analysis across all languages. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

  2. investigating Aug 06, 2025, 03:20 PM UTC

    We are actively working to reduce the error rate and collaborating with our cloud provider to investigate further. We hope to resolve the root cause soon. We apologize again for the ongoing disruption and appreciate your patience.

  3. monitoring Aug 06, 2025, 09:44 PM UTC

    Our Cloud provider has identified the root cause of the issue and has already addressed the issue in the region with the highest rate of failure. We have confirmed that the rate of failure has dropped to zero in that region. Now we are waiting for the fix to be applied across all regions. Thank you for your continued patience and understanding as we work to fully resolve the issue

  4. monitoring Aug 07, 2025, 08:39 AM UTC

    Our Cloud provider is actively rolling out the fix and prioritizing the most affected regions, to restore service as quickly as possible. However, due to the nature of this global deployment, the rollout will take some time. You may continue to experience the error until the fix is fully deployed. Thank you for your patience and understanding as we work to fully resolve the issue.

  5. resolved Aug 11, 2025, 12:56 PM UTC

    This incident has been resolved. Thank you for your patience and support during this period of time.