Socket Outage History

62 incidents recorded over the last 365 days, 57 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Socket status100.00% uptime history

Every Recorded Socket Incident

Socket incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Elevated errors on the Socket API.The issue has not reoccurred since we initially corrected it.38 minResolved
Oct 16, 2026Delayed creation and updates for ticketing integrationsReplay completed. Tickets service has been restored to normal operations.1h 50mResolved
Oct 1, 2026Degraded system performance from previous emergency DB maintenanceAll systems were impacted from slower responses times. As part of of the overall recovery from the maintenance yesterday. This has now been resolved and systems are back to normal status.0 minResolved
Oct 1, 2026Delayed updates for ticketing integrationsThis incident has been resolved.7h 7mResolved
Oct 1, 2026Emergency Maintenance: DB Restart RequiredThe scheduled maintenance has been completed.1h 0mScheduled
Sep 30, 2026Degraded GitHub app performanceThe GitHub app has been restored to full capacity and throughput.9h 17mResolved
Sep 24, 2026Degraged performance across multiple servicesThis incident has been resolved.1h 32mResolved
Sep 22, 2026Elevated latency and error rate on public APIWe identified the issue and resolved the cause.3h 2mResolved
Sep 17, 2026Socket website intermittently loading for some usersThis incident has been resolved.2h 8mResolved
Sep 17, 2026Degraded performance on public package pagesThis incident has been resolved.3h 40mResolved
Sep 17, 2026Planned maintenance upgradeThe scheduled maintenance has been completed.1h 0mScheduled
Sep 5, 2026Elevated latency and error rate on public APIThis incident has been resolved.1h 43mResolved
Aug 20, 2026Firewall Events rejected/droppedThis incident has been resolved.2h 1mResolved
Aug 14, 2026Socket Github App is degradedThis incident has been resolved.41 minResolved
Aug 12, 2026GitHub Service Disruption Impacting Socket Firewall DownloadsThis incident has been resolved.56 minResolved
Aug 4, 2026Some events uploads slowThis incident has been resolved.38 minResolved
Aug 4, 2026Issues with pages loading in the Socket dashboard for select customersThis incident has been resolved.7h 28mResolved
Aug 4, 2026Elevated latency across multiple surfacesThis incident has been resolved.1h 3mResolved
Aug 2, 2026Degraded API PerformanceThis incident has been resolved.3h 16mResolved
Jul 30, 2026Delayed Scan TimesThis incident has been resolved.1h 23mResolved
Jul 24, 2026Degraded API performanceThis incident has been resolved.5h 32mResolved
Jul 24, 2026Degraded api performanceCurrently investigating degraded performance to Socket's API.-86 minResolved
Jul 23, 2026Github App reports are failingThis incident has been resolved.35 minResolved
Jul 23, 2026Planned database upgradeThe scheduled maintenance has been completed.30 minScheduled
Jul 21, 2026Elevated latency on GitHub App and APIThis incident has been resolved.1h 19mResolved
Jul 20, 2026Upstream GitHub API errors impacting Socket GitHub AppUpstream API requests appear to be operating normally now.1h 14mResolved
Jul 16, 2026Github App reports are failingThis incident has been resolved.15 minResolved
Jul 13, 2026Scan error rate elevatedPartial outage of ingesting new scans due to increased load.-37 minResolved
Jul 13, 2026Degraded GitHub App check runsThis incident has been resolved.3h 22mResolved
Jul 13, 2026Degraded API PerformanceThis incident has been resolved.14 minResolved
Jul 8, 2026Degraded GitHub App PerformanceSocket's GitHub app is experiencing degraded performance causing delayed check run indicators.0 minResolved
Jun 24, 2026Degraded Performance for API and IntegrationsThis incident has been resolved.4h 21mResolved
Jun 23, 2026Degraded scanning performanceThis incident has been resolved.4h 35mResolved
Jun 19, 2026Public package pages degradedThis incident has been resolved.1h 16mResolved
Jun 16, 2026Investigating API instabilityThe issue has been resolved.16 minResolved
Jun 8, 2026Degraded API PerformanceThis incident has been resolved.1h 59mResolved
Jun 4, 2026Planned Database UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
Jun 3, 2026Degraded API PerformanceThis incident has been resolved.4h 42mResolved
May 27, 2026Degraded API PerformanceThis incident has been resolved.3h 45mResolved
May 26, 2026Degraded system performanceThis incident has been resolved.9h 9mResolved
May 25, 2026Elevated latency on socket.devThis incident has been resolved.47 minResolved
May 18, 2026Degraded system performanceThis incident has been resolved.5h 22mResolved
May 5, 2026Investigating reports of API scan timeoutsThis incident has been resolved.4h 34mResolved
Apr 29, 2026Degraded Maven scanning performanceThis incident has been resolved.58 minResolved
Apr 28, 2026Degraded system performanceThis incident has been resolved.1h 10mResolved
Apr 21, 2026Delayed scans runsThis incident has been resolved.1h 22mResolved
Apr 11, 2026Increased latency and timeoutsThis incident has been resolved.3h 39mResolved
Apr 8, 2026Github App Reports are delayedThis incident has been resolved.3h 20mResolved
Apr 7, 2026GitHub App reports are delayedThis incident has been resolved.24 minResolved
Apr 6, 2026Elevated report latencyThis incident has been resolved.1h 26mResolved
Mar 30, 2026Degraded API PerformanceThis incident has been resolved.11h 11mResolved
Mar 25, 2026Investigating: Degraded Dashboard and API PerformanceThis incident has been resolved.15 minResolved
Mar 14, 2026GitHub App reports not startingThis incident has been resolved.37 minResolved
Mar 13, 2026Dashboard access unavailable due to DNS issueThe outage was caused by a DNS migration which has now been resolved.7 minResolved
Mar 6, 2026GitHub app reports are stuck not startingThis incident has been resolved.14h 48mResolved
Feb 25, 2026Elevated GitHub App report latencyThis incident has been resolved.50 minResolved
Jan 8, 2026Packages are being incorrectly flagged as malwareThis incident has been resolved.2h 41mResolved
Dec 18, 2025We are investigating an issue that could cause Github Check runs to not runThis incident has been resolved.2h 54mResolved
Dec 18, 2025Investigating issues with some of the API endpoints returning 503This incident has been resolved.3h 7mResolved
Dec 11, 2025Upgrade database infrastructureThe scheduled maintenance has been completed.2h 0mScheduled
Nov 18, 2025Socket website intermittently loading for some usersThis incident has been resolved.2h 59mResolved
Nov 14, 2025Issue causing intermittent API ErrorsThis incident has been resolved.1h 37mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Socket incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Socket Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Socket acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Socket outage in this window ran 14h 48m, against a mean recovery of 2h 42m. If you depend on Socket in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.