- Level
- confirmed
- Worst impact
- Major outage
- Components
- Socket for GitHub
- Down Index
- 37of 100
What to do
Check whether you use Socket Socket for 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 16m it lasted.
Anything that failed between 2026-07-16 23:45 UTC and 2026-07-17 00:00 UTC may need a replay.Subscribe to Socket's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=socket works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Socket 4
- investigating
We are currently investigating an increase in Github App report error rates.
provider
- identified
The GitHub App is failing due to a high error rate on GitHub's API: https://www.githubstatus.com/incidents/gxycch3076xk We are dependent on GitHub to restore service.
provider
- monitoring
GitHub has restored service.
provider
- resolved
This incident has been resolved.
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-7d5ace95fa
Is Socket still down?
No, this incident was resolved 2026-07-17 00:00 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
16m, from 2026-07-16 23:45 UTC to 2026-07-17 00:00 UTC, by the times Socket posted.
What was affected?
Socket named Socket for GitHub.
What caused it?
Socket hasn't published a root cause. If it does, it shows here.
Where does this come from?
Socket's official status page, https://status.socket.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.