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

As listed on Socket’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Socket status & history page.

Related: Socket status & history. SquidGrid is not affiliated with Socket.