Skip to main content

Is SonarQube Cloud Down?

No — SonarQube Cloud is up

Reachable from all 8 checked regions

Average response time: 631ms

Last checked · checks run every 6 hours

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

SonarQube Cloud uptime

—
Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days

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

30-day history

Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: 100.00% uptime, 16 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: no data
Jul 26 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.

jnb
775ms
DNS 0ms TCP 0ms TLS 7ms TTFB 603ms
lax
704ms
DNS 0ms TCP 2ms TLS 5ms TTFB 542ms
lhr
133ms
DNS 1ms TCP 3ms TLS 8ms TTFB 123ms
nrt
949ms
DNS 0ms TCP 2ms TLS 6ms TTFB 725ms
ord
379ms
DNS 0ms TCP 91ms TLS 93ms TTFB 359ms
sin
665ms
DNS 0ms TCP 1ms TLS 4ms TTFB 510ms
sjc
698ms
DNS 41ms TCP 2ms TLS 6ms TTFB 548ms
syd
1035ms
DNS 0ms TCP 1ms TLS 3ms TTFB 788ms
yyz
489ms
DNS 0ms TCP 11ms TLS 14ms TTFB 397ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
GitLab
GitLab
S
Snyk
J
Jenkins

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 — 8 of them answered the most recent check.
  • 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required