CompaniesGitHub CopilotIncidents
GitHub Copilot: Disruption with actions hosted runners
Timeline of updates
- resolved
On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start. At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
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 2026-07-22 20:43 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Disruption with actions hosted runners
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/20frdtvv3yg6
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on July 22, 2026GitHub Copilot in July 2026MarkdownJSON