Live  /  Providers  /  Socket

Socket

socket.devNo open incidents

Independent assessment — SquidGrid is not affiliated with Socket. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Socket’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Socket is reporting

Current & recent incidents

Resolved

Degraged performance across multiple services

None impact · 2026-09-25 03:36 UTC

Resolved

Elevated latency and error rate on public API

Minor impact · 2026-09-23 01:15 UTC

Resolved

Socket website intermittently loading for some users

Critical impact · 2026-09-17 20:35 UTC

Resolved

Degraded performance on public package pages

Minor impact · 2026-09-17 18:10 UTC

Resolved

Elevated latency and error rate on public API

Major impact · 2026-09-05 07:41 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Socket has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Socket runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Socket is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Socket.