GitHub outage, 1 October 2026

[Retroactive] Actions workflow run failures after deployment gate approvals

Started
Resolved
1 Oct 2026, 02:00 UTC - reported afterwards
Impact
Minor

Last update from GitHub

On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already...

1 Oct 2026, 02:00 UTC

Read the full incident on the official GitHub status page

Is GitHub down now?

This page is the record of one past incident. For the live status, see Is GitHub down right now? - it reads the official status page every 2 minutes.

Other GitHub incidents

  1. [Retroactive] Actions workflow run logs delayed

  2. Incident with Actions, Pull Requests and Issues

  3. Incident with Git Operations, Issues, Actions and Pull Requests

  4. Incident with Git Operations, Pull Requests and Actions

  5. Several services are degraded

  6. Disruption with some GitHub services

  7. Incident with Actions

  8. Actions Job Delays

All recorded GitHub incidents