SonarQube incident
Autoscan triggers receive no webhooks due to GitHub Outage
Resolved on October 9, 2025.
A GitHub outage caused Autoscan to receive 0% of webhook requests from Github. Any users who submitted code in their own repo would not trigger Autoscan. This also impacted customers who use CI-based analysis related to Github. CI customers who do not use Github were unaffected. GitHub has indicated recovery at 17:26 (GMT +2) and the backlog queue is processing without issue. As of 17:45 (GMT +2), we have completed processing of the backlog. Impact Start: 2025-10-09 16:30 (GMT +2) Mitigation (GitHub recovery, start of backlog processing): 2025-10-09 17:26 (GMT +2) Impact End (Full return to normal operations): 2025-10-09 17:45 (GMT +2) https://www.githubstatus.com/incidents/k7bhmjkblcwp
Update timeline
- resolved Oct 09, 2025, 03:41 PM UTC
A GitHub outage caused Autoscan to receive 0% of webhook requests from Github. Any users who submitted code in their own repo would not trigger Autoscan. This also impacted customers who use CI-based analysis related to Github. CI customers who do not use Github were unaffected. GitHub has indicated recovery at 17:26 (GMT +2) and the backlog queue is processing without issue. As of 17:45 (GMT +2), we have completed processing of the backlog. Impact Start: 2025-10-09 16:30 (GMT +2) Mitigation (GitHub recovery, start of backlog processing): 2025-10-09 17:26 (GMT +2) Impact End (Full return to normal operations): 2025-10-09 17:45 (GMT +2) https://www.githubstatus.com/incidents/k7bhmjkblcwp
Your product runs on more than SonarQube
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services