Skip to main content
Socket

Elevated latency across multiple surfaces

Partial outage Lasted 1h 3m · started · Socket's page

Level
confirmed
Worst impact
Partial outage
Components
Socket API, Socket for GitHub, Socket Website, Socket Dashboard, Package Pages
Down Index
33of 100

What to do

  • Check whether you use Socket Socket API, Socket for GitHub, Socket Website, Socket Dashboard and 1 more. 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 1h 3m it lasted.

    Anything that failed between 2026-08-04 07:42 UTC and 2026-08-04 08:45 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-b3ef15bd85

Is Socket still down?

No, this incident was resolved 2026-08-04 08:45 UTC. For Socket's live state, see https://down.guide/socket.

How long did it last?

1h 3m, from 2026-08-04 07:42 UTC to 2026-08-04 08:45 UTC, by the times Socket posted.

What was affected?

Socket named Socket API, Socket for GitHub, Socket Website, Socket Dashboard and 1 more.

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.