Live / Socket / Incident
Socket: Degraded GitHub app performance
Socket · socket.devMinor incidentResolved2026-10-01 03:35 UTC
Public — what happened
Summary
Socket said its GitHub app was slow to process events starting at 18:18 UTC on 2026-09-30, an issue it rated as minor. By 00:17 UTC on 2026-10-01 the company said things were partly stable but the app could still be degraded, and it expected emergency maintenance to settle the problem. Socket reported at 03:24 UTC that a fix was in place and capacity was being brought back up, and it marked the incident resolved at 03:35.
Timeline
- Started — 2026-09-30 18:18 UTC
- Identified — 2026-09-30 18:18 UTC (2 updates)
- Monitoring — 2026-10-01 03:24 UTC (2 updates)
- Resolved — 2026-10-01 03:35 UTC · 9h 18m 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 41, 2026, our weekly internet health report.