[2026-05-26] Incident Thread

[samus-aran]

❗ An incident has been declared:

Incident with Actions and Pages

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[tothambrus11]

Hi! All my GitHub action downloads are failing:

Error: An action could not be found at the URI 'https://codeload.github.com/hylo-lang/get-llvm/tar.gz/fb2dfe871aa20727a2e569ab27160b63e924d695' (AD50:13B9C:19E7DD:1E31FC:6A159165)
Error: Failed to download archive 'https://codeload.github.com/hylo-lang/get-llvm/tar.gz/fb2dfe871aa20727a2e569ab27160b63e924d695' after 1 attempts.

Details

Current runner version: '2.334.0'
Runner Image Provisioner
  Hosted Compute Agent
  Version: 20260213.493
  Commit: 5c115507f6dd24b8de37d8bbe0bb4509d0cc0fa3
  Build Date: 2026-02-13T00:28:41Z
  Worker ID: {cff9a20e-7fb7-4c7e-a5f4-8d3a0ca403de}
  Azure Region: westus
Operating System
  macOS
  15.7.7
  24G720
Runner Image
  Image: macos-15-arm64
  Version: 20260520.0085.1
  Included Software: https://github.com/actions/runner-images/blob/macos-15-arm64/20260520.0085/images/macos/macos-15-arm64-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-15-arm64%2F20260520.0085
GITHUB_TOKEN Permissions
  Actions: write
  ArtifactMetadata: write
  Attestations: write
  Checks: write
  CodeQuality: write
  Contents: write
  Deployments: write
  Discussions: write
  Issues: write
  Metadata: read
  Models: read
  Packages: write
  Pages: write
  PullRequests: write
  RepositoryProjects: write
  SecurityEvents: write
  Statuses: write
  VulnerabilityAlerts: read
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v4' (SHA:34e114876b0b11c390a56381ad16ebd13914f8d5)
Download action repository 'hylo-lang/get-llvm@v0.3.0' (SHA:fb2dfe871aa20727a2e569ab27160b63e924d695)
Error: An action could not be found at the URI 'https://codeload.github.com/hylo-lang/get-llvm/tar.gz/fb2dfe871aa20727a2e569ab27160b63e924d695' (AD50:13B9C:19E7DD:1E31FC:6A159165)
Error: Failed to download archive 'https://codeload.github.com/hylo-lang/get-llvm/tar.gz/fb2dfe871aa20727a2e569ab27160b63e924d695' after 1 attempts.

https://github.com/hylo-lang/Swifty-LLVM/actions/runs/26399488882/job/77860992811?pr=123

[SpenserCai]

Thanks for the update. I can now start the workflow from the UI / gh CLI, so the dispatch part seems to be partially recovered.

However, the run fails almost immediately during “Set up job” while downloading actions from codeload.github.com. In my case,two workflow_dispatch runs were created successfully, but both failed at:

Download action repository 'dtolnay/rust-toolchain@stable'

with:

An action could not be found at the URI 'https://codeload.github.com/dtolnay/rust-toolchain/tar.gz/...'
Failed to download archive ... after 1 attempts.

So the UI queue issue may be improving, but Actions still appears to have problems starting jobs / downloading action archives.

[tothambrus11]

The actions now seem to be downloading fine!

[EugeneGoroschenya]

FYI
https://github.com/orgs/community/discussions/196970?sort=new#discussioncomment-17062513
https://github.com/orgs/community/discussions/196970?sort=new#discussioncomment-17062259

[SzymonDukla]

Is anyone else experiencing existing PRs resolving to 404 once they're updated/changes are pushed?

[mig5]

Yes! I still have a PR that is 404ing, yet it appears in the Project board, and the branch still exists. It's driving me crazy because I can't make a new PR from that same branch.

The PR in question was created by the github-actions[bot] account, and I'm guessing that's the same for you too.

I raised a support ticket a day or two ago, but there's been no reply.

[mig5]

Other PRs that were created by that user, magically re-appeared once the Actions incident was 'resolved', but not one that had changes pushed to it during the outage.