Disruption with actions hosted runners
An incident affecting GitHub Copilot, recorded by is-down.ai.
- Status
- Resolved
- Verdict
- Degraded
- Detection
- Provider confirmed
- Official signal
- Degraded
- Affected component
- Actions
- Started
- Jul 22, 2026 20:43 UTC
- Last update
- Jul 24, 2026 23:09 UTC · updated 4 days ago
- Resolved
- Jul 22, 2026 22:09 UTC
- Duration
- 1 hour
- Provider updates
- 5
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 impa
View the official status report
See the current GitHub Copilot status and full uptime history