We started checking SonarCloud on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when SonarCloud reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what SonarCloud's own status page declared. Below it, any public chatter we saw about SonarCloud and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what SonarCloud's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about SonarCloud in the last 24 hours, which is not evidence that nothing is wrong.
SonarCloud's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is SonarCloud's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention SonarCloud next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
443
US-West
100.00%
340
Europe
100.00%
311
Asia-Pacific
100.00%
188
Their declared record
SonarCloud's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Oct 26, 2026, 4:55 PM UTC to Oct 26, 2026, 7:15 PM UTC (2h 20m)resolved
their latest update (Oct 26, 2026, 7:15 PM UTC): The issue affecting pull request analyses for some Bitbucket Cloud projects in SonarQube Cloud’s EU region has resolved without intervention. Affected users can retry failed analyses. We apologize for the disruption.
Quality Gates Computation DegradedMinor incident
Oct 16, 2026, 7:24 AM UTC to Oct 16, 2026, 12:27 PM UTC (5h 2m)resolved
their latest update (Oct 16, 2026, 12:27 PM UTC): Thank you for your patience while we investigated the incorrect quality gate status and measures affecting some projects. This is no longer considered an active incident. If your project is still affected, re-running the analysis will restore the correct values. Our teams are tra…
Automatic and CI Analysis DegradedMinor incident
Oct 5, 2026, 7:11 PM UTC to Oct 5, 2026, 8:09 PM UTC (58 min)resolved
their latest update (Oct 5, 2026, 8:09 PM UTC): This incident has been resolved.
Sep 24, 2026, 8:34 PM UTC to Sep 24, 2026, 11:11 PM UTC (2h 37m)resolved
their latest update (Sep 24, 2026, 11:11 PM UTC): We have deployed a fix for an issue that caused some pull request analysis results to be missing from SonarQube Cloud, even when the analysis completed successfully.
Impact Window (UTC):
EU Region: 24 Sep 13:11 – 24 Sep 22:04
US Region: 24 Sep 13:28 – 24 Sep 22:21
For pull requ…
Increased errors affecting analysis and CIPartial outage
Sep 17, 2026, 7:22 PM UTC to Sep 17, 2026, 8:08 PM UTC (46 min)resolved
their latest update (Sep 17, 2026, 8:08 PM UTC): Resolved — We have resolved an issue that caused elevated errors and slower processing for Auto Scan and CI analyses.
Processing performance has returned to normal.
We will continue to monitor the service and are completing follow-up work to prevent recurrence. We apologize for…
SQC EU: Automatic Analysis Degraded for Java ProjectsMinor incident
Sep 8, 2026, 12:13 PM UTC to Sep 8, 2026, 1:00 PM UTC (46 min)resolved
their latest update (Sep 8, 2026, 1:00 PM UTC): This incident has been resolved.
Regulatory Reports Download Issue — ResolvedAll systems operational
Sep 2, 2026, 7:35 PM UTC to Sep 2, 2026, 7:35 PM UTC (0 min)resolved
their latest update (Sep 2, 2026, 7:35 PM UTC): A limited number of customers may have experienced failures when attempting to download regulatory reports in the U.S. and Europe regions beginning at 16:43 UTC today.
The EU instance recovered at 19:00 UTC and the U.S. instance recovered at 19:30 UTC, restoring full functionali…
CI Analysis FailuresMajor outage
Sep 2, 2026, 3:42 PM UTC to Sep 2, 2026, 4:21 PM UTC (40 min)resolved
their latest update (Sep 2, 2026, 4:21 PM UTC): Resolved — Automatic Analysis Performance Degradation (Europe)
Between approximately 14:59–15:12 UTC, customers using SonarQube Cloud in Europe may have experienced failed automatic analyses due to a service issue affecting continuous integration processing. The issue has been re…
Automatic analyses are being delayedMinor incident
Sep 2, 2026, 1:36 PM UTC to Sep 2, 2026, 4:47 PM UTC (3h 11m)resolved
their latest update (Sep 2, 2026, 4:47 PM UTC): The issue has been resolved. Automatic analysis processing has returned to normal, and there is no current customer impact. We will continue to monitor the service.
Resolved- Login issues on SonarQube Cloud (US)All systems operational
Aug 28, 2026, 7:31 AM UTC to Aug 28, 2026, 7:31 AM UTC (0 min)resolved
their latest update (Aug 28, 2026, 7:31 AM UTC): Resolved — We have identified the root cause and confirmed the issue is fully resolved.
Between 05:52 and 07:05 UTC on August 28, 2026, users on sonarqube.us may have been unable to sign in using GitHub, GitLab, Bitbucket, Azure DevOps, or SAML authentication. The issue was caus…
Showing the 10 most recent of 50 incidents SonarCloud has declared in the history we hold.
These entries are SonarCloud's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
SonarCloud's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.