Live / Socket / Incident
Socket: Elevated errors on the Socket API.
Socket · socket.devResolved2026-11-02 17:28 UTC
Public — what happened
Summary
Socket said it saw a period of higher-than-normal errors on its API starting at 16:49 UTC on 2026-11-02. The company said it fixed the problem right away and does not expect any further impact. The incident was marked resolved at 17:28, and Socket did not name a cause or say who was affected.
Affected
Socket API, Package Pages
Timeline
- Started — 2026-11-02 16:49 UTC
- Monitoring — 2026-11-02 16:49 UTC
- Resolved — 2026-11-02 17:28 UTC · 38 min 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 46, 2026, our weekly internet health report.