Partial outageGitHub ・ August 24, 2026

Elevated errors on Fable 5 due to upstream provider

A record of the GitHub incident on August 24, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.

Started
Aug 24, 2026, 07:12 AM UTC
Resolved
Aug 24, 2026, 07:58 AM UTC
Duration
47m
Impact
Partial outage

Other providers down at the same time

2 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.

Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.

How big was this outage?

This outage lasted 47 minutes. Across 58 major incidents recorded for GitHub, the median duration is 95 minutes, making this the 44th longest.

Shorter than a typical outage.

Only incidents recorded as major-or-worse and already resolved are counted.

Current status

GitHub is operating normally now. This incident has been resolved.

See current GitHub status →

What you can do during an outage

Source: GitHub's official status page.

Other GitHub incidents

  1. Grok 4.6 and Grok 4.7 Service IssuesOctober 23, 2026
  2. Disruption with Dependabot AlertsOctober 23, 2026
  3. Delayed Actions status check resultsOctober 23, 2026
  4. Project updates delayedOctober 22, 2026
  5. Incident with Actions ResultsOctober 22, 2026