Live / Socket / Incident
Socket: Delayed updates for ticketing integrations
Socket · socket.devResolved2026-10-01 15:06 UTC
Public — what happened
Summary
Socket reported that its ticketing integrations were slow to open, change and close tickets, beginning on October 1, 2026 at 07:59 UTC, when it said it had already found the cause, though it did not describe what that cause was. By 09:02 UTC the company said a fix was in place for new ticket activity, while it worked to push through events that had been stuck earlier. At 13:15 UTC Socket said those missed events were being reprocessed, and the incident was marked resolved at 15:06.
Timeline
- Started — 2026-10-01 07:59 UTC
- Identified — 2026-10-01 07:59 UTC (3 updates)
- Resolved — 2026-10-01 15:06 UTC · 7h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Socket against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Socket: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Socket report →
More from Socket
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.