Live  /  Providers  /  SonarQube

SonarQube

sonarsource.comNo open incidents

Independent assessment — SquidGrid is not affiliated with SonarQube. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks SonarQube’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what SonarQube is reporting

Current & recent incidents

Resolved

Quality Gates Computation Degraded

Minor impact · 2026-10-16 12:27 UTC · source

Resolved

Automatic and CI Analysis Degraded

Minor impact · 2026-10-05 20:09 UTC · source

Resolved

Investigating missing pull request results

Major impact · 2026-09-24 23:11 UTC · source

Resolved

Increased errors affecting analysis and CI

Major impact · 2026-09-17 19:22 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 5 incidents from SonarQube’s own status page since 2026-09-17.

Recent incidents in the archive

Computed by SquidGrid from the incidents SonarQube published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what SonarQube has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

SonarQube runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of SonarQube is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with SonarQube.