SonarQube Outage History

SonarCloud experienced high scanner error rates for AutoScan C/C++ across both EU and US regions for 2.5 hours. The issue affected automated code scanning functionality for C/C++ projects, preventing successful analysis completion. The team applied fixes sequentially, first restoring the EU region and then the US region, bringing error rates back to normal operating levels.

SonarQube experienced authentication failures for Organizational Tokens using Basic Authentication, making SonarCloud unavailable for affected users while customers using Personal Access Tokens (PAT) remained unaffected. The authentication issue lasted 9.6 hours before being fully resolved, restoring normal access to SonarCloud services.

SonarQube experienced a major incident where SCIM events for user and group management (creation, deletion, and membership changes) could not be processed, with potential event loss. The issue lasted 4 minutes and did not affect user logins. The incident was resolved after investigation.

SonarQube experienced a 36-minute outage where users were unable to authenticate or log in to SonarCloud.io using GitHub Single Sign-On (SSO). The issue was caused by an incident with a third-party vendor that disrupted authentication handshakes between services. The vendor resolved the GitHub authentication issue and the incident was fully resolved after continued monitoring.

SonarQube Cloud (EU) experienced performance issues with slow loading times on the Issues page, affecting the web interface. The engineering team investigated and resolved the latency problem within 32 minutes.

SonarQube Cloud experienced intermittent login issues where some users encountered a blank screen after logging into sonarcloud.io, affecting the web interface sporadically across EU and US regions. The incident lasted 2 hours, with the engineering team identifying the root cause and deploying a fix first to the EU region, then to the US region. All systems were restored to normal operation once the fix was fully deployed across both regions.

SonarQube Cloud EU experienced a major incident causing delays in Automatic Analysis processing, with users experiencing approximately one-hour delays for analysis results to appear after PR creation. The service was stabilized after 2 hours, with the processing queue recovering and all backlogged results successfully delivered.

SonarQube Cloud EU experienced a major incident where analysis failures occurred for new projects that had not yet been created, preventing automatic project creation during analysis. Users could work around the issue by manually creating projects in the SonarQube Cloud UI before running their analysis. The issue was resolved after 3.5 hours, restoring automatic project creation and analysis functionality for new projects.

SonarQube Cloud EU experienced a 1.2-hour service disruption caused by a third-party vendor outage, resulting in extended processing times for Automatic Analysis and intermittent login failures. The incident was resolved when the third-party vendor restored their services, returning both Automatic Analysis and authentication to normal operation.