tag:status.socket.dev,2005:/historySocket Status - Incident History2026-03-16T06:23:58-07:00Sockettag:status.socket.dev,2005:Incident/289834352026-03-13T23:54:31-07:002026-03-13T23:54:31-07:00GitHub App reports not starting<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>23:54</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>23:16</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating problems with GitHub App reports not starting. Preliminary investigation shows high error rates coming from the upstream GitHub API.</p>tag:status.socket.dev,2005:Incident/289760702026-03-13T15:34:13-07:002026-03-13T15:34:13-07:00Dashboard access unavailable due to DNS issue<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>15:34</var> PDT</small><br><strong>Resolved</strong> - The outage was caused by a DNS migration which has now been resolved.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>15:31</var> PDT</small><br><strong>Update</strong> - We have identified the issue and seeing services load.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>15:27</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating an issue that is causing an outage due to DNS. We are investigating and determining the impact</p>tag:status.socket.dev,2005:Incident/288289412026-03-06T23:04:53-08:002026-03-06T23:04:53-08:00GitHub app reports are stuck not starting<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>23:04</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>12:53</var> PST</small><br><strong>Update</strong> - We have investigated further and still believe this to be a problem with GitHub upstream. We are working on implementing mitigations.<br /><br />If a PR has a stuck check run, please try closing and reopening the PR. This will cause GitHub to send another webhook, which should be delivered.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>09:50</var> PST</small><br><strong>Update</strong> - GitHub is having a Webhooks incident which may be impacting webhook deliveries to Socket. We are working to confirm this.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>08:15</var> PST</small><br><strong>Investigating</strong> - We are investigating an issue with some GitHub app reports not starting.</p>tag:status.socket.dev,2005:Incident/286528262026-02-24T20:02:14-08:002026-02-24T20:02:14-08:00Elevated GitHub App report latency<p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>20:02</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>19:12</var> PST</small><br><strong>Investigating</strong> - We are experiencing elevated GitHub App report run times. We are currently investigating.</p>tag:status.socket.dev,2005:Incident/279384912026-01-08T15:41:24-08:002026-01-08T15:41:24-08:00Packages are being incorrectly flagged as malware<p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:41</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>12:59</var> PST</small><br><strong>Identified</strong> - We have observed that a large number packages have been incorrectly flagged as malware, with incorrect threat descriptions. We are working on a fix.</p>tag:status.socket.dev,2005:Incident/276447542025-12-18T04:42:06-08:002025-12-18T04:42:06-08:00We are investigating an issue that could cause Github Check runs to not run<p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>04:42</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>02:00</var> PST</small><br><strong>Monitoring</strong> - We have implemented a fix and are monitoring the status</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>01:47</var> PST</small><br><strong>Investigating</strong> - We are currently investigating this issue</p>tag:status.socket.dev,2005:Incident/276446252025-12-18T04:41:57-08:002025-12-18T04:41:57-08:00Investigating issues with some of the API endpoints returning 503<p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>04:41</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>02:00</var> PST</small><br><strong>Monitoring</strong> - We have implemented a fix and are monitoring the status</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>01:34</var> PST</small><br><strong>Investigating</strong> - Some endpoints are returning a 503. We are currently investigating</p>tag:status.socket.dev,2005:Incident/274786212025-12-10T23:36:28-08:002025-12-10T23:36:28-08:00Upgrade database infrastructure<p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>23:36</var> PST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>10</var>, <var data-var='time'>22:00</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>08:18</var> PST</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>08:18</var> PST</small><br><strong>Scheduled</strong> - During this time:<br /><br />The Socket Dashboard will be unavailable<br />API and Full Scans will be offline<br />New GitHub scans will not be created<br /><br />All queued events will resume processing automatically once maintenance is complete.<br />We will post updates here throughout the window.</p>tag:status.socket.dev,2005:Incident/272165562025-11-18T07:16:06-08:002025-11-18T07:16:07-08:00Socket website intermittently loading for some users<p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>07:16</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>06:48</var> PST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>06:45</var> PST</small><br><strong>Update</strong> - The issue is resolved</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>05:16</var> PST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>04:30</var> PST</small><br><strong>Monitoring</strong> - Our upstream cloud provider is working on remediating their outage, and we are seeing traffic fully recover. We will continue to monitor.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>04:16</var> PST</small><br><strong>Identified</strong> - We have identified an issue with an upstream cloud provider that may be intermittently affecting the Socket website and package pages for some users.</p>tag:status.socket.dev,2005:Incident/271653632025-11-14T10:42:42-08:002025-11-14T10:42:42-08:00Issue causing intermittent API Errors<p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>10:42</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>09:05</var> PST</small><br><strong>Investigating</strong> - We have received reports of intermittent errors with the API and we are investigating</p>tag:status.socket.dev,2005:Incident/268465142025-10-22T08:51:51-07:002025-10-22T08:51:51-07:00Socket platform outage<p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>08:51</var> PDT</small><br><strong>Resolved</strong> - The issue has been fully resolved, and all services are now back to normal. During the incident, some Socket GitHub app actions were automatically closed due to timeouts, but new runs are now completing successfully.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>04:36</var> PDT</small><br><strong>Monitoring</strong> - We identified a problem with an upstream cloud provider. We have implemented a workaround, which has restored service. We are continuing to monitor for problems.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>03:44</var> PDT</small><br><strong>Investigating</strong> - Some parts of the Socket platform are unavailable due to underlying infrastructure issues. Package pages are not loading and scans are not completing. We are working to resolve these issues as fast as possible.</p>tag:status.socket.dev,2005:Incident/265890142025-09-29T10:26:04-07:002025-09-29T10:26:04-07:00Issues loading Org Alerts, Repository stats, and overview page<p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>10:26</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>08:11</var> PDT</small><br><strong>Identified</strong> - This issue was caused by an upstream cloud provider. We have implemented a workaround, and functionality should be restored shortly.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>06:10</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.socket.dev,2005:Incident/265678172025-09-26T17:44:33-07:002025-09-26T17:44:33-07:00Issues loading Org Alerts, Repository stat, and overview page<p><small>Sep <var data-var='date'>26</var>, <var data-var='time'>17:44</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>26</var>, <var data-var='time'>14:18</var> PDT</small><br><strong>Update</strong> - We have implemented a partial fix and some functionality has been restored, we are working on a few remaining fixes.</p><p><small>Sep <var data-var='date'>26</var>, <var data-var='time'>13:46</var> PDT</small><br><strong>Identified</strong> - We have found an issue that is impacting certain Socket Plans for loading of the historical alerts. We are currently working on a fix.</p>tag:status.socket.dev,2005:Incident/264755212025-09-17T14:47:17-07:002025-09-17T14:47:17-07:00Elevated scan latency<p><small>Sep <var data-var='date'>17</var>, <var data-var='time'>14:47</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>17</var>, <var data-var='time'>13:55</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>17</var>, <var data-var='time'>12:47</var> PDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Sep <var data-var='date'>17</var>, <var data-var='time'>12:34</var> PDT</small><br><strong>Identified</strong> - A small percentage of scans are experiencing timeouts due to high load within our system. We have identified the cause and are implementing a fix.</p>tag:status.socket.dev,2005:Incident/261659462025-08-19T09:02:10-07:002025-08-19T09:02:10-07:00Org Alerts are showing no results for some customers<p><small>Aug <var data-var='date'>19</var>, <var data-var='time'>09:02</var> PDT</small><br><strong>Resolved</strong> - Organization alerts and overview data is now loading and this issue has been resolved.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>18:12</var> PDT</small><br><strong>Investigating</strong> - We are investigating an issue impacting some customers where Org Alerts and Org Overview might be empty.</p>tag:status.socket.dev,2005:Incident/260357882025-08-05T19:02:52-07:002025-08-05T19:02:52-07:00Organization alerts not loading<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>19:02</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>15:29</var> PDT</small><br><strong>Update</strong> - We have made changes to work around our provider issues. Dashboard analytics are currently working again. We are monitoring to ensure the service stays healthy.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>15:25</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>15:08</var> PDT</small><br><strong>Identified</strong> - An upstream cloud provider is having an outage, which is affecting the loading of analytics data in our dashboard. We are awaiting resolution from them. Scanning and blocking of threats continue to operate normally.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>15:00</var> PDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:47</var> PDT</small><br><strong>Investigating</strong> - We are investigating elevated errors and timeouts with loading organization alerts in the dashboard.</p>tag:status.socket.dev,2005:Incident/259491442025-07-28T13:06:22-07:002025-07-28T13:06:22-07:00Intermittent issue fetching alerts and analytics<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>13:06</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>08:29</var> PDT</small><br><strong>Monitoring</strong> - We have increased capacity of the system by scaling up necessary components and we are seeing a decrease in the error rate. We will continue to evaluate our infrastructure to look for ways to avoid issues like this in the future.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>08:09</var> PDT</small><br><strong>Investigating</strong> - We are seeing increased error rate when fetching alerts and analytics, and the team is investigating.</p>tag:status.socket.dev,2005:Incident/258603992025-07-19T18:26:30-07:002025-07-19T18:26:30-07:00High npm package ingestion/analysis latency<p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>18:26</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>12:20</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented to increase the queue priority for downloading npm tarballs, and additional resources have been provisioned. We are already observing improvements and will continue to monitor the situation closely.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>09:10</var> PDT</small><br><strong>Update</strong> - We have identified a processing backlog for npm tarball downloads. However, the backlog is actively being reduced, and services are working normally. We are investigating steps to increase system capacity.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>08:32</var> PDT</small><br><strong>Investigating</strong> - We are currently experiencing an outage where our system is running behind with downloading tarballs for npm. This issue is preventing users from receiving proper alerts on newly published npm package versions.</p>tag:status.socket.dev,2005:Incident/256845202025-07-03T17:42:30-07:002025-07-03T17:42:30-07:00Degraded performance for Alert Processing<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>17:42</var> PDT</small><br><strong>Resolved</strong> - Service is working normally again at this point</p><p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>17:31</var> PDT</small><br><strong>Investigating</strong> - We have discovered an issue with our processing of alerts for Org Alerts, Org Dependencies, and and Repo Alerts. It can take longer than usual for them to appear after the latest scan to the default branch of your repo. We are currently investigating.</p>tag:status.socket.dev,2005:Incident/255144142025-06-17T13:39:07-07:002025-06-17T13:39:07-07:00High GitHub App Error Rate<p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>13:39</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>12:47</var> PDT</small><br><strong>Identified</strong> - We are experiencing an elevated error rate on GitHub API requests due to an upstream GitHub incident.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>12:43</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.socket.dev,2005:Incident/254570212025-06-12T14:10:54-07:002025-06-12T14:10:54-07:00Socket performance can be degraded due to ongoing outages with cloud providers<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>14:10</var> PDT</small><br><strong>Resolved</strong> - Our upstream cloud providers (Cloudflare, GCP, etc) have resolve their outages and operations should be back to normal.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>11:47</var> PDT</small><br><strong>Identified</strong> - We are monitoring an issue with our upstream cloud providers that are having outages or degraded performance. This can impact the processing of the Github integration, Dashboard loading, and other features.</p>tag:status.socket.dev,2005:Incident/253499802025-06-03T03:32:28-07:002025-06-03T03:32:28-07:00Github PR Checks processing running slow<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>03:32</var> PDT</small><br><strong>Resolved</strong> - This has been resolved and all checks should be performing as normal. We determined that the only impact was for the internal Socket org and customers should not have been impacted.</p><p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>02:44</var> PDT</small><br><strong>Investigating</strong> - Engineering is investigating an issue that is causing the Socket Github App to process the Webhooks from Github very slowly. This could cause Socket PR checks to either get triggered after a long amount of time or Socket PR checks be in a pending state for longer than normal. times. We are actively investigating and working on fixing this.</p>tag:status.socket.dev,2005:Incident/253145852025-05-30T13:26:40-07:002025-05-30T13:26:41-07:00Github App is Down<p><small>May <var data-var='date'>30</var>, <var data-var='time'>13:26</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'>30</var>, <var data-var='time'>13:16</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.socket.dev,2005:Incident/248469302025-05-01T18:42:43-07:002025-05-02T10:23:12-07:00Dashboard Outage<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>18:42</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved. The incident was caused by a DDoS attack on the Socket website. We are improving our DDoS mitigations to avoid future impact.</p><p><small>May <var data-var='date'> 1</var>, <var data-var='time'>12:09</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>May <var data-var='date'> 1</var>, <var data-var='time'>12:01</var> PDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>May <var data-var='date'> 1</var>, <var data-var='time'>11:42</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating an incident for Socket that is causing an outage of the dashboard.</p>tag:status.socket.dev,2005:Incident/246351202025-04-11T20:30:16-07:002025-04-11T20:30:16-07:00Unexpected Reset of Feature Flags Impacting User Experience<p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>20:30</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>18:12</var> PDT</small><br><strong>Investigating</strong> - We have identified an incident where internal feature flags were inadvertently reset, potentially affecting user experience across our platform. We are currently investigating the impact of this issue and are actively working to restore configuration to its correct state.</p>