Incident with Actions and Pages

Summary

Incident with Actions and Pages

On May 26, 2026, between 10:40 UTC and 12:56 UTC, GitHub Actions jobs were degraded. From 10:40 to 12:16 UTC, all newly queued Actions runs failed to start. From 12:16 to 12:56 UTC, Actions runs that required downloading actions for their workflows continued to fail. GitHub Pages, Copilot Code Review, Copilot coding agent, Octoshift, and GitHub Enterprise Importer were also impacted due to their dependency on Actions. <br /><br />This was caused by our automated account review system incorrectly suspending the service account used by GitHub Actions to authenticate workflow runs and download actions. <br /><br />We mitigated by restoring the account at 12:16 UTC, marking it exempt from further automated review at 12:20 UTC, and redeploying a related service at 12:48 UTC to flush cached account state. Full recovery was confirmed at 12:56 UTC. <br /><br />During this incident, a small number of Issues, PRs, Comments, and Discussions were marked as hidden when the service account was disabled. No data was lost. All content hidden because of this incident has been restored and full search index restoration is in progress. <br /><br />To prevent a recurrence, we have added an allowlist of all service accounts that cannot be suspended by automated systems, and ensuring these protections are enforced consistently across all account management tooling. We are also improving diagnostic tooling for accounts and reducing cache propagation delays to shorten time to mitigate similar incidents in the future.

• Started

  May 26, 2026 · 10:57 AM

• Resolved

  May 26, 2026 · 1:18 PM

• Duration

  2h 21m

• Severity

  Critical

• ◐

  Investigating

  May 26 · 10:57 AM GitHub

  We are investigating reports of degraded performance for Actions and Pages

• ◐

  Investigating

  May 26 · 11:19 AM GitHub

  Actions is experiencing degraded availability. We are continuing to investigate.

• ◐

  Investigating

  May 26 · 11:53 AM GitHub

  We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

• ◐

  Investigating

  May 26 · 12:17 PM GitHub

  Actions is experiencing degraded performance. We are continuing to investigate.

• ◐

  Investigating

  May 26 · 12:37 PM GitHub

  We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation

• ◉

  Monitoring

  May 26 · 1:00 PM GitHub

  The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

• ◉

  Monitoring

  May 26 · 1:01 PM GitHub

  The degradation has been mitigated. We are monitoring to ensure stability.

• ✓

  Resolved

  May 26 · 1:18 PM GitHub

  On May 26, 2026, between 10:40 UTC and 12:56 UTC, GitHub Actions jobs were degraded. From 10:40 to 12:16 UTC, all newly queued Actions runs failed to start. From 12:16 to 12:56 UTC, Actions runs that required downloading actions for their workflows continued to fail. GitHub Pages, Copilot Code Review, Copilot coding agent, Octoshift, and GitHub Enterprise Importer were also impacted due to their dependency on Actions. <br /><br />This was caused by our automated account review system incorrectly suspending the service account used by GitHub Actions to authenticate workflow runs and download actions. <br /><br />We mitigated by restoring the account at 12:16 UTC, marking it exempt from further automated review at 12:20 UTC, and redeploying a related service at 12:48 UTC to flush cached account state. Full recovery was confirmed at 12:56 UTC. <br /><br />During this incident, a small number of Issues, PRs, Comments, and Discussions were marked as hidden when the service account was disabled. No data was lost. All content hidden because of this incident has been restored and full search index restoration is in progress. <br /><br />To prevent a recurrence, we have added an allowlist of all service accounts that cannot be suspended by automated systems, and ensuring these protections are enforced consistently across all account management tooling. We are also improving diagnostic tooling for accounts and reducing cache propagation delays to shorten time to mitigate similar incidents in the future.