Skip to main content
SonarCloud

[RESOLVED] Intermittent Java Scanner Failures – April 23

Degraded Lasted 0m · started · SonarCloud's page

Level
confirmed
Worst impact
Degraded
Components
CI-based Analysis, CI-based Analysis
Regions
eu, us
Down Index
16of 100

What to do

  • Check whether you use SonarCloud CI-based Analysis, CI-based Analysis in eu, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-04-23 10:34 UTC and 2026-04-23 10:34 UTC may need a replay.
  • Subscribe to SonarCloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=sonarcloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SonarCloud 1

  1. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-6d02ed3f36

Is SonarCloud still down?

No, this incident was resolved 2026-04-23 10:34 UTC. For SonarCloud's live state, see https://down.guide/sonarcloud.

How long did it last?

0m, from 2026-04-23 10:34 UTC to 2026-04-23 10:34 UTC, by the times SonarCloud posted.

What was affected?

SonarCloud named CI-based Analysis, CI-based Analysis in eu, us.

What caused it?

SonarCloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

SonarCloud's official status page, https://status.sonarqube.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.