Incident with Actions
A record of the GitHub incident on August 27, 2026 (Japan time): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
1 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.
- ElevenLabsElevated latency on Text-to-Speech and Speech-to-Text Requests
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 170 minutes. Across 49 major incidents recorded for GitHub, the median duration is 85 minutes, making this the 15th 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
- Degradation in repos contents APISeptember 5, 2026
- Disruption with Copilot Code ReviewSeptember 5, 2026
- Incident with Grok Copilot AI Model ProviderSeptember 3, 2026
- Delays in commit processingSeptember 2, 2026
- Elevated rate of errors for OpenAI models provided by CopilotAugust 31, 2026