Skip to main content
Socket

Delayed creation and updates for ticketing integrations

Major outage Lasted 1h 51m · started · Socket's page

Level
confirmed
Worst impact
Major outage
Components
Ticketing
Down Index
42of 100

What to do

  • Check whether you use Socket Ticketing. 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 51m it lasted.

    Anything that failed between 2026-10-16 07:28 UTC and 2026-10-16 09:19 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.

Root cause

We have identified the cause and are working on a fix.
Read the postmortem

Updates from Socket 4

  1. 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

  2. identified

    We are starting a deploy which should resolve the issue for new tickets. After this completes we will work to get missed ticket updates replayed.

    provider

  3. identified

    We have restored live functionality and are working on replaying older events that were missed during the incident window.

    provider

  4. resolved

    Replay completed. Tickets service has been restored to normal operations.

    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-ec8f526b44

Is Socket still down?

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

How long did it last?

1h 51m, from 2026-10-16 07:28 UTC to 2026-10-16 09:19 UTC, by the times Socket posted.

What was affected?

Socket named Ticketing.

What caused it?

Socket wrote: "We have identified the cause and are working on a fix." The postmortem: https://stspg.io/x3r25xrz3hq6

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.