Live / Socket / Incident
Socket: Delayed creation and updates for ticketing integrations
Socket · socket.devCritical outageResolved2026-10-16 09:19 UTC
Public — what happened
Summary
Socket reported that its ticketing integrations were slow to create, update and close tickets, an issue it rated critical, starting at 07:28 UTC on 2026-10-16. The company said it had found the cause and began deploying a fix at 08:01 UTC meant to handle new tickets. By 08:42 UTC Socket said live functionality was back and it was working to replay events missed during the problem period, and the incident was marked resolved at 09:19 UTC.
Affected
Ticketing
Timeline
- Started — 2026-10-16 07:28 UTC
- Identified — 2026-10-16 07:28 UTC (3 updates)
- Resolved — 2026-10-16 09:19 UTC · 1h 51m 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 43, 2026, our weekly internet health report.