Live / SonarQube / Incident
SonarQube: Automatic and CI Analysis Degraded
SonarQube · sonarsource.comMinor incidentResolved2026-10-05 20:09 UTC
Public — what happened
Summary
SonarQube said it began looking into reports of slow or failed code analyses at 19:11 UTC on 2026-10-05, tied to the availability of its C# Security and Architecture Analyzer packages. The company later said the problem was confined to its US region and hit both Automatic and CI analysis. SonarQube did not name a cause, but reported putting a fix in place by 19:56 UTC, and the incident was marked resolved at 20:09.
Affected
Automatic Analysis, Automatic Analysis, CI-based Analysis, CI-based Analysis
Timeline
- Started — 2026-10-05 19:11 UTC
- Investigating — 2026-10-05 19:11 UTC (2 updates)
- Monitoring — 2026-10-05 19:56 UTC
- Resolved — 2026-10-05 20:09 UTC · 58 min after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 42, 2026, our weekly internet health report.