- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-05-23 19:32 UTC and 2026-05-23 19:32 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 8
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens. We are continuing to investigate.
provider
- investigating
We are continuing to investigate an elevated error rate of authentication failures for app installation tokens. Next update in one hour.
provider
- investigating
We are seeing signs of mitigation and are continuing to monitor for complete mitigation. Next update in one hour.
provider
- investigating
We see significant signs of mitigation and are monitoring for full mitigation.
provider
- investigating
We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.
provider
- investigating
This is fully mitigated, we will continue to monitor to ensure it does not reoccur.
provider
- resolved
On May 23, 2026 between 06:00 UTC and 19:12 UTC, GitHub experienced intermittent errors authenticating GitHub app installation tokens . During this time, between 1-5% of app installation token authentication requests failed, with an average of 2.3% and the error rate peaking at approximately 5.4% around 14:00 UTC. Users may have experienced authentication failures when using GitHub Apps, including failures in Git operations and API calls using app installation tokens. The issue was caused by an issue in a caching proxy component and was remediated by rolling back that component to a previous version. We are taking steps to improve monitoring for cache miss anomalies to ensure that token authentication remains functional during infrastructure changes and reviewing our protocol for testing and when we upgrade third-party dependencies.
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-783b8a2384
Is GitHub still down?
No, this incident was resolved 2026-05-23 19:32 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
0m, from 2026-05-23 19:32 UTC to 2026-05-23 19:32 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.