- Detected by Pingoru
- May 29, 2026, 10:21 AM UTC
- Resolved
- May 29, 2026, 12:50 PM UTC
- Duration
- 2h 29m
Affected: Automatic AnalysisAutomatic Analysis
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 21, 2026, 10:27 PM UTC
- Resolved
- May 22, 2026, 08:00 AM UTC
- Duration
- 9h 33m
Affected: Authentication and User ManagementAuthentication and User Management
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- May 21, 2026, 01:00 PM UTC
- Resolved
- May 21, 2026, 03:38 PM UTC
- Duration
- 2h 37m
Affected: Authentication and User ManagementAuthentication and User Management
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Apr 23, 2026, 02:43 PM UTC
- Resolved
- Apr 23, 2026, 03:19 PM UTC
- Duration
- 35m
Affected: Authentication and User ManagementAuthentication and User Management
Timeline · 3 updates
-
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.
-
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.
-
resolved Apr 23, 2026, 03:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 10:34 AM UTC
- Resolved
- Apr 23, 2026, 10:34 AM UTC
- Duration
- —
Affected: CI-based AnalysisCI-based Analysis
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 01:50 PM UTC
- Resolved
- Mar 19, 2026, 03:47 PM UTC
- Duration
- 1h 56m
Affected: WebsiteWebsite
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Mar 12, 2026, 02:55 PM UTC
- Resolved
- Mar 12, 2026, 04:50 PM UTC
- Duration
- 1h 54m
Affected: Automatic Analysis
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Mar 12, 2026, 02:09 PM UTC
- Resolved
- Mar 12, 2026, 05:39 PM UTC
- Duration
- 3h 29m
Affected: CI-based Analysis
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Mar 11, 2026, 03:06 PM UTC
- Resolved
- Mar 11, 2026, 04:18 PM UTC
- Duration
- 1h 12m
Affected: Authentication and User ManagementAutomatic Analysis
Timeline · 2 updates
-
investigating Mar 11, 2026, 03:06 PM UTC
We are currently experiencing delays with Automatic Analysis and intermittent login failures due to an ongoing service disruption with a third-party vendor. Current Status: While the root cause is an upstream outage affecting API requests and webhooks, our engineering team is proactively investigating potential internal solutions we can deliver to mitigate the impact while the vendor's issue is still ongoing. Impact: Automatic Analysis: Extended processing times. Authentication: Intermittent failures when logging in via the affected provider. We are monitoring the situation closely and will provide an update as soon as more information or a mitigation becomes available.
-
resolved Mar 11, 2026, 04:18 PM UTC
The third-party vendor has resolved their service disruption. Our team has confirmed that Automatic Analysis and Login services are now functioning normally. Thank you for your patience!
Read the full incident report →
Critical February 13, 2026 - Detected by Pingoru
- Feb 13, 2026, 02:00 PM UTC
- Resolved
- Feb 13, 2026, 03:05 PM UTC
- Duration
- 1h 5m
Affected: Automatic AnalysisPull Request Experience
Timeline · 3 updates
-
investigating Feb 13, 2026, 02:00 PM UTC
We are currently experiencing a major service interruption affecting Automatic Analysis in our EU Instance. The US regions are operating normally. Our team is actively investigating the EU issue to restore service. We will provide an update as soon as we have a recovery timeline.
-
monitoring Feb 13, 2026, 02:39 PM UTC
We have implemented a fix for the issues affecting our EU Instance. We can confirm that Automated Analysis is now working correctly, and requests are processing as expected. We also recognize that the Pull Request experience was impacted by these failures; this should no longer be affected, and PR statuses should update normally moving forward. We are continuing to monitor the service closely to ensure full stability.
-
resolved Feb 13, 2026, 03:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 04:37 PM UTC
- Resolved
- Feb 02, 2026, 07:00 PM UTC
- Duration
- 2h 22m
Affected: CI-based AnalysisCI-based AnalysisPull Request ExperiencePull Request Experience
Timeline · 2 updates
-
identified Feb 02, 2026, 04:37 PM UTC
We are experiencing an issue resulting in JaCoCo coverage being reporting as zero. This could result in Quality Gates failing in error. The issue has been identified and is being addressed. After the issue is fixed, new analysis will be required to correct the Quality Gates. 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.
-
resolved Feb 02, 2026, 07:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 01:00 PM UTC
- Resolved
- Jan 29, 2026, 06:21 PM UTC
- Duration
- 5h 20m
Affected: WebsiteWebsite
Timeline · 2 updates
-
investigating Jan 29, 2026, 01:00 PM UTC
We are experiencing a problem where users are not able to view the issues within the issues page of an organization. The problem is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional problems or share your observations, please visit the Sonar Community or contact Support.
-
resolved Jan 29, 2026, 06:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 04:25 PM UTC
- Resolved
- Jan 28, 2026, 04:29 PM UTC
- Duration
- 3m
Affected: Authentication and User Management
Timeline · 2 updates
-
investigating Jan 28, 2026, 04:25 PM UTC
We are currently investigating an issue impacting users who are trying to log in to sonarcloud.io using Bitbucket. 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.
-
resolved Jan 28, 2026, 04:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 02:11 PM UTC
- Resolved
- Jan 28, 2026, 05:49 PM UTC
- Duration
- 3h 37m
Affected: Automatic Analysis
Timeline · 3 updates
-
investigating Jan 28, 2026, 02:11 PM UTC
We are experiencing an issue causing delays in Autoscan analyses in the SonarQube EU instance. 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.
-
monitoring Jan 28, 2026, 03:20 PM UTC
We are still investigating the root cause, but we have implemented temporary measures to mitigate the issue, and we are currently not seeing any delays in Autoscan analyses. 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.
-
resolved Jan 28, 2026, 05:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 01:25 PM UTC
- Resolved
- Jan 26, 2026, 03:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 26, 2026, 01:25 PM UTC
We experienced a service disruption to Automatic Analysis on SonarQube Cloud (EU) between 11:30 and 12:15 CET today. During this window, 70% of tasks submitted to Automatic Analysis failed to complete successfully. We have implemented a fix and all systems are operational as of 12:15 CET. If your analysis failed during the impact window, please manually re-trigger or resubmit the affected analyses. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 04:44 PM UTC
- Resolved
- Jan 21, 2026, 06:58 PM UTC
- Duration
- 2h 13m
Affected: Automatic AnalysisAutomatic AnalysisCI-based AnalysisCI-based Analysis
Timeline · 2 updates
-
identified Jan 21, 2026, 04:44 PM UTC
Code Coverage calculation for Go is currently not working. We have identified the issue and are actively working on the fix. 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.
-
resolved Jan 21, 2026, 06:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2026, 02:15 PM UTC
- Resolved
- Jan 07, 2026, 02:47 PM UTC
- Duration
- 31m
Affected: CI-based AnalysisCI-based Analysis
Timeline · 2 updates
-
investigating Jan 07, 2026, 02:15 PM UTC
Analysis fails with Sonar Scanner for NPM version 4.3.3. We are actively working on the fix. The workaround is to explicitly invoke version 4.3.2. 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.
-
resolved Jan 07, 2026, 02:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 01:38 PM UTC
- Resolved
- Dec 17, 2025, 01:53 PM UTC
- Duration
- 15m
Affected: Automatic Analysis
Timeline · 2 updates
-
identified Dec 17, 2025, 01:38 PM UTC
We are currently investigating an issue where some Autoscan analyses are failing due to authentication errors. Our team has identified the root cause and is currently working on a resolution. 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.
-
resolved Dec 17, 2025, 01:53 PM UTC
Our engineering team has successfully redeployed and refreshed all Autoscan workers across all environments. All services are now operating normally, and failed analyses are being re-processed. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 09:36 AM UTC
- Resolved
- Dec 15, 2025, 02:54 PM UTC
- Duration
- 5h 17m
Affected: Automatic AnalysisAutomatic Analysis
Timeline · 4 updates
-
investigating Dec 15, 2025, 09:36 AM UTC
We are experiencing an issue where automatic analysis are not being processed in a reasonable time. 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.
-
identified Dec 15, 2025, 10:56 AM UTC
The issue has been fixed for SonarQube Cloud US. Remediation work is currently in progress for SonarQube Cloud EU. 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.
-
monitoring Dec 15, 2025, 01:18 PM UTC
The underlying issue affecting analysis processing on SonarQube Cloud EU has been resolved. The system is currently working through the backlog of analysis requests submitted during the incident. While processing, you may still experience increased latency. We anticipate that all latency will return to normal within the next 2 hours. 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.
-
resolved Dec 15, 2025, 02:54 PM UTC
The incident affecting analysis request processing on SonarQube Cloud EU is now fully resolved. System performance has been restored, the analysis backlog has been successfully cleared, and latency is operating at normal parameters. We appreciate your patience and apologize for any disruption this may have caused.
Read the full incident report →
- Detected by Pingoru
- Oct 30, 2025, 03:49 PM UTC
- Resolved
- Oct 30, 2025, 03:49 PM UTC
- Duration
- —
Affected: Automatic AnalysisAutomatic AnalysisCI-based AnalysisCI-based Analysis
Timeline · 1 update
-
resolved Oct 30, 2025, 03:49 PM UTC
During a deployment a downtime of 5 minutes occurred on both EU and US instances causing failed analysis, quality gates related operations during EU Instance (12:55-13:00 CEST) and US Instance (13:15-13:26 CEST) on Oct 30, 2025. Analyses that failed during this period will need to be resubmitted. 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 →
- Detected by Pingoru
- Oct 22, 2025, 03:03 PM UTC
- Resolved
- Oct 23, 2025, 12:07 PM UTC
- Duration
- 21h 4m
Affected: Automatic AnalysisCI-based Analysis
Timeline · 5 updates
-
investigating Oct 22, 2025, 03:03 PM UTC
We are experiencing an issue with the Report processor that causes Analysis to fail intermittently. 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.
-
monitoring Oct 22, 2025, 07:49 PM UTC
We have implemented mitigation steps and are no longer observing any new analysis failures. Our team is still investigating and working to resolve residual slowness affecting some users. Action Required: Please resubmit any analysis that failed during the incident window. We apologize for the inconvenience.
-
identified Oct 23, 2025, 08:26 AM UTC
We're observing increased latency across the service. Our team is actively investigating the cause and working to mitigate the impact. Additional updates will be shared on this page as necessary. We apologize for any inconvenience.
-
monitoring Oct 23, 2025, 09:18 AM UTC
The analyses no longer display the increased latency previously observed. Our team will continue to monitor the service. 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.
-
resolved Oct 23, 2025, 12:07 PM UTC
A fix has been successfully deployed, and the incident is now considered resolved. Thank you for your patience during this time. To report additional issues or share your observations, please visit the Sonar Community or contact Support.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 03:06 PM UTC
- Resolved
- Oct 21, 2025, 08:45 AM UTC
- Duration
- 17h 39m
Affected: Third-Party Outages
Timeline · 6 updates
-
investigating Oct 20, 2025, 03:06 PM UTC
We are continuing to experience issues with AWS infrastructure in the US-EAST-1 Region due to which Analysis is not processing since 2 pm UTC. We are monitoring the situation closely and are awaiting updates from our provider. You can track the status of the underlying infrastructure directly on the AWS Health Dashboard: https://health.aws.amazon.com/health/status We apologize for the inconvenience and will provide our next update as soon as we receive new information from AWS.
-
identified Oct 20, 2025, 06:28 PM UTC
Our cloud provider, AWS, has identified the root cause and is actively working on a mitigation. We are closely monitoring their progress and will share another update as soon as we have more definitive information. We apologize for the inconvenience and thank you for your patience. We will provide our next update as soon as we receive new details from AWS.
-
monitoring Oct 20, 2025, 07:50 PM UTC
AWS is observing continued recovery across most of the affected services in the US-EAST-1 Region. We are also seeing recovery across our platform and is currently working through the remaining backlog, which we are closely monitoring. Action Required: Any Analysis that failed during the outage will need to be resubmitted. We apologize for the inconvenience and thank you for your patience.
-
monitoring Oct 20, 2025, 09:22 PM UTC
AWS is reporting continued recovery across the majority of impacted services in the US-EAST-1 Region. We are also seeing widespread recovery across our platform. While analysis has resumed, processing speed is slower than normal as systems stabilize. We are closely monitoring the situation and taking all necessary steps to restore full performance. We sincerely apologize for the disruption and appreciate your continued patience.
-
monitoring Oct 20, 2025, 09:31 PM UTC
We are continuing to monitor for any further issues.
-
resolved Oct 21, 2025, 08:45 AM UTC
The outage is fully resolved, and all systems are now completely operational. The AWS incident that impacted the US-EAST-1 region between 11:49 PM PDT on October 19 and 3:01 PM PDT on October 20 is officially closed. All SonarQube Cloud services are functioning normally. Please ensure that any analysis that failed during the disruption is resubmitted. We greatly appreciate your patience during this period of recovery.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:30 AM UTC
- Resolved
- Oct 20, 2025, 10:41 AM UTC
- Duration
- 3h 11m
Affected: Third-Party OutagesThird-Party Outages
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Oct 17, 2025, 07:35 AM UTC
- Resolved
- Oct 17, 2025, 08:28 AM UTC
- Duration
- 53m
Affected: Authentication and User ManagementAuthentication and User Management
Timeline · 3 updates
-
investigating Oct 17, 2025, 07:35 AM UTC
We are experiencing an issue impacting some SonarQube Cloud users attempting to log in via Single Sign-On (SSO). 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.
-
identified Oct 17, 2025, 08:09 AM UTC
We have successfully implemented the fix, and the issue is now resolved for users in the EU region. We are currently working on a fix for the US instance.
-
resolved Oct 17, 2025, 08:28 AM UTC
We have successfully implemented the solution and confirmed service restoration. Thank you for your patience while our team worked diligently to resolve this incident.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 02:30 PM UTC
- Resolved
- Oct 09, 2025, 02:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 09, 2025, 03:41 PM UTC
A GitHub outage caused Autoscan to receive 0% of webhook requests from Github. Any users who submitted code in their own repo would not trigger Autoscan. This also impacted customers who use CI-based analysis related to Github. CI customers who do not use Github were unaffected. GitHub has indicated recovery at 17:26 (GMT +2) and the backlog queue is processing without issue. As of 17:45 (GMT +2), we have completed processing of the backlog. Impact Start: 2025-10-09 16:30 (GMT +2) Mitigation (GitHub recovery, start of backlog processing): 2025-10-09 17:26 (GMT +2) Impact End (Full return to normal operations): 2025-10-09 17:45 (GMT +2) https://www.githubstatus.com/incidents/k7bhmjkblcwp
Read the full incident report →
