SonarQube incident

[RESOLVED] Intermittent Java Scanner Failures – April 23

Notice Resolved View vendor source →

SonarQube experienced a notice incident on April 23, 2026 affecting CI-based Analysis and CI-based Analysis, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 23, 2026, 10:34 AM UTC
Resolved
Apr 23, 2026, 10:34 AM UTC
Duration
Detected by Pingoru
Apr 23, 2026, 10:34 AM UTC

Affected components

CI-based AnalysisCI-based Analysis

Update timeline

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

    Status: Resolved 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.