SonarQube Cloud Status

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.

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

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.

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.

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.