Vendor reports: operationalResolved · vendor status “resolved”Official status API

Disruption with SonarQube Cloud

Reported by SonarQube Cloud · Developer Tools & CI/CD · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Jul 16, 2026, 08:46 UTC
Vendor's clock
Resolved
Jul 16, 2026, 13:04 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
4 h 18 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • SonarQube Cloud reports operational: "Disruption with SonarQube Cloud".[E1, E2]
  • The vendor marked it resolved at 2026-07-16 13:04 UTC.[E3, E7]

Affected products and regions

  • Components: Authentication and User Management, Authentication and User Management, Automatic Analysis, Automatic Analysis, Billing and Subscription, AI CodeFix, Billing and Subscription, CI-based Analysis, CI-based Analysis, Advanced Security - Software Composition Analysis, Notifications, Notifications, Public APIs, Public APIs, Pull Request Experience, Pull Request Experience, SonarQube IDE Experience, SonarQube IDE Experience, Website, Website, Integrations, Integrations, Advanced Security - Software Composition Analysis, Advanced Security - Software Composition Analysis, Third-Party Outages, Third-Party Outages, Architecture, Architecture.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:11 UTC · summary s1, evidence 3164816e605c8fdd

Evidence (8)
  1. E1SonarQube Cloud reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Disruption with SonarQube Cloud". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-07-16 08:46 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Authentication and User Management, Authentication and User Management, Automatic Analysis, Automatic Analysis, Billing and Subscription, AI CodeFix, Billing and Subscription, CI-based Analysis, CI-based Analysis, Advanced Security - Software Composition Analysis, Notifications, Notifications, Public APIs, Public APIs, Pull Request Experience, Pull Request Experience, SonarQube IDE Experience, SonarQube IDE Experience, Website, Website, Integrations, Integrations, Advanced Security - Software Composition Analysis, Advanced Security - Software Composition Analysis, Third-Party Outages, Third-Party Outages, Architecture, Architecture. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-07-16 13:04 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: Authentication and User Management, Authentication and User Management, Automatic Analysis, Automatic Analysis, Billing and Subscription, AI CodeFix, Billing and Subscription, CI-based Analysis, CI-based Analysis, Advanced Security - Software Composition Analysis, Notifications, Notifications, Public APIs, Public APIs, Pull Request Experience, Pull Request Experience, SonarQube IDE Experience, SonarQube IDE Experience, Website, Website, Integrations, Integrations, Advanced Security - Software Composition Analysis, Advanced Security - Software Composition Analysis, Third-Party Outages, Third-Party Outages, Architecture, Architecture

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

SonarQube Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 16, 2026, 08:46 UTCVendor-reported startVendor time
  2. Jul 16, 2026, 13:04 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall