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