Elevated 404s for GitHub App s2s tokens in git/API
GitHub・最後の保存提供元状態：resolved
公式情報源の文章は原語で表示します。
最後の保存インシデント状態は現在サービス状態ではありません。一覧は不完全の場合があり、情報源からの消失は復旧確認ではありません。最新証拠は現在報告・公式情報源を開いてください。
保存インシデント詳細
- 提供元状態
- resolved
- 提供元が報告する影響
- none
- 提供元記録の作成
- 27 10月 2026, 08:00:00 UTC
- 提供元記録の更新
- 27 10月 2026, 20:21:53 UTC
- 提供元が明記した開始
- 27 10月 2026, 20:21:53 UTC
- 提供元が明記した終了
- 27 10月 2026, 08:00:00 UTC
The provider's end time precedes its start time. These reported timestamps do not establish a valid event duration.
提供元が報告した影響を受けるコンポーネント
この保存リビジョンで提供元は影響コンポーネントなしと明記しました。
関連はインシデント報告範囲で、現在コンポーネント可用性や検証依存関係を証明しません。
記録の作成時刻が障害開始時刻とは限りません。未報告の時刻は不明のままです。収集時刻から停止時間を算出しません。
保存リビジョンの提供元更新
新しい順です。最新の保存内容20リビジョンから最大100件の異なる更新を表示します。同じ提供元時刻の文章変更も別に保持します。
- resolved
Between 0655 and 0801 UTC on 10/27, customers experienced increased failure rates for API and git requests authenticated with server-to-server tokens for GitHub Apps (excluding Actions tokens). During this window, authenticated git operations mistakenly returned 404 for 1.24% (2.6x) of requests on average and 2.49% (5.3x) at peak. These failures were caused by a scheduled maintenance event where GitHub migrated 7 tables between two MySQL clusters in our IAD and Azure Central US datacenters. One of the affected tables stores installation records for GitHub App server-to-server tokens (excluding Actions). We've successfully completed several of these migrations in recent months without notable customer impact. However, in this case, the migration coincided with a scheduled cleanup job on the installation records table, which deleted approximately 59 million records from 0444-0617 UTC. As a result, the gh-ost tooling used in the migration experienced inter-cluster replication delays (up to 1 hour at peak). At 0655 UTC, we begin transitioning reads of the target tables to the new MySQL cluster, with 100% of reads cutover at 0721 UTC. Customer impact began, but was not detected, throughout the read cutover and persisted until completion of the write cutover at 0801 UTC. We are updating our processes and automation to prevent a repeat of this incident, including disabling overlapping cleanup jobs prior to these migrations and blocking the cutover of reads when replication delays are high.
保存リビジョンでの確認：27 10月 2026, 20:23:07 UTC