Minor impactResolvedDevOps

GitHub incident: Delays with Code Scanning and Billing

GitHub reported this minor-impact incident on its official status page on Jun 1, 2026, 15:17 UTC. It was resolved after 9h.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jun 1, 2026, 15:17 UTC
started
Jun 2, 2026, 00:17 UTC
resolved
9h
duration
Minor
impact
  1. resolvedJun 2, 2026, 00:17 UTC

    Starting from 13:00 UTC June 1, 2026, to 00:17 UTC June 2, 2026, multiple services experienced delayed job processing due to increased latency in our background job queue service. The root cause was insufficient queue processing capacity to handle a large week-over-week increase in total job traffic.Users saw up to 90 minutes of delay in billing usage updates, 30 minutes of delay for webhook notifications to show, and 15 minutes of delay to see email notifications. Mitigation involved scaling up our background job service capacity to handle the spike in job traffic.We have added queue capacity monitoring to our background job queue service to stay ahead of weekly growth patterns and to reduce time to detect 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 Jun 1, 2026: Delays with Code Scanning and Billing · APIStatus.watch