- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 57m it lasted.
Anything that failed between 2026-08-12 22:02 UTC and 2026-08-12 22:59 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 2
- monitoring
GitHub is currently experiencing a service disruption that may impact customers attempting to download GitHub-hosted releases, including Socket Firewall. This is an upstream GitHub issue and does not impact the operation of existing Socket Firewall deployments. Customers attempting new installations, upgrades, or other workflows that require downloading a release from GitHub may experience failures until GitHub restores service. We are monitoring the incident and will provide updates as GitHub resolves the issue.
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-b0aae23746
Is Socket still down?
No, this incident was resolved 2026-08-12 22:59 UTC. For Socket's live state, see https://down.guide/socket.
How long did it last?
57m, from 2026-08-12 22:02 UTC to 2026-08-12 22:59 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.