Incident across several services
GitHub · 마지막 저장 제공업체 상태: resolved
공식 출처 문구는 원어로 표시됩니다.
마지막 저장 사고 상태는 현재 서비스 상태가 아닙니다. 출처 목록은 불완전할 수 있고 소멸은 복구 확인이 아닙니다. 최신 증거는 현재 보고 또는 공식 출처를 확인하세요.
저장 사고 상세
- 제공업체 상태
- resolved
- 제공업체 영향
- minor
- 제공업체 기록 생성
- 23 Sep 2026, 10:11:12 UTC
- 제공업체 기록 갱신
- 29 Sep 2026, 12:43:35 UTC
- 제공업체가 명시한 시작
- 23 Sep 2026, 10:11:12 UTC
- 제공업체가 명시한 종료
- 24 Sep 2026, 04:55:33 UTC
제공업체가 보고한 영향받은 구성 요소
- API Requests
brv1bkgrwx7q
연결은 사고 보고 범위이며 현재 구성 요소 가용성이나 검증 의존 관계를 입증하지 않습니다.
기록 생성 시각이 반드시 장애 시작 시각인 것은 아닙니다. 보고되지 않은 시각은 알 수 없음으로 유지하며 수집 시각으로 중단 시간을 계산하지 않습니다.
저장 수정본의 제공업체 업데이트
최신순입니다. 최신 저장 내용 수정본 20개에서 최대 100개의 서로 다른 업데이트를 표시합니다. 같은 제공업체 시각의 문구 변경도 별도 보존됩니다.
- resolved
Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects. <br /><br />The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24. <br /><br />The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays. <br /><br />We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We are preparing to deploy a change that will mitigate the impact.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We will post another update in approximately one hour to share our progress.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for API Requests
저장 수정본에서 확인 06 Oct 2026, 13:58:39 UTC