Minor impactResolvedDevOps

GitHub incident: Incident with CodeQL, Webhooks, Notifications, and Slack Integration

GitHub reported this minor-impact incident on its official status page on May 12, 2026, 14:38 UTC. It was resolved after 3h 5m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 12, 2026, 14:38 UTC
started
May 12, 2026, 17:43 UTC
resolved
3h 5m
duration
Minor
impact
  1. resolvedMay 12, 2026, 17:43 UTC

    On May 12, 2026, between 13:41 and 17:43 UTC, some services experienced delays in processing. For the Code Scanning service, 53% of check runs took over 15 minutes to complete. Additionally, notifications took an average of 22 minutes to be delivered and Slack integration webhooks took an average of 20 minutes to be delivered. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker capacity for our high rate of job enqueues. We mitigated the impact by scaling our processing workers to handle the increased load. All services returned to normal processing times after the mitigation was applied. We are working to create dedicated worker pools for some of our high usage shared queues to help prevent this in the future.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on May 12, 2026: Incident with CodeQL, Webhooks, Notifications, and Slack Integration · APIStatus.watch