ARCHIVED OFFICIAL INCIDENT

Degradation in repos contents API

GitHub · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
minor
Provider record created
04 Sep 2026, 22:02:15 UTC
Provider record updated
15 Sep 2026, 23:34:38 UTC
Explicit provider start
04 Sep 2026, 22:02:15 UTC
Explicit provider end
04 Sep 2026, 22:23:34 UTC

Affected components reported by the provider

The provider explicitly listed no affected components in this saved revision.

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. resolved

    On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.<br /><br />The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.<br /><br />We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  2. investigating

    We are investigating reports of impacted performance for some GitHub services.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC