Skip to main content

GitHub outage on October 1, 2026: [Retroactive] Actions workflow run failures after deployment gate approvals

GitHub reported an incident affecting GitHub for 1 minute on 1 October 2026, from 02:00 to 02:00 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started
02:00
1 Oct 2026 UTC
Resolved
02:00
1 Oct 2026 UTC
Duration
<1m
1 minute
Impact
Minor
as rated by GitHub
Updates
1
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

[Retroactive] Actions workflow run failures after deployment gate approvals

Resolved Minor impact 1 Oct 2026 02:00 UTC View on GitHub's status page
  1. Official
    Resolved

    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 completed to avoid repeating changes.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.