- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, us
What to do
Check whether you use SonarCloud 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-07-01 10:06 UTC and 2026-07-01 08:30 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
- resolved
We experienced an issue resulting in some failures with AutoScan and CI Analysis between 08:34 UTC and 09:35 UTC. During this period a subset of customers analyses using the Scanner for .NET and who also had no local cache for the static dependency of the analyzer saw some failures in their AutoScan and CI Analyses. The issue has been remediated. 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-c056160ba0
Is SonarCloud still down?
No, this incident was resolved 2026-07-01 08:30 UTC. For SonarCloud's live state, see https://down.guide/sonarcloud.
How long did it last?
0m, from 2026-07-01 10:06 UTC to 2026-07-01 08:30 UTC, by the times SonarCloud posted.
What was affected?
SonarCloud named 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.