Is SonarQube Cloud Down?

No — SonarQube Cloud is up

Reachable from all 8 checked regions

Average response time: 661ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.sonarqube.com

SonarQube Cloud uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

648ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 51 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

51-day clean streak

Sep 13 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg

180ms

DNS 133ms TCP 1ms TLS 4ms TTFB 179ms

dfw

822ms

DNS 308ms TCP 22ms TLS 24ms TTFB 719ms

ewr

414ms

DNS 25ms TCP 2ms TLS 4ms TTFB 336ms

fra

85ms

DNS 34ms TCP 1ms TLS 3ms TTFB 84ms

gru

1062ms

DNS 231ms TCP 1ms TLS 3ms TTFB 864ms

iad

538ms

DNS 157ms TCP 81ms TLS 83ms TTFB 469ms

jnb

1384ms

DNS 231ms TCP 0ms TLS 4ms TTFB 1383ms

lax

804ms

DNS 119ms TCP 11ms TLS 14ms TTFB 655ms

What SonarQube Cloud does

SonarQube Cloud, formerly SonarCloud, is the hosted version of Sonar's static analysis. It scans pull requests and branches for bugs, vulnerabilities and maintainability problems, then reports a quality gate result back to the pull request. Teams wire it into CI so a failing gate can block a merge, which makes it a dependency of the merge path rather than an optional report.

What an outage looks like

Pull requests sit with the Sonar check pending and never resolve, so branch protection holds the merge open. CI jobs that run the scanner fail or time out uploading their results. The web interface may load stale project data or refuse sign-in. Because analysis is split into Automatic Analysis and CI-based Analysis, one path can break while the other keeps reporting.

What to do about it

Read status.sonarqube.com and find your region first: SonarQube Cloud EU and SonarQube Cloud US are separate groups with their own fourteen components. If the blocker is a check that never resolves, the practical option is an administrator override on branch protection rather than waiting. Public APIs and the IDE experience are listed apart from analysis, so a stalled scan and a broken plugin are different incidents.

Is it down for everyone, or just you?

If this page says SonarQube Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

SonarQube Cloud outage FAQ

Why did SonarCloud become SonarQube Cloud?

Sonar consolidated its product names, and sonarcloud.io now redirects to the SonarQube Cloud product page on sonarsource.com. The status page moved with it: status.sonarqube.com is the live one, while sonarcloud.statuspage.io returns a page-inactive notice. Search results and older CI configuration still say SonarCloud, and both names refer to the same hosted service.

Does a SonarQube Cloud outage block merges?

It does if branch protection requires the Sonar status check, because a check that never reports stays pending rather than failing outright. That is the most common way an analysis outage turns into a delivery outage. Repository administrators can usually merge past a pending check, and teams that treat the gate as advisory rather than required are unaffected.

Is my code at risk during an outage?

An availability incident affects analysis and reporting, not your repository, which lives with your Git host rather than with Sonar. What is lost is coverage: commits merged while the gate was unavailable were not scanned at that moment. Most teams re-run analysis on the branch afterwards so the project history does not carry a gap.

Does SonarQube Server go down when SonarQube Cloud does?

No. SonarQube Server is self-hosted in your own infrastructure, so an incident on Sonar's side does not reach it. The shared status page does carry a global group covering the support portal, documentation and payments, which touches Server customers too, but the analysis components under SonarQube Cloud EU and US apply only to the hosted service.

How we measure this

We request SonarQube Cloud's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where SonarQube Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when SonarQube Cloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required