已歸檔的官方INCIDENT

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 條不同更新。同一提供方時間的文字修訂單獨保留。

  1. 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 的已儲存修訂中觀察到

Cookie 偏好設定

在您同意後,我們使用 Google Analytics 和 Umami 了解服務查詢需求。這些工具會使用 Cookie 或瀏覽器儲存。選用統計在您接受前保持關閉。

Cookie 與儲存詳情