{"slug": "incident-with-actions-and-pages", "title": "Incident with Actions and Pages", "summary": "GitHub experienced a two-hour service degradation on May 26, 2026, after its automated account review system incorrectly suspended the service account used by GitHub Actions, causing all newly queued workflow runs to fail and impacting GitHub Pages, Copilot Code Review, and other dependent services. The company restored the account at 12:16 UTC and fully recovered by 12:56 UTC, though the incident also caused a small number of Issues, PRs, and Discussions to be incorrectly hidden. GitHub has added an allowlist for service accounts and improved diagnostic tooling to prevent a recurrence.", "body_md": "May `26`, `13:18` UTC\n\n**Resolved** - 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.\n\nThis was caused by our automated account review system incorrectly suspending the service account used by GitHub Actions to authenticate workflow runs and download actions.\n\nWe 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.\n\nDuring 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.\n\nTo 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.\n\nMay `26`, `13:01` UTC\n\n**Update** - The degradation has been mitigated. We are monitoring to ensure stability.\n\nMay `26`, `13:00` UTC\n\n**Monitoring** - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.\n\nMay `26`, `12:37` UTC\n\n**Update** - We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation\n\nMay `26`, `12:17` UTC\n\n**Update** - Actions is experiencing degraded performance. We are continuing to investigate.\n\nMay `26`, `11:53` UTC\n\n**Update** - 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.\n\nMay `26`, `11:19` UTC\n\n**Update** - Actions is experiencing degraded availability. We are continuing to investigate.\n\nMay `26`, `10:57` UTC\n\n**Investigating** - We are investigating reports of degraded performance for Actions and Pages", "url": "https://wpnews.pro/news/incident-with-actions-and-pages", "canonical_source": "https://www.githubstatus.com/incidents/gnftqj9htp0g", "published_at": "2026-05-26 13:18:48+00:00", "updated_at": "2026-05-29 22:51:22.295656+00:00", "lang": "en", "topics": ["ai-infrastructure"], "entities": ["GitHub Actions", "GitHub Pages", "Copilot", "Octoshift", "GitHub Enterprise Importer"], "alternates": {"html": "https://wpnews.pro/news/incident-with-actions-and-pages", "markdown": "https://wpnews.pro/news/incident-with-actions-and-pages.md", "text": "https://wpnews.pro/news/incident-with-actions-and-pages.txt", "jsonld": "https://wpnews.pro/news/incident-with-actions-and-pages.jsonld"}}