tag:snyk.statuspage.io,2005:/historySnyk Status - Incident History2024-03-29T03:54:58ZSnyktag:snyk.statuspage.io,2005:Incident/203920152024-03-28T23:33:28Z2024-03-28T23:33:28ZPlatform Degraded Performance<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>23:33</var> UTC</small><br><strong>Monitoring</strong> - The rate our platform processes request is back to normal. We’re currently monitoring the situation.</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>23:05</var> UTC</small><br><strong>Investigating</strong> - The Snyk Engineering Team has identified a decrease in the rate of our platform processes requests. Customers may experience slow response times. The incident response has been invoked. Snyk technical teams are investigating the issue. Further updates to follow.</p>tag:snyk.statuspage.io,2005:Incident/203884712024-03-28T14:16:36Z2024-03-28T14:16:36ZOccasional drops in success rates for Snyk APIs<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>14:16</var> UTC</small><br><strong>Investigating</strong> - Snyk Engineers are currently observing occasional drops in success rates in some of our APIs. The drops are observed at intermittent intervals, for extremely short durations.<br /><br />Customers may see occasional failures/timeouts, for a brief duration when calling Snyk APIs.<br /><br />The Snyk Incident response has been invoked, further updates will follow.</p>tag:snyk.statuspage.io,2005:Incident/203582082024-03-26T07:11:50Z2024-03-26T07:11:50ZSCM Imports degraded in MT-US<p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>07:11</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>06:47</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>06:33</var> UTC</small><br><strong>Update</strong> - We have identified that SCM imports will start, but will not show any projects found. This is affecting MT-US only. Snyk Incident Response is in flight</p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>06:31</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:snyk.statuspage.io,2005:Incident/203124642024-03-20T19:32:13Z2024-03-20T20:14:40ZLogout for App.snyk.io<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>19:32</var> UTC</small><br><strong>Resolved</strong> - Snyk Technical Teams have completed their activity. Services are normalized. This incident is now resolved.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>17:46</var> UTC</small><br><strong>Monitoring</strong> - Users connecting to app.synk.io experienced slow response times, which have now normalized. To ensure no further latency is observed, Snyk Technical Teams are taking mitigation steps that will result in all users connected to app.synk.io being logged out and needing to log back in. No additional downtime will be observed. This activity will take place within the next hour.</p>tag:snyk.statuspage.io,2005:Incident/203118502024-03-20T16:50:06Z2024-03-20T16:50:06ZSlow Response to App.snyk.io<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>16:50</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. Response times to app.snyk.io have normalized, and no impact is currently being experienced.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>16:24</var> UTC</small><br><strong>Investigating</strong> - Snyk monitoring systems have identified degraded performance to app.snyk.io in the Multi-Tenant US (MT-US). The Snyk Incident Response process has been evoked. Technical Teams have been engaged. Initial triage is underway.</p>tag:snyk.statuspage.io,2005:Incident/203102632024-03-20T13:43:48Z2024-03-20T13:43:48ZSnyk Code is Degraded for EU Deployment<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>13:43</var> UTC</small><br><strong>Resolved</strong> - Snyk Engineers have deployed a fix which has restored Code analysis for multi-tenant EU (<a href="https://app.eu.snyk.io/">app.eu.snyk.io/</a>) users.<br /><br />Customers who experienced a failed analysis during the degradation period (12:05 UTC - 13:35 UTC) should manually re-trigger their scans.<br /><br />No further impact is expected.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>13:25</var> UTC</small><br><strong>Investigating</strong> - Snyk Monitoring tools have identified that Code analysis is currently degraded affecting multi-tenant EU (<a href="https://app.eu.snyk.io/">app.eu.snyk.io/</a>) users.<br /><br />This does not affect <a href="https://app.snyk.io/">app.snyk.io</a> or <a href="https://app.au.snyk.io">app.au.snyk.iok</a>.<br /><br />The Incident Response has been invoked and technical teams have commenced with initial investigations.</p>tag:snyk.statuspage.io,2005:Incident/203006262024-03-19T11:59:33Z2024-03-19T12:33:21ZGo imports were degraded<p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>11:59</var> UTC</small><br><strong>Resolved</strong> - Snyk identified that Go imports with Full Source Code Analysis enabled were degraded between 22:30 UTC on the 14th of March and 21:35 UTC on the 17th of March.<br /><br />Customers importing projects through the Snyk UI with go.mod files that didn't target the latest version of Go (1.22.1) may have observed a failure error when attempting imports.<br /><br />Snyk Engineers have deployed a fix to restore functionality.</p>tag:snyk.statuspage.io,2005:Incident/202930702024-03-18T20:05:05Z2024-03-18T20:05:05ZGitlab PR checks degraded<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>20:05</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>17:55</var> UTC</small><br><strong>Monitoring</strong> - The Snyk Incident Response process remains in flight. Mitigation steps have been taken, services have stabilized, and are now under close monitoring.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>16:45</var> UTC</small><br><strong>Investigating</strong> - Snyk Monitoring systems have identified that Gitlab PR checks are currently degraded. Other Gitlab features and PR checks from other sources are unaffected.<br /><br />The Snyk Incident Response process has been invoked. Technical Teams have been engaged and initial triage is underway.</p>tag:snyk.statuspage.io,2005:Incident/202934082024-03-18T17:40:58Z2024-03-18T17:40:58ZSnyk Platform Outage<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>17:40</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>17:38</var> UTC</small><br><strong>Monitoring</strong> - The Snyk Incident Response process remains in flight. Mitigation steps have been taken, services have stabilized, and are now under close monitoring.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>17:25</var> UTC</small><br><strong>Investigating</strong> - Snyk monitoring tools have identified an intermittent outage affecting the Snyk platform in Multi-Tenant-US. Snyk Technical Teams are investigating. Additional updates will follow.</p>tag:snyk.statuspage.io,2005:Incident/201007162024-03-18T15:26:44Z2024-03-18T15:26:44ZRecurring Test Delays<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>15:26</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>16:19</var> UTC</small><br><strong>Monitoring</strong> - Snyk continues to observe delays which are affecting recurring tests. A small percentage of customers are experiencing missed daily test runs, impacting a small number of their projects. Any projects that miss their daily test runs, will complete the run the following day.<br /><br />Snyk Engineers are aware of the situation and continue to take steps towards mitigating the delays.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>20:50</var> UTC</small><br><strong>Identified</strong> - Snyk Technical Teams have observed delays affecting recurring tests. A small percentage of customers is experiencing for a small set of their projects to miss the daily test runs. They will complete the following day instead. Snyk Teams are aware of this situation and are taking steps to mitigate the delay.</p>tag:snyk.statuspage.io,2005:Incident/202358012024-03-18T13:41:02Z2024-03-18T13:41:02ZAutomated Test degradation<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>13:41</var> UTC</small><br><strong>Resolved</strong> - Snyk Engineers have implemented a fix to fully restore automated tests.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>17:16</var> UTC</small><br><strong>Monitoring</strong> - Snyk Engineers have identified that automated testing within the multi-tenant EU environment are being processed at a reduced rate.<br /><br />A fix for this will be implemented by Monday the 18th of March, until then we expect some level of degradation to affect automated testing.</p>tag:snyk.statuspage.io,2005:Incident/201163852024-03-16T15:35:56Z2024-03-16T15:35:56ZUpcoming planned maintenance<p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>15:35</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>01:45</var> UTC</small><br><strong>Scheduled</strong> - As <a href="https://status.snyk.io/incidents/wt5jc7z8ppkn">previously announced</a>, we have a planned maintenance on March 16th. This maintenance period is being reduced to 2 hours from the previously announced 12 hour window. The new maintenance window will be 12 pm UTC to 2 PM UTC.<br /><br />Maintenance is currently scheduled to take place:<br /><br />Saturday, March 16th, 12 pm UTC (8 AM ET, 1 PM GMT) to 2 pm UTC (10 AM ET, 3 PM GMT)<br /><br />We will provide prompt updates on this page if the above date or time changes.<br /><br />During this period, you may not be able to access Snyk’s services, including the CLI, API, UI and PR checks. For more information on this please check out our <a href="https://support.snyk.io/hc/en-us/articles/16431412798621">Maintenance Guide</a>.<br /><br />We understand that our services are important to your business operations and we have designed our maintenance process to minimize inconvenience to our customers. This maintenance window enables us to upgrade the Snyk platform to our new, more robust, and reliable service architecture, to better meet your business needs and to continue to scale in the future.<br /><br />We will provide status updates during the maintenance window at status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team.</p>tag:snyk.statuspage.io,2005:Incident/202718152024-03-15T18:56:05Z2024-03-15T18:56:05ZCloud Compliance Report Unresponsive<p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>18:56</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>18:42</var> UTC</small><br><strong>Monitoring</strong> - The Snyk Incident Response process remains in flight. Snyk Technical Teams have taken action to mitigate the incident. Services are now restored and are under close monitoring conditions.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>18:13</var> UTC</small><br><strong>Investigating</strong> - Snyk monitoring services have identified the Cloud Compliance Report as unresponsive. The Snyk Incident Response process has been evoked. Technical Teams have been engaged. Initial triage is underway.</p>tag:snyk.statuspage.io,2005:Incident/202322742024-03-13T13:37:17Z2024-03-13T13:37:17ZSnyk Platform outage<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>13:37</var> UTC</small><br><strong>Resolved</strong> - Snyk Engineers identified a degradation in service from 09:30 UTC to 09:45 UTC due to higher than expected load.<br /><br />Snyk Engineers have increased the resources available to handle this in future. Services have fully recovered and no further impact is expected.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>10:04</var> UTC</small><br><strong>Monitoring</strong> - Snyk Monitoring tools identified a brief outage which affected the Snyk platform at approximately 09:30 UTC. Services have now recovered.<br /><br />Snyk Engineers continue to investigate the cause of the outage.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>09:57</var> UTC</small><br><strong>Identified</strong> - Snyk Monitoring tools have identified a brief outage which affected the Snyk platform at approximately 09:30 UTC. Services have now recovered.<br /><br />Snyk Engineers are investigating the cause of the outage.</p>tag:snyk.statuspage.io,2005:Incident/201858832024-03-07T17:05:48Z2024-03-07T17:05:48ZProject Move API Failing<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>17:05</var> UTC</small><br><strong>Resolved</strong> - Snyk Technical Teams have mitigated the issue and have confirmed Project Move API is working as intended. The Incident Response has been stood down as this Incident is now Resolved.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>15:34</var> UTC</small><br><strong>Identified</strong> - Snyk Technical Teams are investigating failures observed with the Project Move API. Customers may receive a 500 response when using the Project Move API. The Snyk Incident Response has been enacted. Snyk Technical Teams have identified the issue and are taking corrective actions; additional updates will follow.</p>tag:snyk.statuspage.io,2005:Incident/201841862024-03-07T11:38:13Z2024-03-07T14:59:36ZSnyk platform outage<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>11:38</var> UTC</small><br><strong>Resolved</strong> - The Snyk platform experienced a brief outage which affected 0.3% of traffic between 11:08:50 and 11:09:00 UTC.<br /><br />This has been revised from the original impact statement where it was believed that there was a partial platform outage between 11:07 and 11:09 UTC.<br /><br />Snyk Engineers have confirmed all services have been restored.</p>tag:snyk.statuspage.io,2005:Incident/201837252024-03-07T11:26:05Z2024-03-07T11:26:05ZIAC+ Degradation<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>11:26</var> UTC</small><br><strong>Resolved</strong> - Snyk Engineers have implemented a fix to restore IaC+ scanning.<br /><br />SCM scans were impacted between 16:30 UTC (6th March) and 10:20 UTC today.<br /><br />Cloud scans were impacted between 16:30 UTC (6th March) and 11:08 UTC today.<br /><br />Customers will need to re-import repositories and re-onboard cloud environments that were initially attempted during the above outage windows. Any failed recurring tests will be run during the next schedule.<br /><br />This incident did not affect the standard Snyk IaC offering.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>10:27</var> UTC</small><br><strong>Identified</strong> - Snyk Monitoring systems have identified that IAC+ scans are currently degraded. Customers may observe issues when attempting Cloud Scans.<br /><br />There was limited impact to SCM scans which has now been resolved.<br /><br />This does not affect the standard Snyk IaC offering.</p>tag:snyk.statuspage.io,2005:Incident/201656442024-03-06T14:47:35Z2024-03-06T14:47:35ZSnyk Reporting Partially Degraded<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>14:47</var> UTC</small><br><strong>Resolved</strong> - Snyk are no longer observing delays in Reporting data.<br /><br />The Snyk incident response has now been stood down.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>09:28</var> UTC</small><br><strong>Monitoring</strong> - Snyk continues to observe a delay which is impacting Reporting data for a small percentage of projects. However, the underlying cause of the delay has been identified and data is now backfilling at an increased rate.<br /><br />Snyk Engineers are aware of the situation and continue to take steps towards mitigating the delays.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>11:40</var> UTC</small><br><strong>Investigating</strong> - Snyk Monitoring tools have identified a significant delay which is currently impacting Reporting for a small percentage of projects.<br /><br />Snyk Engineers have commenced troubleshooting the issue.<br /><br />The Snyk incident response has been invoked.</p>tag:snyk.statuspage.io,2005:Incident/200993772024-02-28T19:53:58Z2024-02-28T19:53:58ZRecurring Test Delays<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>19:53</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>17:36</var> UTC</small><br><strong>Identified</strong> - Snyk Technical Teams have observed delays affecting recurring tests. A small percentage of customers is experiencing for a small set of their projects to miss the daily test runs. They will complete the following day instead. Snyk Teams are aware of this situation and are taking steps to mitigate the delay.</p>tag:snyk.statuspage.io,2005:Incident/200976742024-02-28T12:00:00Z2024-02-28T14:12:24ZMissed Recurring Tests for Golang and Ruby<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Resolved</strong> - Users with Golang or Ruby projects will not have seen recurring tests executed from February 17th through today. <br /><br />A fix was released and as such all projects will resume automatic tests as of today (2023-02-28).</p>tag:snyk.statuspage.io,2005:Incident/200836062024-02-27T17:02:32Z2024-02-27T17:02:32ZSCM imports in MT-AU are degraded<p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>Resolved</strong> - Snyk Engineers have confirmed that the fix has been successful.<br /><br />The Snyk incident process has now been stood down.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>01:38</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>01:04</var> UTC</small><br><strong>Update</strong> - We are investigating reports that SCM imports (or API based imports) into Snyk in the MT-AU environment are degraded.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>01:03</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:snyk.statuspage.io,2005:Incident/200818782024-02-26T23:08:57Z2024-02-26T23:08:57ZCSV Failing Download From Reporting<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>23:08</var> UTC</small><br><strong>Resolved</strong> - Snyk Technical Teams deployed a fix and are now reporting all services have been restored, and no impact is currently being experienced. The Snyk Incident Response process has been stood down. This incident is now resolved.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>20:39</var> UTC</small><br><strong>Identified</strong> - Snyk Technical Teams have confirmed that customers cannot download CSV from reporting. Snyk has identified the issue and is taking steps to mitigate the impact. Further updates to follow.</p>tag:snyk.statuspage.io,2005:Incident/200806582024-02-26T19:57:19Z2024-02-26T19:57:19ZReporting PDF Missing Data Incident<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>19:57</var> UTC</small><br><strong>Resolved</strong> - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced. This incident is now resolved.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>17:25</var> UTC</small><br><strong>Monitoring</strong> - Snyk Monitoring Systems identified an issue with Reporting PDF missing data. Reports are displaying zeros for data and loading indicators across all instances. Snyk Technical Teams have now mitigated this issue and are monitoring the environment.</p>tag:snyk.statuspage.io,2005:Incident/200785632024-02-26T15:49:26Z2024-02-26T16:16:11ZSnyk Code Analysis Degradation<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>15:49</var> UTC</small><br><strong>Resolved</strong> - Snyk monitoring systems identified an outage to Snyk Code Scans. Snyk Technical Teams took steps to mitigate the issue. All functions are now operational and have remained stable throughout the monitoring period. The outage was from 12:35 to 13:15 UTC. This incident has been resolved.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>13:21</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>13:11</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:snyk.statuspage.io,2005:Incident/200584932024-02-26T12:34:48Z2024-02-26T12:34:48ZDelays affecting data retrieval in Snyk Reporting<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>12:34</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. Data in Reporting has returned to expected availability.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>15:53</var> UTC</small><br><strong>Investigating</strong> - Snyk Monitoring tools have identified that there are currently delays impacting data retrieval affecting Snyk reporting for approximately 2% of projects. Some Customers may observe significant delays affecting reporting data.<br /><br />The Snyk incident response process has been invoked.</p>