GitHub header

Incident with Actions

Incident Report for GitHub

Resolved

Between 16:39 and 16:57 UTC on November 5, 2026, some customers experienced failures starting workflow runs in GitHub Actions and Checks, and some in-progress runs failed. At peak, about 3% of workflow runs failed to queue, and roughly 0.21% of in-progress runs failed.

The cause was resource exhaustion in a database service that stores Actions Checks data. Bursts of highly concurrent, large read requests put the service under memory pressure, which caused it to stall and reject requests.

We mitigated the incident by failing over the affected database host. To prevent a recurrence, we have increased memory capacity across the affected database fleet. We will also be limiting concurrency of large queries to prevent heavy read traffic from causing a broad failure of critical workflows.
Posted Nov 05, 2026 - 17:42 UTC

Monitoring

The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Posted Nov 05, 2026 - 17:04 UTC

Update

Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
Posted Nov 05, 2026 - 16:52 UTC

Investigating

We are investigating reports of degraded performance for Actions
Posted Nov 05, 2026 - 16:50 UTC
This incident affected: Actions.