SonarQube incident

Automatic Analysis - latency in processing messages

Minor Resolved View vendor source →

SonarQube experienced a minor incident on December 15, 2025 affecting Automatic Analysis and Automatic Analysis, lasting 5h 17m. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2025, 09:36 AM UTC
Resolved
Dec 15, 2025, 02:54 PM UTC
Duration
5h 17m
Detected by Pingoru
Dec 15, 2025, 09:36 AM UTC

Affected components

Automatic AnalysisAutomatic Analysis

Update timeline

  1. investigating Dec 15, 2025, 09:36 AM UTC

    We are experiencing an issue where automatic analysis are not being processed in a reasonable time. The issue is currently being investigated. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

  2. identified Dec 15, 2025, 10:56 AM UTC

    The issue has been fixed for SonarQube Cloud US. Remediation work is currently in progress for SonarQube Cloud EU. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

  3. monitoring Dec 15, 2025, 01:18 PM UTC

    The underlying issue affecting analysis processing on SonarQube Cloud EU has been resolved. The system is currently working through the backlog of analysis requests submitted during the incident. While processing, you may still experience increased latency. We anticipate that all latency will return to normal within the next 2 hours. Additional updates will be shared on this page as necessary. We apologize for any inconvenience. To report additional issues or share your observations, please visit the Sonar Community or contact Support.

  4. resolved Dec 15, 2025, 02:54 PM UTC

    The incident affecting analysis request processing on SonarQube Cloud EU is now fully resolved. System performance has been restored, the analysis backlog has been successfully cleared, and latency is operating at normal parameters. We appreciate your patience and apologize for any disruption this may have caused.