Socket change history
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Delayed creation and updates for ticketing integrations Socket reported a critical ticketing integration degradation delaying ticket creation, updates and closure from 2026-10-16 07:28 UTC to 2026-10-16 09:19 UTC, lasting 1 h 50 min. Live functionality was restored, missed events were replayed, and the ticketing service returned to normal operations. | Major incident | |
| Critical incident: Socket website intermittently loading for some users Socket Website loaded intermittently for some users in an incident rated critical, starting 2026-09-17 19:52 UTC and resolved at 2026-09-17 22:01 UTC; the reported duration was 2 h 8 min. Socket implemented a fix at 20:35 UTC but did not state a cause. | Major incident | |
| Major incident: Elevated latency and error rate on public API Socket’s public API experienced elevated latency and error rates in a major-impact incident from 2026-09-05 07:21 UTC to 2026-09-05 09:04 UTC, lasting 1 h 43 min. Socket reported implementing a fix at 07:41 UTC and subsequently resolved the incident; no cause was stated. | Major incident | |
| Major incident: Firewall Events rejected/dropped Socket reported a major Socket API incident in which the Events collection system incorrectly rejected Firewall Events. It started at 2026-08-20 23:05 UTC and was resolved at 2026-08-21 01:06 UTC, lasting 2 h 1 min; customers’ Firewall Events could be rejected or dropped during that period. | Major incident | |
| Major incident: Elevated latency across multiple surfaces Socket reported major elevated latency affecting Socket for GitHub, Package Pages, Socket API, Socket Dashboard and Socket Website, starting 2026-08-04 07:42 UTC. A fix was implemented by 2026-08-04 08:33 UTC, and the incident was resolved at 2026-08-04 08:45 UTC after 1 h 3 min. | Major incident | |
| Critical incident: Github App reports are failing Socket’s GitHub App reports failed in a critical-impact incident starting 2026-07-16 23:45 UTC, lasting 15 min and resolved at 2026-07-17 00:00 UTC. Socket attributed the failures to a high error rate on GitHub’s API and reported that GitHub restored service. | Major incident | |
| Critical incident: GitHub App reports not starting | Major incident | |
| Major incident: Dashboard access unavailable due to DNS issue | Major incident | |
| Major incident: GitHub app reports are stuck not starting | Major incident |