GitHub reported this critical-impact incident on its official status page on Jul 25, 2026, 12:31 UTC. It was resolved after 42 min.
Right now GitHub is operational. Live GitHub status →
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8
We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried.
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure.
We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality.
We are investigating reports of degraded availability for Actions
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.
Overlapping incidents aren't necessarily related.
GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history