SonarQube Outage History

Started Oct 16, 2026, 07:24 AM UTC· resolved Oct 16, 2026, 12:27 PM UTC

1. investigating Oct 16, 2026, 07:24 AM UTC

   We are aware of an issue where some projects are experiencing problems with their measure computation, which can lead to an incorrect quality gate status and are actively investigating. We will provide an update shortly.

2. investigating Oct 16, 2026, 08:13 AM UTC

   The database and index integrity checks have passed with no discrepancies found. Our investigation is now focused on live measure computation logic to isolate the root cause, and we will provide an update shortly.

3. resolved Oct 16, 2026, 12:27 PM UTC

   Thank you for your patience while we investigated the incorrect quality gate status and measures affecting some projects. This is no longer considered an active incident. If your project is still affected, re-running the analysis will restore the correct values. Our teams are tracking a permanent improvement. We sincerely apologize for any inconvenience this may have caused.

Read the full incident report →

Started Oct 05, 2026, 07:11 PM UTC· resolved Oct 05, 2026, 08:09 PM UTC

1. investigating Oct 05, 2026, 07:11 PM UTC

   We are currently investigating reports of delayed or failing analyses (availability of the C# Security and/or Architecture Analyzer packages). We will share an update as soon as we have more information. We apologize for the inconvenience.

2. investigating Oct 05, 2026, 07:20 PM UTC

   We are continuing to investigate the issue. Scope is limited to US region. Both Automatic and CI analysis affected.

3. monitoring Oct 05, 2026, 07:56 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 05, 2026, 08:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 08:34 PM UTC· resolved Sep 24, 2026, 11:11 PM UTC

1. investigating Sep 24, 2026, 08:34 PM UTC

   We are investigating a partial outage affecting pull request analysis results in SonarQube Cloud. Some customers may see their pull request analysis complete successfully, while the corresponding result is missing from the Pull Requests list or cannot be opened in SonarQube Cloud. Our teams are investigating and will provide an update as soon as more information is available.

2. resolved Sep 24, 2026, 11:11 PM UTC

   We have deployed a fix for an issue that caused some pull request analysis results to be missing from SonarQube Cloud, even when the analysis completed successfully. For pull requests affected before the fix was deployed, please push a new commit or rerun the pull request analysis to regenerate the result in SonarQube Cloud. New analyses are processing as expected.

Read the full incident report →

Started Sep 17, 2026, 07:22 PM UTC· resolved Sep 17, 2026, 08:08 PM UTC

1. identified Sep 17, 2026, 07:22 PM UTC

   We are investigating increased error rates affecting the SonarQube Cloud web experience, Automatic Analysis, and CI-based analysis. Some customers may experience failed or delayed analyses. Our engineering teams have identified the cause and working to restore normal service. We will provide another update as soon as more information is available.

2. resolved Sep 17, 2026, 08:08 PM UTC

   Resolved — We have resolved an issue that caused elevated errors and slower processing for Auto Scan and CI analyses. Processing performance has returned to normal. We will continue to monitor the service and are completing follow-up work to prevent recurrence. We apologize for the disruption.

Read the full incident report →

Started Sep 08, 2026, 12:13 PM UTC· resolved Sep 08, 2026, 01:00 PM UTC

1. investigating Sep 08, 2026, 12:13 PM UTC

   We are currently investigating reports of delayed analyses for Java Projects in EU. We will share an update as soon as we have more information. We apologize for the inconvenience.

2. monitoring Sep 08, 2026, 12:21 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 08, 2026, 01:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 04:43 PM UTC· resolved Sep 02, 2026, 07:30 PM UTC

1. resolved Sep 02, 2026, 07:35 PM UTC

   A limited number of customers may have experienced failures when attempting to download regulatory reports in the U.S. and Europe regions beginning at 16:43 UTC today. The EU instance recovered at 19:00 UTC and the U.S. instance recovered at 19:30 UTC, restoring full functionality for customers in both regions. We apologize for the inconvenience.

Read the full incident report →

Started Sep 02, 2026, 03:42 PM UTC· resolved Sep 02, 2026, 04:21 PM UTC

1. monitoring Sep 02, 2026, 03:42 PM UTC

   An issue was identified and has been mitigated. From 14:59 to 15:12 UTC, some customers in Europe experienced CI analysis failures. The disruption was caused by a temporary configuration inconsistency affecting Quality Profile availability. Service has been restored, and our team is monitoring the situation.

2. resolved Sep 02, 2026, 04:21 PM UTC

   Resolved — Automatic Analysis Performance Degradation (Europe) Between approximately 14:59–15:12 UTC, customers using SonarQube Cloud in Europe may have experienced failed automatic analyses due to a service issue affecting continuous integration processing. The issue has been resolved and the platform is operating normally. If your analysis failed during this window, it will not automatically re-run — please re-trigger the analysis from your CI pipeline. We apologize for the disruption and are continuing to investigate the underlying cause to prevent recurrence.

Read the full incident report →

Started Sep 02, 2026, 01:36 PM UTC· resolved Sep 02, 2026, 04:47 PM UTC

1. investigating Sep 02, 2026, 01:36 PM UTC

   We are currently investigating this issue.

2. resolved Sep 02, 2026, 04:47 PM UTC

   The issue has been resolved. AutoScan analysis processing has returned to normal, and there is no current customer impact. We will continue to monitor the service.

Read the full incident report →

Started Aug 28, 2026, 05:52 AM UTC· resolved Aug 28, 2026, 09:04 AM UTC

1. resolved Aug 28, 2026, 07:31 AM UTC

   Resolved — We have identified the root cause and confirmed the issue is fully resolved. Between 05:52 and 07:05 UTC on August 28, 2026, users on sonarqube.us may have been unable to sign in using GitHub, GitLab, Bitbucket, Azure DevOps, or SAML authentication. The issue was caused by a misconfiguration introduced during internal maintenance. Our team identified and corrected the configuration; a brief recurrence during the fix was resolved shortly after. Active user sessions and token-based traffic were not impacted. No other SonarQube Cloud services were affected. We apologize for the inconvenience this may have caused.

Read the full incident report →

Started Aug 11, 2026, 04:10 PM UTC· resolved Aug 13, 2026, 07:29 AM UTC

1. investigating Aug 11, 2026, 04:10 PM UTC

   We’ve identified an issue affecting a subset of projects that can cause CI analysis to fail when retrieving the project’s quality profile. The impact is limited: most customers and projects are not affected. No data has been lost or compromised. Analyses for affected projects will resume successfully once the underlying issue has been resolved. Our team is actively working on a fix and will share another update as soon as it has been deployed.

2. monitoring Aug 11, 2026, 09:24 PM UTC

   Monitoring — We have completed remediation for the primary issue affecting Quality Profiles. The impacted configuration data has been restored, and affected functionality is operating normally. We are continuing to investigate a separate, pre-existing source of intermittent errors. This work is not expected to affect the remediation above. We will provide another update as soon as we have more information.

3. resolved Aug 13, 2026, 07:29 AM UTC

   We have verified that the environment is fully stable and operating normally following remediation of the Quality Profile configuration issue. Preventive actions and long-term improvements are underway and will be tracked offline by our team. Thank you for your patience.

Read the full incident report →

Started Aug 06, 2026, 08:03 PM UTC· resolved Aug 07, 2026, 06:35 PM UTC

1. investigating Aug 06, 2026, 08:03 PM UTC

   We are investigating an issue affecting access to our Cloud API documentation at api-docs.sonarsource.com. Visitors may be unable to load the site due to SSL connection errors. We are working to restore access and will provide an update as soon as more information is available.

2. investigating Aug 06, 2026, 08:26 PM UTC

   The custom domain for our Cloud API documentation, http://api-docs.sonarsource.com/, is currently unavailable. Documentation remains available at https://sonar.portal.swaggerhub.com/. We are working to restore access through the custom domain.

3. investigating Aug 07, 2026, 12:22 PM UTC

   Update — The custom domain for our Cloud API documentation, api-docs.sonarsource.com, remains unavailable due to an SSL connection issue. Our documentation remains available at sonar.portal.swaggerhub.com. We have escalated the issue with our service provider and are working to restore access through the custom domain. We will provide another update as soon as more information is available.

4. monitoring Aug 07, 2026, 04:51 PM UTC

   Monitoring Update We have updated links across the web application and documentation to use sonar.portal.swaggerhub.com instead of api-docs.sonarsource.com, restoring access for most users. The custom domain, api-docs.sonarsource.com, remains unavailable because of an SSL connection issue. If this URL is hardcoded in any integrations, bookmarks, or configurations, you may continue to encounter errors until the underlying issue is resolved with our service provider. We will share another update as soon as more information is available.

5. resolved Aug 07, 2026, 06:35 PM UTC

   Resolved — The custom domain for our Cloud API documentation, api-docs.sonarsource.com, has been fully restored and is now functioning normally. All documentation and web application links have been (or are being) reverted to reference api-docs.sonarsource.com directly. This incident is now resolved.

Read the full incident report →

Started Jul 21, 2026, 03:36 PM UTC· resolved Jul 21, 2026, 04:38 PM UTC

1. resolved Jul 21, 2026, 05:03 PM UTC

   Resolved: Between approximately 15:30 and 16:52 UTC, some customers experienced elevated errors affecting code analysis and code viewing. The issue has been resolved, and services are operating normally. We will continue to monitor the platform to ensure stability.

2. postmortem Jul 22, 2026, 08:52 PM UTC

   # Root Cause Analysis \(RCA\) External Document ## Incident: SonarQube Cloud EU Outage on July 21, 2026 ## Incident Summary On July 21, 2026, from 15:36 to 16:38 UTC, SonarQube Cloud EU experienced elevated errors that affected code analysis and code viewing. Customers may have encountered failed analyses, including HTTP 500 and 504 responses, during the affected period. ## Incident Timeline \(UTC\) * **15:36:** Errors began. * **15:39:** Multiple high severity alarms were triggered and engineers started investigating the problem * **16:37:** Engineering restored the affected API Lambda and reverted the deployment. * **16:38:** Error rates returned to normal. * **After mitigation:** A resolved notice was posted on the status page. ## Root Cause Analysis A code change caused failures in a core Lambda function backing the API that retrieves source files from the database. This API is a critical step during the analysis process, thus all analyses began to fail. ## Resolution Engineering reverted the change to return to a known healthy state. Service error rates quickly returned to normal. ## Preventive and Improvement Measures * Assess options to make analysis more resilient when dependent file-information requests are unavailable. * Improve our status-page process to ensure updates more closely align with observed service errors as they occur. - Completed * We recognize that the status page should have reflected this disruption sooner; going forward, we will publish an initial notice when a significant customer impact is identified, then provide follow-up updates as investigation and recovery progress. ‌ We apologize for the disruption this incident caused and appreciate your patience.

Read the full incident report →

Started Jul 16, 2026, 08:46 AM UTC· resolved Jul 16, 2026, 01:04 PM UTC

1. investigating Jul 16, 2026, 08:46 AM UTC

   We are experiencing an issue resulting in the unavailability of SonarQube Cloud. 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. identified Jul 16, 2026, 09:29 AM UTC

   We have escalated the issue to our vendor and it is currently being investigated. Additionally, we are developing an in-house solution to mitigate this vendor-related challenges. 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.

3. identified Jul 16, 2026, 09:45 AM UTC

   We have escalated the issue to our vendor and it is currently being investigated. Additionally, we are developing an in-house solution to mitigate this vendor-related challenges. 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.

4. identified Jul 16, 2026, 10:22 AM UTC

   Whilst the vendor is actively working to fix the root cause issue and mitigate the impact, we are in parallel actively working on workaround options. 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.

5. identified Jul 16, 2026, 10:55 AM UTC

   While the vendor is implementing their root-cause fix, our engineers have designed a workaround and are actively working on the implementation for that workaround. 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.

6. monitoring Jul 16, 2026, 11:27 AM UTC

   The vendor has deployed a fix and the issue is now mitigated. We continue to monitor the stability of the environment. 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.

7. monitoring Jul 16, 2026, 11:29 AM UTC

   We are continuing to monitor for any further issues.

8. resolved Jul 16, 2026, 01:04 PM UTC

   Following confirmation of a full resolution from our vendor, all system functionality has been successfully restored and normal operations have resumed. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Jul 01, 2026, 08:30 AM UTC· resolved Jul 01, 2026, 09:35 AM UTC

1. resolved Jul 01, 2026, 10:06 AM UTC

   We experienced an issue resulting in some failures with AutoScan and CI Analysis between 08:34 UTC and 09:35 UTC. During this period a subset of customers analyses using the Scanner for .NET and who also had no local cache for the static dependency of the analyzer saw some failures in their AutoScan and CI Analyses. The issue has been remediated. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Jun 23, 2026, 11:56 AM UTC· resolved Jun 23, 2026, 02:53 PM UTC

1. investigating Jun 23, 2026, 11:56 AM UTC

   We are currently investigating an issue where users attempting to log in via SSO may not receive the one-time password (OTP) in their authentication email. Affected users will be unable to complete login using this method. We are actively investigating the root cause and will provide updates as more information becomes available. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. investigating Jun 23, 2026, 01:35 PM UTC

   We are continuing to investigate this issue. We will provide further updates as more information becomes available. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

3. identified Jun 23, 2026, 02:41 PM UTC

   We have identified the cause of this issue and are actively working on a fix. Thank you for your patience while we work to resolve this. We will provide another update once the resolution is deployed.

4. resolved Jun 23, 2026, 02:53 PM UTC

   The issue has been successfully resolved, and all SSO authentication emails are now being delivered correctly with the required one-time passwords (OTP). Thank you again for your patience. If you continue to experience any issues, please reach out via the Sonar Community or contact Support.

Read the full incident report →

Started Jun 10, 2026, 02:10 PM UTC· resolved Jun 11, 2026, 05:44 AM UTC

1. investigating Jun 10, 2026, 02:10 PM UTC

   We are investigating an issue affecting GitHub social login for SonarCloud. Some users may be unable to sign in to SonarCloud using GitHub at this time. Our current investigation indicates this is related to a third-party provider. We are actively monitoring the situation and will provide another update as soon as more information is available.

2. investigating Jun 10, 2026, 03:45 PM UTC

   We are continuing to monitor an issue affecting GitHub social login for SonarCloud. This appears to be related to an ongoing third-party incident affecting GitHub services. Customers can track the latest third-party updates on GitHub’s public status page here: GitHub status incident: https://www.githubstatus.com/incidents/fcj3088jg1wx

3. resolved Jun 11, 2026, 05:44 AM UTC

   This incident has been resolved. To report additional issues or share your observations, please visit the Sonar Community (https://community.sonarsource.com/) or contact Support.

Read the full incident report →

Started Jun 04, 2026, 01:20 PM UTC· resolved Jun 05, 2026, 09:29 AM UTC

1. investigating Jun 04, 2026, 01:20 PM UTC

   Investigating - We are investigating an issue causing intermittent HTTP 403 errors to be returned to GitHub Actions runners. These errors can show up when downloading SonarScanner CLI from binaries.sonarsource.com, as well as when contacting SonarQube Cloud during analysis. This is primarily impacting automated CI/CD workflows (such as GitHub Actions). We are actively working on a resolution with our infrastructure providers and will provide further updates shortly.

2. monitoring Jun 04, 2026, 06:38 PM UTC

   Monitoring - We have implemented mitigation measures to address the intermittent HTTP 403 errors affecting some downloads of SonarScanner CLI from binaries.sonarsource.com, as well as a subset of analysis requests from affected CI environments. We are continuing to monitor the situation closely to confirm stability.

3. monitoring Jun 04, 2026, 06:40 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 05, 2026, 09:29 AM UTC

   This incident has been resolved. To report additional issues or share your observations, please visit the Sonar Community (https://community.sonarsource.com/) or contact Support.

Read the full incident report →

Started May 29, 2026, 10:21 AM UTC· resolved May 29, 2026, 12:50 PM UTC

1. investigating May 29, 2026, 10:21 AM UTC

   We are experiencing an issue resulting in high scanner error rate for AutoScan C/C++ for both SonarCloud EU and US. 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. monitoring May 29, 2026, 12:26 PM UTC

   We have successfully applied a fix to the SonarCloud EU region, and AutoScan error rates for C/C++ have returned to normal. Mitigation work for the SonarCloud US region is currently underway. We are closely monitoring the progress and will provide another update as soon as the US region is fully restored.

3. resolved May 29, 2026, 12:50 PM UTC

   The mitigation has now been successfully applied to the SonarCloud US region as well. AutoScan error rates for C/C++ have returned to normal operating levels across both EU and US regions. Thank you for your patience while we worked through this.

Read the full incident report →

Started May 21, 2026, 10:27 PM UTC· resolved May 22, 2026, 08:00 AM UTC

1. investigating May 21, 2026, 10:27 PM UTC

   We are experiencing an issue authenticating Organizational Tokens using Basic Authentication, resulting in the unavailability of SonarCloud from approximately 10:50 CDT. Customers using PAT appear to be unaffected. 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. resolved May 22, 2026, 08:00 AM UTC

   The issue is now resolved. You can now authenticate your Organizational Tokens using Basic Authentication. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started May 21, 2026, 01:00 PM UTC· resolved May 21, 2026, 03:38 PM UTC

1. investigating May 21, 2026, 01:00 PM UTC

   We are experiencing an issue where we are not able to process SCIM events (user creation/deletion, group creation/deletion, and group membership changes), and potentially losing events. This does not impact logins. 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. resolved May 21, 2026, 03:38 PM UTC

   All Services are restored as of 10:10 (UTC-5). We are reprocessing the data queued during the issue, and we do not appear to have lost any events. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Apr 23, 2026, 02:43 PM UTC· resolved Apr 23, 2026, 03:19 PM UTC

1. investigating Apr 23, 2026, 02:43 PM UTC

   We are currently experiencing issues where users are unable to authenticate or log in to SonarCloud.io using GitHub Single Sign-On (SSO). Our team has identified that this is due to an ongoing incident with our third-party vendor, which is affecting authentication handshakes between our services.

2. monitoring Apr 23, 2026, 03:13 PM UTC

   The vendor has confirmed that the GitHub issue has been resolved and they are continuing to monitor to ensure stability.

3. resolved Apr 23, 2026, 03:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2026, 08:04 AM UTC· resolved Apr 23, 2026, 09:06 AM UTC

1. resolved Apr 23, 2026, 10:34 AM UTC

   Incident Period: 10:04 CEST – 11:06 CEST, April 23, 2026 Summary: Earlier today, we identified a partial outage affecting Java project scans following a recent scanner update. Users may have encountered the following error during analysis: "org.sonar.java.AnalysisException: Your project contains .java files, please provide compiled classes with sonar.java.binaries property..." Action Taken: Our engineering team identified that the latest update introduced a regression in how Java binaries are handled. To restore service, we have successfully reverted the update across all regions: EU Region: Revert completed at 11:03 CEST US Region: Revert completed at 11:06 CEST Next Steps for Customers: Standard service has been restored. If you experienced a failed scan during this window, please re-run your pipeline or analysis now. No manual configuration changes (such as adjusting sonar.java.binaries or exclusions) are required, as the system has been returned to its previous stable state. We apologize for the interruption to your workflow and are conducting a full internal review to prevent a recurrence in future updates. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Mar 19, 2026, 01:50 PM UTC· resolved Mar 19, 2026, 03:47 PM UTC

1. investigating Mar 19, 2026, 01:50 PM UTC

   We are investigating reports of some users encountering a blank screen after logging into sonarcloud.io. Please note that this issue is sporadic and may not affect all users. Our engineering team is looking into the root cause and we will provide an update as soon as more information is available. We apologize for the disruption to your workflow.

2. identified Mar 19, 2026, 03:11 PM UTC

   We have identified the cause of the issue. A fix is currently being implemented. We appreciate your patience as we restore full functionality.

3. monitoring Mar 19, 2026, 03:20 PM UTC

   The fix for the issue causing a sporadic blank screen after login has been successfully deployed to the EU region, and service is now fully restored for users in that area. We are currently in the process of applying the same fix to the US region. We expect this to be completed shortly and will provide a final update once all regions are stabilized. Thank you for your continued patience as we finalize this resolution.

4. resolved Mar 19, 2026, 03:47 PM UTC

   The issue causing a sporadic blank screen after login has now been fully resolved in both the EU and US regions. Following the successful fix in the EU, the update has been fully deployed to the US region, and all systems are now operating normally. We appreciate your patience while our teams worked to identify and resolve this across all environments.

Read the full incident report →

Started Mar 12, 2026, 02:55 PM UTC· resolved Mar 12, 2026, 04:50 PM UTC

1. investigating Mar 12, 2026, 02:55 PM UTC

   We are currently investigating an issue causing delays in Automatic Analysis results. Users may experience a delay of approximately one hour for analysis results to appear following a PR creation. We will provide another update as soon as we have more information on the recovery of the processing queue. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

2. monitoring Mar 12, 2026, 04:04 PM UTC

   Service has been stabilized and the processing queue is recovering. We are continuing to monitor the queue to ensure a full return to operational status. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

3. resolved Mar 12, 2026, 04:50 PM UTC

   Automatic analysis processing has returned to nominal levels and all backlogged results have been successfully delivered. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

Read the full incident report →

Started Mar 12, 2026, 02:09 PM UTC· resolved Mar 12, 2026, 05:39 PM UTC

1. investigating Mar 12, 2026, 02:09 PM UTC

   We have identified an issue where analyses fail for projects that have not yet been created. Workaround: To avoid analysis failures, please manually create the project in the SonarQube Cloud UI before running your analysis. 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. resolved Mar 12, 2026, 05:39 PM UTC

   The issue has been identified and remediated. Automatic project creation and analysis for new projects are now functioning as expected. We apologize for any inconvenience and thank you for your patience!

Read the full incident report →