Is SonarQube down?

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.

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

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.

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.

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.

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.

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.

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.

We are continuing to monitor for any further issues.

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.

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.

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.

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.

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.

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.

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.

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

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.