Incident with Actions
A record of the GitHub incident on August 6, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
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.
- PerplexityComputer Sandbox Issue
- CursorDegraded Performance for Grok 4.5
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 642 minutes. Across 58 major incidents recorded for GitHub, the median duration is 95 minutes, making this the 2th longest.
Longer 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
- Grok 4.6 and Grok 4.7 Service IssuesOctober 23, 2026
- Disruption with Dependabot AlertsOctober 23, 2026
- Delayed Actions status check resultsOctober 23, 2026
- Project updates delayedOctober 22, 2026
- Incident with Actions ResultsOctober 22, 2026