- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
What to do
Check whether your product depends on Socket. 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 7h 7m it lasted.
Anything that failed between 2026-10-01 07:59 UTC and 2026-10-01 15:06 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 5
- identified
We have observed that ticketing integrations are having delays in creating/updating/closing tickets. We have identified the cause and are working on a fix.
provider
- identified
We have deployed a fix for new creations/updates/deletions going forwards. We are working on un-sticking delivery of the events from earlier in the incident window.
provider
- identified
The events that were missed during the incident window are being replayed now. The tickets should be creating/updating/closing.
provider
- monitoring
All the events have been replayed successfully. The tickets have been created/updated/closed accordingly.
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-633b67980e
Is Socket still down?
No, this incident was resolved 2026-10-01 15:06 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
7h 7m, from 2026-10-01 07:59 UTC to 2026-10-01 15:06 UTC, by the times Socket posted.
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.