- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 100
What to do
Check whether your product depends on GitHub. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 48m it lasted.
Anything that failed between 2026-09-04 20:39 UTC and 2026-09-04 22:26 UTC may need a replay.Subscribe to GitHub's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub 5
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.
provider
- investigating
We are applying the mitigation and expect recovery within approximately 30 minutes.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments. The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC. We apologize for the disruption.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d0097de146
Is GitHub still down?
No, this incident was resolved 2026-09-04 22:26 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
1h 48m, from 2026-09-04 20:39 UTC to 2026-09-04 22:26 UTC, by the times GitHub posted.
What caused it?
GitHub hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.