Skip to main content
Socket

Elevated latency and error rate on public API

Degraded Lasted 3h 3m · started · Socket's page

Level
confirmed
Worst impact
Degraded
Components
Socket API, Socket for GitHub, Socket Dashboard
Down Index
24of 100

What to do

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

    Anything that failed between 2026-09-22 22:13 UTC and 2026-09-23 01:15 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. investigating

    We are continuing to investigate this issue.

    provider

  3. resolved

    We identified the issue and resolved the cause.

    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-5b8a83300f

Is Socket still down?

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

How long did it last?

3h 3m, from 2026-09-22 22:13 UTC to 2026-09-23 01:15 UTC, by the times Socket posted.

What was affected?

Socket named Socket API, Socket for GitHub, Socket Dashboard.

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.