Live  /  SonarQube  /  Incident

SonarQube: Quality Gates Computation Degraded

SonarQube · sonarsource.comMinor incidentResolved2026-10-16 12:27 UTC
Public — what happened

Summary

SonarQube said that starting at 07:24 UTC on 2026-10-16, some projects had trouble with measure computation, which could lead to an incorrect quality gate status. About an hour later it reported that its database and index integrity checks had found no discrepancies, and that it was turning to the logic that computes measures live to look for the root cause. The incident, which the company rated minor, was marked resolved at 12:27 UTC, and the text provided does not name a final cause.

Affected

CI-based Analysis, CI-based Analysis, Pull Request Experience, Pull Request Experience

As listed on SonarQube’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach SonarQube against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for SonarQube: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the SonarQube report →

More from SonarQube

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the SonarQube status & history page.

Related: SonarQube status & history. SquidGrid is not affiliated with SonarQube.