Incident with Actions
GitHub · 마지막 저장 제공업체 상태: resolved
공식 출처 문구는 원어로 표시됩니다.
마지막 저장 사고 상태는 현재 서비스 상태가 아닙니다. 출처 목록은 불완전할 수 있고 소멸은 복구 확인이 아닙니다. 최신 증거는 현재 보고 또는 공식 출처를 확인하세요.
저장 사고 상세
- 제공업체 상태
- resolved
- 제공업체 영향
- critical
- 제공업체 기록 생성
- 05 Oct 2026, 19:11:58 UTC
- 제공업체 기록 갱신
- 06 Oct 2026, 22:48:02 UTC
- 제공업체가 명시한 시작
- 05 Oct 2026, 19:11:58 UTC
- 제공업체가 명시한 종료
- 05 Oct 2026, 22:49:42 UTC
제공업체가 보고한 영향받은 구성 요소
- Actions
br0l2tvcx85d - Pages
vg70hn9s2tyj
연결은 사고 보고 범위이며 현재 구성 요소 가용성이나 검증 의존 관계를 입증하지 않습니다.
기록 생성 시각이 반드시 장애 시작 시각인 것은 아닙니다. 보고되지 않은 시각은 알 수 없음으로 유지하며 수집 시각으로 중단 시간을 계산하지 않습니다.
저장 수정본의 제공업체 업데이트
최신순입니다. 최신 저장 내용 수정본 20개에서 최대 100개의 서로 다른 업데이트를 표시합니다. 같은 제공업체 시각의 문구 변경도 별도 보존됩니다.
- resolved
On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br /> <br />During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. <br /><br /><br />The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. <br /><br /><br />We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. <br /><br /> <br />We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Pages is operating normally.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
Actions is operating normally.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
Actions is experiencing degraded performance. We are continuing to investigate.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
Pages is experiencing degraded performance. We are continuing to investigate.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
Actions is experiencing degraded availability. We are continuing to investigate.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC - investigating
We are investigating reports of degraded performance for Actions
저장 수정본에서 확인 06 Oct 2026, 22:48:58 UTC