- Level
- confirmed
- Worst impact
- Major outage
- Components
- Actions, Pages
- Down Index
- 61of 100
What to do
Check whether you use GitHub Pages Actions, Pages. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 22m it lasted.
Anything that failed between 2026-05-26 10:57 UTC and 2026-05-26 13:18 UTC may need a replay.Subscribe to GitHub Pages's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-pages works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Pages 8
- investigating
We are investigating reports of degraded performance for Actions and Pages
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
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.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation
provider
- monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- 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. 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. 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. 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. 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-031f25d30f
Is GitHub Pages still down?
No, this incident was resolved 2026-05-26 13:18 UTC. For GitHub Pages's live state, see https://down.guide/github-pages.
How long did it last?
2h 22m, from 2026-05-26 10:57 UTC to 2026-05-26 13:18 UTC, by the times GitHub Pages posted.
What was affected?
GitHub Pages named Actions, Pages.
What caused it?
GitHub Pages hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Pages's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.