‹ 返回事件歷史

Incident with Git Operations, Pull Requests and Actions

已復原嚴重故障GitHub
2026年10月8日星期四 00:25 至 2026年10月8日星期四 00:25(不到 1 分鐘)
受影響元件
Git Operations
Webhooks
Issues
Pull Requests
Actions
更新記錄
已復原2026年10月8日星期四 00:25

On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected. In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded. GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers. Each outage ended when one of our established machines with correct configuration became the leader of the quorum and sent the correct configuration. After the first outage, we identified the new machine as the source and paused automated maintenance to stop it from being leader again. At 16:52 UTC, an automated maintenance task that did not honor the pause put it back in charge, and the outage happened again. We shut that machine down at 17:02 UTC and have since removed it, and the automation now honors the pause, which was a new regression due to an update of our puppet infrastructure. To prevent recurrence, we are clearing retired database servers from the service's records before any new machine is added, and we are keeping new machines from being elected leader until their records have been checked. We are also changing our systems to reject configuration that point to servers that don't exist and to keep using the last known-good settings instead. Finally, we are giving responders a faster way to take a misbehaving machine out of service, and adding alerts so changes like this are spotted within seconds. We will share a more detailed write-up of these incidents in our monthly availability report, along with the status of the repairs we are making to prevent issues like these in the future.

監控中2026年10月8日星期四 00:23

Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

監控中2026年10月7日星期三 23:58

We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

監控中2026年10月7日星期三 23:56

The degradation has been mitigated. We are monitoring to ensure stability.

監控中2026年10月7日星期三 23:49

The degradation has been mitigated. We are monitoring to ensure stability.

排查中2026年10月7日星期三 23:49

The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

排查中2026年10月7日星期三 23:47

The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

排查中2026年10月7日星期三 23:41

We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

排查中2026年10月7日星期三 23:35

Git Operations is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:32

Actions is operating normally.

排查中2026年10月7日星期三 23:31

The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

排查中2026年10月7日星期三 23:27

Webhooks is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:27

Git Operations is operating normally.

排查中2026年10月7日星期三 23:25

Pull Requests is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:24

We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

排查中2026年10月7日星期三 23:21

Git Operations is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:16

Webhooks is experiencing degraded availability. We are continuing to investigate.

排查中2026年10月7日星期三 23:15

Issues is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:14

Webhooks is experiencing degraded performance. We are continuing to investigate.

排查中2026年10月7日星期三 23:14

We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

事件資料來自 GitHub 官方狀態頁:查看官方原文

關於這些資料

GitHub 的事件資料來自哪裡?

資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。

如何解讀元件狀態列?

每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。

為什麼有些服務查不到歷史?

只收錄提供公開官方狀態頁的服務。

持續時間如何計算?

按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。

完整的服務清單與即時狀態見狀態總覽