Autoscan triggers receive no webhooks due to GitHub Outage

What to do

• Check whether your product depends on SonarCloud. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2025-10-09 14:30 UTC and 2025-10-09 14:30 UTC may need a replay.

• Subscribe to SonarCloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=sonarcloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SonarCloud 1

1. resolvedOct 9, 2025, 2:30 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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.