GitHub: Incident with Actions
Timeline of updates
- resolved
On May 27, 2025, between 09:31 UTC and 13:31 UTC, some Actions jobs experienced failures uploading to and downloading from the Actions Cache service. During the incident, 6% of all workflow runs couldn’t upload or download cache entries from the service, resulting in a non-blocking warning message in the logs and performance degradation. The disruption was caused by an infrastructure update related to the retirement of a legacy service, which unintentionally impacted Cache service availability. We resolved the incident by reverting the change and have since implemented a permanent fix to prevent recurrence. We are improving our configuration change processes by introducing additional end-to-end tests to cover the identified gaps, and implementing deployment pipeline improvements to reduce mitigation time for similar issues in the future.
From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2025-05-27 12:26 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Incident with Actions
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/9hzy25gws8vh
GitHub profileRecent GitHub incidentsAll outages on May 27, 2025GitHub in May 2025MarkdownJSON