- Level
- confirmed
- Worst impact
- Degraded
- Components
- Third-Party Outages
- Regions
- us, us-east-1
What to do
Check whether you use SonarCloud Third-Party Outages in us, us-east-1. 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 17h 39m it lasted.
Anything that failed between 2025-10-20 15:06 UTC and 2025-10-21 08:45 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 6
- investigating
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.
provider
- identified
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.
provider
- monitoring
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.
provider
- monitoring
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.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
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.
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-6616bdc4b4
Is SonarCloud still down?
No, this incident was resolved 2025-10-21 08:45 UTC. For SonarCloud's live state, see https://down.guide/sonarcloud.
How long did it last?
17h 39m, from 2025-10-20 15:06 UTC to 2025-10-21 08:45 UTC, by the times SonarCloud posted.
What was affected?
SonarCloud named Third-Party Outages in us, us-east-1.
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.