CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Actions
Timeline of updates
- resolved
On April 9, 2024, between 18:00 and 20:17 UTC, Actions was degraded and had failures for new and existing customers. During this time, Actions failed to start for 5,426 new repositories, and 1% of runs for existing customers were delayed, with half of those failing due to an infrastructure error. The root cause was an expired certificate which caused authentication to fail between internal services. The incident was mitigated once the cert was rotated. We are working to improve our automation to ensure certs are rotated before expiration.
From GitHub Copilot’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 Copilot, started 2024-04-09 18:36 UTC, resolved after 1.7 h, 1 update(s).
- Title
- Incident with Actions
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/xcjgp37zx5dt
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on April 9, 2024GitHub Copilot in April 2024MarkdownJSON