Disruption with actions hosted runners

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.<br /><br />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, 2026, 10:09 PM UTC

• monitoring

  The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  Jul 22, 2026, 10:01 PM UTC

• investigating

  The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  Jul 22, 2026, 10:01 PM UTC

• investigating

  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, 2026, 8:47 PM UTC

• investigating

  We are investigating reports of degraded performance for Actions

  Jul 22, 2026, 8:43 PM UTC