Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Disruption with actions hosted runners

Дата публикации: 22-07-2026 22:09:26


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

Основное содержимое страницы с новостью.

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.

Posted Jul 22, 2026 - 22:09 UTC

Monitoring

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

Posted Jul 22, 2026 - 22:01 UTC

Update

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

Posted Jul 22, 2026 - 22:01 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.

Posted Jul 22, 2026 - 20:47 UTC

Investigating

We are investigating reports of degraded performance for Actions

Posted Jul 22, 2026 - 20:43 UTC

This incident affected: Actions.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Incident with Actions012.5629-07-2026
2Incident with Actions014.9625-07-2026
3Actions run failures and delays010.0825-07-2026
4Incident with Actions08.8206-08-2026
5Latency issues across a number of services012.6223-07-2026
6Some Copilot Cloud Agent jobs not starting010.2805-08-2026
7Disruption with some GitHub services08.4424-07-2026
8Incident with Pull Requests010.9624-07-2026
9Incident with Copilot AI Model Providers07.8129-07-2026
10Some SSH connections using deploy keys are failing011.6621-07-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 13.62. Источник: www.githubstatus.com.