Major impactResolvedDevOps

GitHub outage: Incident with Actions, we are investigating reports of degraded availability

GitHub reported this major-impact incident on its official status page on May 6, 2026, 07:19 UTC. It was resolved after 2h 25m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
May 6, 2026, 07:19 UTC
started
May 6, 2026, 09:44 UTC
resolved
2h 25m
duration
Major
impact
  1. resolvedMay 6, 2026, 09:44 UTC

    On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed.This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover.We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.

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 outage on May 6, 2026: Incident with Actions, we are investigating reports of degraded availability · APIStatus.watch