- Level
- confirmed
- Worst impact
- Degraded
- Components
- Socket API
- Down Index
- 24of 100
What to do
Check whether you use Socket Socket API. 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 11h 11m it lasted.
Anything that failed between 2026-03-30 12:01 UTC and 2026-03-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 3
- investigating
We are investigating reports of intermittent errors and elevated response times on the Socket API. Some requests may take longer than expected or require retries. We are actively working to resolve the issue and will provide updates as we have them.
provider
- identified
We have rolled out a initial fixes and working on additional updates. Overall response times and errors have improved.
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-0214cdb25f
Is Socket still down?
No, this incident was resolved 2026-03-30 23:12 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
11h 11m, from 2026-03-30 12:01 UTC to 2026-03-30 23:12 UTC, by the times Socket posted.
What was affected?
Socket named Socket API.
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.