GitHub reported this critical-impact incident on its official status page on Oct 7, 2026, 17:17 UTC. It was resolved after 48 min.
Right now GitHub is operational. Live GitHub status →
On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7
All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
The degradation has been mitigated. We are monitoring to ensure stability.
We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history