- Level
- confirmed
- Worst impact
- Degraded
- Components
- Socket Website, Socket Dashboard
- Down Index
- 19of 100
What to do
Check whether you use Socket Socket Website, Socket Dashboard. 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 47m it lasted.
Anything that failed between 2026-05-25 08:44 UTC and 2026-05-25 09:31 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 3
- identified
We have identified elevated latency and timeouts on socket.dev caused by high request load. We are working on a solution.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-b7b1be6c23
Is Socket still down?
No, this incident was resolved 2026-05-25 09:31 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
47m, from 2026-05-25 08:44 UTC to 2026-05-25 09:31 UTC, by the times Socket posted.
What was affected?
Socket named Socket Website, Socket Dashboard.
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.