Jul 22, 22:09 UTC
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. Jul 22, 22:01 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Jul 22, 22:01 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Jul 22, 20:47 UTC
Update - Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation. Jul 22, 20:43 UTC
Investigating - We are investigating reports of degraded performance for Actions
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.
Posted Jul 22, 2026 - 22:09 UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Posted Jul 22, 2026 - 22:01 UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Posted Jul 22, 2026 - 22:01 UTC
Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.
Posted Jul 22, 2026 - 20:47 UTC
We are investigating reports of degraded performance for Actions
Posted Jul 22, 2026 - 20:43 UTC
This incident affected: Actions.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Incident with Actions | 0 | 12.56 | 29-07-2026 |
| 2 | Incident with Actions | 0 | 14.96 | 25-07-2026 |
| 3 | Actions run failures and delays | 0 | 10.08 | 25-07-2026 |
| 4 | Incident with Actions | 0 | 8.82 | 06-08-2026 |
| 5 | Latency issues across a number of services | 0 | 12.62 | 23-07-2026 |
| 6 | Some Copilot Cloud Agent jobs not starting | 0 | 10.28 | 05-08-2026 |
| 7 | Disruption with some GitHub services | 0 | 8.44 | 24-07-2026 |
| 8 | Incident with Pull Requests | 0 | 10.96 | 24-07-2026 |
| 9 | Incident with Copilot AI Model Providers | 0 | 7.81 | 29-07-2026 |
| 10 | Some SSH connections using deploy keys are failing | 0 | 11.66 | 21-07-2026 |