5 Nov 17:42 UTCResolvedBetween 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.
5 Nov 17:42 UTCResolvedThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
5 Nov 17:04 UTCMonitoringThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
5 Nov 16:52 UTCUpdateSome GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
5 Nov 16:50 UTCInvestigatingWe are investigating reports of degraded performance for Actions
Around it
From the sources ChangeIntel reads; a match in time is not a cause
Up to 100 recent field edits are shown; older edits may be outside retention.
13 Nov 2026 · 04:24:47 UTCSummaryThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. → 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.
5 Nov 2026 · 17:45:01 UTCSummaryThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability. → This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
5 Nov 2026 · 17:09:22 UTCSummarySome GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation. → The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.