已归档的官方INCIDENT

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 条不同更新。同一提供方时间的文字修订单独保留。

  1. 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 的已保存修订中观察到
  2. monitoring

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

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  3. 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 的已保存修订中观察到
  4. 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 的已保存修订中观察到
  5. 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 的已保存修订中观察到
  6. 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 的已保存修订中观察到
  7. investigating

    We are preparing to deploy a change that will mitigate the impact.

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  8. 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 的已保存修订中观察到
  9. investigating

    We will post another update in approximately one hour to share our progress.

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  10. 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 的已保存修订中观察到
  11. 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 的已保存修订中观察到
  12. 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 的已保存修订中观察到
  13. investigating

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

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  14. investigating

    Database replicas have been restored. Org creation and the GitHub API are no longer degraded.

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  15. 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 的已保存修订中观察到
  16. investigating

    We are investigating reports of degraded performance for API Requests

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到