- Level
- confirmed
- Worst impact
- Degraded
- Components
- Socket API, Socket for GitHub
- Down Index
- 20of 100
What to do
Check whether you use Socket Socket API, 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 1h 24m it lasted.
Anything that failed between 2026-07-30 21:48 UTC and 2026-07-30 23:12 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
- identified
We are investigating delayed scan times.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
We've identified the problem and deployed remediation and are monitoring system performance. Request and report latencies are restoring to normal.
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-63890f130a
Is Socket still down?
No, this incident was resolved 2026-07-30 23:12 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
1h 24m, from 2026-07-30 21:48 UTC to 2026-07-30 23:12 UTC, by the times Socket posted.
What was affected?
Socket named Socket API, 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.