Socket: Github App reports are failing

What to do

Check whether you use Socket 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 36m it lasted.
Anything that failed between 2026-07-23 14:41 UTC and 2026-07-23 15:17 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.

investigatingJul 23, 2026, 2:41 PM UTC
We are currently investigating this issue.
provider
investigatingJul 23, 2026, 2:59 PM UTC
We are continuing to investigate this issue.
provider
identifiedJul 23, 2026, 2:59 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringJul 23, 2026, 3:04 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedJul 23, 2026, 3:17 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Socket still down?

No, this incident was resolved 2026-07-23 15:17 UTC. For Socket's live state, see https://down.guide/socket.

How long did it last?

36m, from 2026-07-23 14:41 UTC to 2026-07-23 15:17 UTC, by the times Socket posted.

What was affected?

Socket named 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.