Is Snyk Down Right Now? Check if there is a current outage ongoing.

Our Engineers are aware of degradation currently affecting customers using Bitbucket Cloud integrations. This appears to be an issue within the Bitbucket Cloud environment. We have invoked our Incident Response to monitor the situation. We will provide further updates as and when these are received from Bitbucket Cloud.

Our Incident Response team has identified some potential issues with Snyk Code PR Checks. We are currently investigating this further and will share any updates as soon as we have them.

Our Incident Response team has identified several Snyk services impacted due to a third party provider issue. We are currently investigating this further and will share updates as we learn more.

Our Engineers have identified degradation affecting the PR Experience within our <a href="https://app.snyk.io">app.snyk.io</a> environment. Customers within the above environment may observe that PR Comments and Inline Comments are delayed. PR checks are unaffected. The Snyk Incident Response has been invoked, and our investigations are underway.

Our Engineers have verified that the issue appears to be resolved. No Snyk intervention was required to restore service. The Snyk Incident Response has now been stood down.

We have identified a problem with the Jira app integration where vulnerabilities are not appearing in the security tab. Our Engineers have verified that the Snyk environment is operating normally. The issue appears to originate within the Atlassian environment. We've engaged Atlassian support and will share additional information as it becomes available.

No additional issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

Our Engineers have identified the root cause of the issue and deployed a fix. We're now monitoring to ensure services remain stable.

Our Engineers have identified degradation affecting project dependencies within our <a href="https://app.snyk.io">app.snyk.io</a> environment. Customers importing new projects or testing already existing projects within Snyk Open Source and Snyk Container may observe that dependencies are not loading. The Snyk Incident Response has been invoked, and our investigations are underway.

Our Engineers have identified degradation affecting project dependencies within our app.snyk.io environment.Customers importing new projects or testing already existing projects within Snyk Open Source and Snyk Container may observe that dependencies are not loading.The Snyk Incident Response has been invoked, and our investigations are underway.

We have identified a problem with the Jira app integration where vulnerabilities are not appearing in the security tab. Our Engineers have verified that the Snyk environment is operating normally. The issue appears to originate within the Atlassian environment. We've engaged Atlassian support and will share additional information as it becomes available.

The overall health of our services looks to be stable, transitioning the incident to Resolved.

GitHub services have been restored, and we are currently monitoring our systems to ensure everything is functioning as expected.

We are actively monitoring the GitHub status page for updates regarding the ongoing API degradation. We will continue to track the situation and will provide further updates as GitHub shares more information or once the issue is resolved on their end.

We are currently experiencing a degradation in the GitHub API, which is impacting the majority of flows that interact with the GitHub Agent across all environments. At this time, there is no indication that self-hosted GitHub Enterprise instances are affected.

We are currently experiencing a degradation in the GitHub API, which is impacting the majority of flows that interact with the GitHub Agent across all environments. At this time, there is no indication that self-hosted GitHub Enterprise instances are affected.

After monitoring the situation, Snyk Engineers have confirmed the issue is resolved. The Snyk Incident Response team has been stood down.

A fix has been deployed, and early indications show it has been effective. We are currently monitoring to ensure continued service stability.

Our Engineers have observed degradation affecting the PR Experience within our <a href="https://app.us.snyk.io">app.us.snyk.io</a> environment. Customers may observe PR Experience failures when using Snyk Code or Snyk Open Source products in the above environment. The Snyk Incident Response has been invoked, and our investigations are underway.

Our Engineers have observed degradation affecting the PR Experience within our app.us.snyk.io environment.Customers may observe PR Experience failures when using Snyk Code or Snyk Open Source products in the above environment.The Snyk Incident Response has been invoked, and our investigations are underway.

Our engineers did not observe any customer impact during the monitoring period. The Snyk Incident Response has been stood down.

Preliminary investigations indicate that our customers are not affected. We will continue to monitor the situation to confirm this remains the case.

Our Engineers have been alerted to degradation affecting Snyk Code. Customers may experience errors when running tests and/or PR checks within Snyk Code. The Snyk Incident Response has been invoked, and our Engineers are investigating.

Our Engineers have been alerted to degradation affecting Snyk Code.Customers may experience errors when running tests and/or PR checks within Snyk Code.The Snyk Incident Response has been invoked, and our Engineers are investigating.

This incident has been resolved.

Our Engineers identified that Snyk CLI version 1.1297.0 (released 14th May ) is failing for a subset of gradle projects (Android projects) and have now released a fix. Customers using Snyk CLI version 1.1297.0 as a pinned version are asked to upgrade to Snyk CLI version 1.1297.1.

Our Engineers have identified that Snyk CLI version 1.1297.0 (released 14th May ) is failing for a subset of gradle projects (Android projects). Customers utilising Snyk CLI test and/or monitor commands may observe failures for the mentioned projects. The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers have identified that Snyk CLI version 1.1297.0 (released 14th May ) is failing for a subset of gradle projects (Android projects).Customers utilising Snyk CLI test and/or monitor commands may observe failures for the mentioned projects.The Snyk Incident Response has been invoked, and investigations are underway.

This incident has been resolved and there is no further backlog

A fix has been implemented, and we are monitoring the results. There should be no further customer impact

We are investigating an issue that is causing some backlog which may be causing a delay in processing project deletion and project move commands. We will provide an update as soon as we know more

We are investigatin an issue that is causing some backlog which may be causing a delay in processing project deletion and project move commands. We will provide an update as soon as we know more

A fix has been deployed, and our Engineers have confirmed this has resolved the incident. The Snyk Incident Response has now been stood down.

Our Engineers are aware of an issue causing degradation of Snyk Essentials. Customers may have experienced failures within the Snyk Essentials inventory UI. The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers are aware of an issue causing degradation of Snyk Essentials.Customers may have experienced failures within the Snyk Essentials inventory UI.The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers have not detected any additional issues during the monitoring period and are confident that the problem has been resolved. The Snyk Incident Response has now been stood down.

Our Engineers have deployed a fix, and initial indications show that this has mitigated the issue. We will continue to monitor to confirm ongoing stability.

Our Engineers have identified that Snyk Code tests are currently degraded. Customers may experience failures affecting their Snyk Code tests. The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers have identified that Snyk Code tests are currently degraded.Customers may experience failures affecting their Snyk Code tests.The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers are aware of a momentary drop in success rate affecting our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment. During this time, customers using this environment may have noticed a temporary rise in error rates. A fix has been implemented, and we do not anticipate any further issues affecting our services.

Our Engineers are aware of a momentary drop in success rate affecting our app.au.snyk.io environment.During this time, customers using this environment may have noticed a temporary rise in error rates.A fix has been implemented, and we do not anticipate any further issues affecting our services.

We’re about to commence scheduled maintenance. During this time Snyk services may be unavailable for up to 3 hours and users of PR checks, CLI, API, and UI will be impacted. Thanks for your patience while we complete this essential work.Regular updates will be posted to the status page throughout the maintenance window.

We are informing you about upcoming planned maintenance that will temporarily impact the availability of Snyk services while we upgrade our cloud infrastructure. Maintenance is scheduled to take place between the following times:Saturday May 10 2025 from 2:00 pm UTC to 5:00 pm UTC07:00 PDT / 10:00 EDT / 15:00 BST / 00:00 AEDT (start of Sunday 11th in Australia)During this time, you will not be able to access Snyk services. We understand that our availability may be critical to your business operations and so we have planned our maintenance activity to minimize disruption.This will be the second of our 2025 planned maintenance events. As a reminder, we intend to give you a predictable schedule by limiting planned maintenance to the second Saturday of every 3rd month from February 8 2025:* February 8 2025* May 10 2025* August 9 2025* November 8 2025We will confirm each event nearer the time with at least 30 days’ advance notice wherever possible.We have put together a support page (https://support.snyk.io/s/article/Snyk-Maintenance---Planning-Guidance) to summarize what you can expect during the downtime and to suggest mitigations you could consider. On the day of maintenance, our team will keep you informed of our progress via updates at https://status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team (https://support.snyk.io/).We appreciate your understanding as we work to improve your experience as a valued customer.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

No further issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

A fix has been deployed, and initial signs suggest this has been successful. However, we're monitoring to ensure stability remains throughout peak traffic periods.

Our Engineers continue to implement mitigation steps and are analyzing the current impact.

Our Engineering team has identified latency issues affecting the Snyk PR check experience within the SCM for customers using our <a href="https://app.snyk.io/">app.snyk.io</a> environment. Customers within the above environment may observe that the native experience (Summary and Inline comments) within PR checks is delayed. PR checks themselves should be unaffected. The Snyk Incident response has been invoked, and investigations are underway.

This issue has been resolved, and customers should no longer encounter problems when installing the Bitbucket Cloud app. The Snyk Incident Response has now been stood down.

Our Engineers are currently investigating an issue impacting the installation of the Bitbucket Cloud app. As a result, customers using the <a href="https://app.us.snyk.io/">app.us.snyk.io</a> environment are unable to install the Bitbucket Cloud app. The Snyk Incident Response has been invoked, and the team are actively working to identify the cause.

Our Engineering team has deployed a fix to address this issue and we do not observe any additional errors at this time. The Snyk Incident Response has been stood down.

Our Engineering team has potential degradation on Project import and tests. The Snyk Incident response has been invoked, and investigations are underway.

Our Engineering team has potential degradation on Project import and tests.The Snyk Incident response has been invoked, and investigations are underway.

Our Engineers are currently investigating an issue impacting the installation of the Bitbucket Cloud app.As a result, customers using the app.us.snyk.io environment are unable to install the Bitbucket Cloud app.The Snyk Incident Response has been invoked, and the team are actively working to identify the cause.

Our Engineering team has identified latency issues affecting the Snyk PR check experience within the SCM for customers using our app.snyk.io environment.Customers within the above environment may observe that the native experience (Summary and Inline comments) within PR checks is delayed. PR checks themselves should be unaffected.The Snyk Incident response has been invoked, and investigations are underway.

No further errors were detected during the monitoring period. The Snyk Incident Response has been stood down.

Our Engineers identified that Snyk Code PR Checks were degraded for a short time. A fix has been implemented, and we are now seeing improvements. We are monitoring to ensure stability remains.

Our Engineers identified that Snyk Code PR Checks were degraded for a short time.A fix has been implemented, and we are now seeing improvements.We are monitoring to ensure stability remains.

Following continued monitoring, we have not identified any further issues and have been unable to reproduce the problem. We are confident that the issue is resolved. The Snyk Incident Response has now been stood down.

The fix has now been deployed to our app.snyk.io environment. The fix has now been applied to all multi-tenant environments. Our engineers are monitoring at this time.

The fix has now been deployed to our <a href="https://app.eu.snyk.io">app.eu.snyk.io</a> and <a href="https://app.au.snyk.io">app.au.snyk.io</a> environments. We will share another update when the rollout has concluded.

The environment on which the fix was initially rolled out was <a href="https://app.us.snyk.io/">app.us.snyk.io</a> and not <a href="https://app.snyk.io">app.snyk.io</a> as reported earlier. Once the rollout to our remaining environments is complete, we will provide a further update.

The fix implemented to our <a href="https://app.snyk.io">app.snyk.io</a> environment has been successful in mitigating the issue. Our Engineers will proceed with deploying the fix across our remaining environments. We will provide a further update once the rollout is complete.

Our Engineers have rolled out a fix to our <a href="https://app.snyk.io">app.snyk.io</a> environment due to the higher volume of expected traffic in this environment. This is to ensure that the issue is mitigated and that services respond well to the changes made. We will continue to monitor throughout the evening and roll out the fix to all other environments once we have full confidence that the issue is resolved.

Our internal testing remains ongoing. However, it is almost complete. During our testing and investigations, we have identified that all our multi-tenant environments will experience this issue. Further updates will be shared once internal testing is completed.

Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact. Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos. We're currently testing a fix internally to ensure it mitigates the issue.

Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally. We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our <a href="https://app.snyk.io">app.snyk.io</a> environment. We will keep you updated on the progress of our investigation.

Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source. Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our <a href="https://app.snyk.io">app.snyk.io</a> environment. Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status. The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Our Engineers have confirmed that services have remained stable. The Snyk Incident Response has been stood down.

Our Engineers confirm no further issues have been observed. However, to ensure stability, we will continue to monitor services throughout today and through the weekend. We will provide a further update on Monday, 21st April.

Snyk Engineers have implemented a fix and, after a period of monitoring, are no longer observing delays. We will continue to monitor to ensure stability.

Our Engineers have implemented a fix to mitigate the load on the environment, and the initial signs are positive. Some customers will continue observing latency of around 2 hours, which we expect to clear in the evening hours(EMEA).

Snyk Engineers continue to observe delays affecting IaC+ scans. Remediation efforts remain underway. We will keep you updated on our progress.

Our Engineers are continuing to work on a fix to mitigate the delays affecting IaC+ scans. We will keep you updated on our progress.

Snyk Engineers have identified an issue affecting IaC+ scan results in the SNYK-US-01 (app.snyk.io) environment. The Snyk Incident response has been enacted. Customers will observe a delay with the IaC+ scans displayed in the UI. Our Engineers are aware of the issue and are working to mitigate the delays.

Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.We will keep you updated on the progress of our investigation.

Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations. Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings. Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Our Engineers identified an issue with our Google SCC integration.Some customers may observe that a small percentage of their projects did not correctly sync from Snyk to SCC, causing stale Findings.Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Snyk Engineers have identified an issue affecting IaC+ scan results in the SNYK-US-01 (app.snyk.io) environment. The Snyk Incident response has been enacted. Customers will observe a delay with the IaC+ scans displayed in the UI. Our Engineers are aware of the issue and are working to mitigate the delays.

No further repeat of the issue was detected during scheduled re-scans. This incident is resolved.

Our Engineers identified that a shutdown issue had caused all integrations to be incorrectly marked as failed after they had, in fact, been completed. A fix has been implemented, and we are monitoring to ensure its effectiveness.

We have verified that most workflows are completing normally, but we have detected an increase in load that may lead to some integrations being reported as failed. Scans are completing at a delayed rate of processing. Investigation is ongoing as to the cause.

Snyk engineering has detected that some Group Level integration profiles- which are used for batch processes to update the Essentials Inventory- are degraded. New connections cannot be created, and existing connections are shown as failing. Existing inventory assets are unaffected, but updates to asset inventory are delayed. Organisation level SCM integrations (used for import, retest) are unaffected. Snyk Engineering are investigating.

Snyk Engineers have confirmed services are operating normally after mitigation steps were taken. No additional impact is expected. The Snyk Incident Response has been stood down.

Our Engineers have identified the cause of the degraded performance and have taken action to mitigate the impact. No additional impact is observed and we are now under monitoring conditions.

Our Engineers have confirmed that customers may observe longer-than-normal complete times for CLI Code tests as well as Code PR checks. The Snyk Incident Response remains in flight as the investigation continues.

Our Engineers continue to investigate degraded performance observed with Snyk Code PR checks.

Our Engineers have identified that Snyk Code PR checks within the <a href="https://app.snyk.io">app.snyk.io</a> environment are degraded. Customers using the above environment may observe that Code PR checks are taking longer than normal to complete or fail. The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers have identified that Snyk Code PR checks within the app.snyk.io environment are degraded.Customers using the above environment may observe that Code PR checks are taking longer than normal to complete or fail.The Snyk Incident Response has been invoked, and investigations are underway.

Snyk engineering has detected that some Group Level integration profiles- which are used for batch processes to update the Essentials Inventory- are degraded.New connections cannot be created, and existing connections are shown as failing. Existing inventory assets are unaffected, but updates to asset inventory are delayed.Organisation level SCM integrations (used for import, retest) are unaffected.Snyk Engineering are investigating.

Our Engineers have implemented the remediation actions and are no longer observing issues with scheduled tests. The Snyk Incident Response has now been stood down.

Our Engineers continue to work on remediation steps to mitigate the degradation that is being observed. Customers may observe that scheduled tests continue to complete at a slower rate than expected. Further updates will follow.

Our Engineers have identified the cause of the degradation and are now working on remediation steps. Customers may observe that scheduled tests continue to complete at a slower rate than expected. Further updates will follow.

Our Engineers are still investigating the cause of the degradation to our recurring tests within the <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment. Further updates will follow.

Our Engineers have identified that recurring tests within our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment are degraded. Customers within the above environment may observe that scheduled tests are completing at a slower rate than expected. The Snyk Incident Response has been invoked, and we are investigating.

Our Engineers have confirmed that the underlying issue has now been resolved. The Snyk Incident Response has been stood down.

Snyk is aware of an issue that impacted customers using the custom branches feature where a subset of projects created using the CLI across the Open Source and Snyk Code products have been duplicated. The issue caused project duplication, and occurred between 28/03/2025 at 11:00 UTC and 31/03/2025 at 06:30 UTC. Duplication is no longer happening, and Snyk is working to de-duplicate the affected projects.

Support services are fully operational. Snyk incident response is standing down

A fix has been identified and deployed. All support services are restored. We are currently monitoring the results

Service to the Snyk support portal (support.snyk.io) is currently degraded. Customers will not be able to log in to the support portal, view or create cases, use the community discussion, or search knowledge articles. Customers can create a case by sending an email to support@snyk.io; however, Snyk Support is currently unable to reply to cases. The service is supported by a third-party vendor, and we are diligently working with them to resolve the issue and restore service. We will provide an update on this page once the issue is resolved or if there is a material development.

Service to the Snyk support portal (support.snyk.io) is currently degraded.Customers will not be able to log in to the support portal, view or create cases, use the community discussion, or search knowledge articles.Customers can create a case by sending an email to support@snyk.io; however, Snyk Support is currently unable to reply to cases.The service is supported by a third-party vendor, and we are diligently working with them to resolve the issue and restore service.We will provide an update on this page once the issue is resolved or if there is a material development.

Snyk is aware of an issue that impacted customers using the custom branches feature where a subset of projects created using the CLI across the Open Source and Snyk Code products have been duplicated. The issue caused project duplication, and occurred between 28/03/2025 at 11:00 UTC and 31/03/2025 at 06:30 UTC. Duplication is no longer happening, and Snyk is working to de-duplicate the affected projects.

Our Engineers have identified that recurring tests within our app.au.snyk.io environment are degraded.Customers within the above environment may observe that scheduled tests are completing at a slower rate than expected.The Snyk Incident Response has been invoked, and we are investigating.

The fix has been deployed, and our Engineers have observed no further issues. The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th. We will keep you updated with our progress.

Synk Engineers have identified an issue affecting Snyk-US-02, Snyk-EU-01, and Snyk-AU-01. No impact has been observed, and there is a low expectation that this will occur. However, the potential impact occurs when new code vulnerabilities are introduced after March 19th; customers utilizing the Snyk code report (CLI Upload) may observe that previously found issues will be given new identities. As a consequence, these issues will not be ignorable. Snyk engineers are working towards mitigation.

The fix has been deployed, and our Engineers have observed no further issues.The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.We will keep you updated with our progress.

Synk Engineers have identified an issue affecting Snyk-US-02, Snyk-EU-01, and Snyk-AU-01. No impact has been observed, and there is a low expectation that this will occur. However, the potential impact occurs when new code vulnerabilities are introduced after March 19th; customers utilizing the Snyk code report (CLI Upload) may observe that previously found issues will be given new identities. As a consequence, these issues will not be ignorable. Snyk engineers are working towards mitigation.

The fix has been deployed, and our Engineers have observed no further issues. The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th. We recognise the impact this is having and appreciate your patience while we work to resolve it. We will keep you updated with our progress.

Our engineers have pinpointed the cause of the problem and are actively working on a solution. The fix is complex, therefore, it may take a few days for this to reach the production environment. We will keep you updated on our progress.

Snyk Engineers are preparing the fix. However, no timeline is available at this time. Once available, the fix will be deployed. Additional details to follow.

Our Engineers have identified the root cause and are taking steps to mitigate the issue.

Snyk Engineers are investigating an issue affecting Jira ticket creation using the Jira Integration via the Snyk UI. Customers may observe "Could not get fields" error message when attempting to create Jira tickets via the UI.

The fix has been deployed, and our Engineers have observed no further issues.The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.We recognise the impact this is having and appreciate your patience while we work to resolve it.We will keep you updated with our progress.

Our engineers have pinpointed the cause of the problem and are actively working on a solution.The fix is complex, therefore, it may take a few days for this to reach the production environment.We will keep you updated on our progress.

Snyk Engineers are preparing the fix. However, no timeline is available at this time. Once available, the fix will be deployed. Additional details to follow.

Our Engineers have identified the root cause and are taking steps to mitigate the issue.

Snyk Engineers are investigating an issue affecting Jira ticket creation using the Jira Integration via the Snyk UI. Customers may observe "Could not get fields" error message when attempting to create Jira tickets via the UI.

No further issues have been observed during the monitoring phase, and our Engineers are confident the issue is now resolved. The Snyk Incident Response has been stood down.

A fix has been deployed, and we are now monitoring to ensure its success.

Our Engineers have identified that Snyk PR checks are degraded. Customers may experience PR Check delays when using Snyk Code. The Snyk Incident Response has been invoked, and we are investigating.

No further issues have been observed during the monitoring phase, and our Engineers are confident the issue is now resolved.The Snyk Incident Response has been stood down.

A fix has been deployed, and we are now monitoring to ensure its success.

Our Engineers have identified that Snyk PR checks are degraded.Customers may experience PR Check delays when using Snyk Code.The Snyk Incident Response has been invoked, and we are investigating.

No further issues have been observed during our monitoring phase. The Snyk Incident Response has now been stood down.

Our Engineers have deployed a fix and are now monitoring to ensure this has been successful.

Our Engineers have identified that AppRisk integrations are currently degraded. Customers may observe that integrations within AppRisk have not run as scheduled and that profiles may show up as 'Failed'. The Snyk Incident Response has been invoked, and we are investigating.

No further issues have been observed during our monitoring phase.The Snyk Incident Response has now been stood down.

Our Engineers have deployed a fix and are now monitoring to ensure this has been successful.

Our Engineers have identified that AppRisk integrations are currently degraded.Customers may observe that integrations within AppRisk have not run as scheduled and that profiles may show up as 'Failed'.The Snyk Incident Response has been invoked, and we are investigating.

Our Engineers are confident the incident is now resolved. The Snyk Incident Response has been stood down.

Our Engineers have deployed a fix and are monitoring the situation to ensure its success.

Our Engineers have identified an issue impacting Snyk Learn. Customers may notice that they are unable to log in to Snyk Learn. The Snyk Incident Response has been invoked, and we are investigating.

Our Engineers are confident the incident is now resolved.The Snyk Incident Response has been stood down.

Our Engineers have deployed a fix and are monitoring the situation to ensure its success.

Our Engineers have identified an issue impacting Snyk Learn.Customers may notice that they are unable to log in to Snyk Learn.The Snyk Incident Response has been invoked, and we are investigating.

Our Engineers have deployed an additional fix, resolving the issue in our <a href="http://app.snyk.io/">app.snyk.io</a> environment. All environments are now operating as expected. The Snyk Incident Response has now been stood down.

Our Engineers implemented a fix which has improved the error rate across our environments. However, our customers using our <a href="http://app.snyk.io/">app.snyk.io</a> environment may still experience issues when scanning JAR files.

Number of errors has dropped significantly since the mitigation was applied. We're continuing to monitor.

We've applied a mitigation to the issue, and will be monitoring it over the next few hours to ascertain its efficacy.

We have found a potential explanation for the failures, and are working to confirm it. We will share additional updates as we obtain more information.

We have found a potential explanation for the failures, and are working to confirm it. We will share additional updates as we obtain more information.

Failures are intermittent - users may experience tests on JAR files fail and succeed shortly after. We'll provide a full update as soon as we have additional details.

We're experiencing issues scanning JAR files in both Snyk Open Source and Snyk Container. The issue affects all environments.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We have identified the issue and have taken the required restorative actions. Al services impact have now been restored.

Our Engineers have identified that there is degradation affecting Snyk tests within our <a href="http://app.us.snyk.io/">app.us.snyk.io</a> environment. Customers may observe degradation in testing functionality (manual and recurring), with some failing or not initiating as scheduled. The Snyk Incident Response has been invoked and our Engineers are investigating.

It has been confirmed that data freshness is now back to normal. The incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing an incident that is causing a delay in the population of the data for both the Reporting page and REST Issues API. As a result, there may be a delay of up to one hour for the data to appear as expected.

Our Engineers are confident that the implemented fix has successfully resolved the issue. The Snyk Incident Response has now been stood down.

We have implemented a fix and are currently monitoring to confirm its effectiveness.

Our Engineers have identified the root cause of the issue and are working on a fix. Some customers may notice that their issues have been resolved. However, the problem may reoccur until a full fix is released. Further updates to follow.

Our Engineers have identified a degradation with the AppRisk Essentials integrations feature. Customers who initiate new integrations within the AppRisk Essentials (group level) integrations page may observe that all existing integrations are no longer listed. However, we are confident all existing integrations remain in place and the error is with the page displaying these. Some customers may receive the 'Action Failed. Try again in a few minutes' error, when trying to configure a new integration. The Snyk Incident Response has been invoked, and our Engineers are investigating.

Snyk Technical Teams are aware of an issue that affected the Open Source Fix PR UI across all environments. Between 16:20 UTC and 20:00 UTC, customers may have observed a forbidden error when accessing the UI. Snyk Engineers applied a fix, and no further impact was observed. The Snyk incident response has been stood down.

We have released a fix for the failures of Imports, Retests and PR Checks for Go Module projects. Our Engineers are no longer observing impact. The incident response process has been stood down.

We have identified a fix for the failures of Imports, Retests and PR Checks for Go Module projects. A further update will be provided when we are confident that the fix can be released.

Snyk Engineers have detected failures with go.mod projects when integrated with GitHub/GitHub Enterprise via Broker. This includes project failing to import, as well as failures of retests and PR checks. We are currently investigating.

Our Engineers have not observed any further issues, and they are confident that the steps implemented have resolved the incident. The Snyk Incident Response has been stood down.

Our Engineers are aware of the degradation which affected our <a href="https://app.snyk.io/">app.snyk.io</a> environment. Customers may have observed tests failing on Open Source as well as CLI tests failing due to being unable to fetch policies. The Snyk Incident Response was invoked, and our Engineers have implemented a fix to restore normal service. We are now monitoring to ensure the stability of the environment.

Our Engineers are aware of a degradation of services between 12:54 GMT and 13:45 GMT, which affected our <a href="http://app.us.snyk.io/">app.us.snyk.io</a> environment. During this window, customers may have experienced errors or timeouts affecting Push Events, PR Checks & Manual Retests. A fix was applied to restore normal service.

Our Engineers have successfully implemented a fix, resolving the incident. The Snyk Incident Response has now been stood down.

Our Engineers have pinpointed what they believe to be the root of the problem and are currently working on a solution. The fix will undergo testing in our pre-production environments prior to being tested and implemented in our production environment.

We are continuing to investigate this issue.

Our Engineers have discovered a sporadic login issue impacting <a href="https://app.snyk.io/">app.snyk.io</a>. Customers using third-party login providers (such as Github, Google, etc.) to log in to <a href="https://app.snyk.io/">app.snyk.io</a> may experience occasional login failures. The Snyk Incident Response has been invoked, and our Engineers are investigating.

This incident has been resolved.

Snyk Engineers have mitigate the SSO Failures and are now under monitoring conditions.

Snyk Engineering Teams continue to take steps to fully mitigate the incident. SSO Logins are being restored. Restoration efforts continue.

Snyk Engineers have identified the issue and are taking steps to mitigate the SSO failures. Further updates to follow.

Snyk Technical Teams are investigating reports of SSO failures. Customers may experience a 404 error. The Snyk Incident Response has been enacted. Additional updates to follow.

No connectivity issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

Snyk Engineers have completed mitigating the incident and no longer observe the previous degradation. Snyk will continue to monitor the environment throughout the weekend to ensure stability before standing down our Incident Response.

Snyk Engineers have identified the cause of degradation affecting our SCMs in the European environments. Our Engineers have taken steps to mitigate the issue and are no longer observing errors, timeouts, or traffic bursts. Synk Engineers are continuing their activities to fully mitigate this incident. Further updates to follow.

We have identified service degradation across our SCMs that is causing an impact on our services in our European environments. The Snyk Incident Response is now in flight and our Engineers are actively investigating to resolve. Further updates will follow.

Customers impacted by the issue should update to CLI v1.1295.2. Those using CLI v1.1295.0 are not required to make any changes. The Snyk Incident Response has now been stood down.

Customers using the latest CLI release (v1.1295.1) may observe their CLI scans failing. Snyk Engineers have confirmed that a new CLI (v1.1295.2) release is available for those customers using CLI (v1.1295.1). Customers currently on CLI (v1.1295.0) do not need to upgrade to (v1.1295.2).

We are continuing to investigate this issue.

Error rates have been confirmed as low and we can advise that the impact will only be experienced by a small subset of Snyk users. The Snyk incident response remains in flight and technical teams focused on working to resolve the issue. Further updates will be provided.

Our Engineers have identified degradation affecting CLI scans. Some customers may observe their CLI scans failing when using the latest CLI release (v1.1295.1). The Snyk Incident Response has been invoked, and our Engineers are investigating.

During our monitoring period, no additional issues were detected. The Snyk Incident Response has now been stood down.

We identified and mitigated the root cause of the intermittent errors following co-op investigations with our cloud services provider. We are monitoring the environment to ensure stability following the fix. No re-occurrences have been observed.

We identified and mitigated the root cause of the intermittent errors following co-op investigations with our cloud services provider. The incident has now been classified as resolved and no additional errors have been identified since approximately 11.20 UTC.

We have identified intermittent connectivity errors impacting service stability across our US Environment. Our incident response process is now in flight and our Engineering teams are investigating the matter. The impact is confirmed as minor, however, customers may well experience intermittent errors across the Snyk suite of products hosted in the US. Our Engineers remain active and engaged and are working to resolve the problems noted above. Further updates will follow.

Atlassian has resolved their incident affecting Jira applications. Snyk Engineers have validated that no further impact is being observed. The Snyk Incident Response has been stood down.

Our Engineers have identified degradation affecting Snyk Security in Jira Cloud. We are aware Atlassian have reported issues affecting Jira applications. Customers utilising Snyk Security in Jira Cloud may notice that vulnerabilities are not being populated within Security Containers. The Snyk Incident Response has been invoked, and our Engineers are investigating. Initial indications suggest that the Snyk platform is operating as expected.

During our monitoring phase, we have not observed any additional impact. The Snyk Incident Response has now been stood down.

Our Engineers pinpointed the issue and implemented a fix. Early indications suggest that this has resolved the incident. We are now monitoring the situation to confirm the effectiveness of the fix.

Our engineers have identified that Snyk Monitoring is currently degraded. This issue will impact actions that save project states, such as CLI monitoring and imports within the Snyk UI. The Snyk Incident Response has been invoked and our Engineers are investigating.

No further impact was observed during our monitoring phase, and our engineers are confident the incident has now been resolved. The Snyk Incident Response has now been stood down.

Snyk Engineers have observed that functionality has been restored across all environments and are monitoring the situations to ensure stability.

Our Engineers have identified that Bitbucket Connect integrations are currently degraded. We are aware that Bitbucket is investigating an issue within its environment. Customers may notice latency and/or failures affecting their Bitbucket Connect integrations. This will affect actions such as recurring tests, amongst others. The Snyk Incident Response has been invoked and our Engineers are investigating.

Our engineers have applied a fix that has been confirmed as successful. We do not anticipate any additional impact to Recurring Tests. The Snyk Incident Response has now been stood down.

Throughout the monitoring period, our engineers have noticed that the initial issue has reappeared. However, its impact has considerably diminished, affecting only a minor portion of recurring tests for customer projects. A limited number of customers may still find that a small percentage of their projects have not been tested as planned. Our investigations are still in progress, and we will provide further updates.

Our Engineers have confirmed that services have now recovered. However, our investigations remain ongoing to identify the root cause. We are now monitoring the services to ensure no further issues are observed.

Our investigations are still in progress, and we will provide additional updates as they become available.

Our Engineers have observed degradation affecting recurring tests. Some Customers may notice that a small percentage of their projects have not been re-tested as scheduled. The Snyk Incident Response has been invoked and our Engineers are investigating.

Our Engineers have implemented a fix, and testing has verified that the incident has now been resolved. The Snyk Incident Response has now been stood down.

Our engineers have identified authentication issues impacting users who haven't authenticated with Snyk and haven't set up an API URL. Customers might notice that users configured to use <a href="https://app.us.snyk.io/">app.us.snyk.io</a>, who haven't specified an endpoint URL in their IDE or CLI while using OAuth2 authentication, encounter login problems indicating invalid credentials or occasional failures in redirecting to the correct cloud environment. To workaround this issue, affected customers can specify the endpoint URL before authentication. The Snyk Incident Response has been invoked and our Engineers are investigating.

The fix has been confirmed as successful and no further issues have been observed. The Snyk Incident Response has now been stood down.

Our engineers have implemented a fix, and initial indications show it has been effective. We are actively monitoring the situation to verify the effectiveness of the fix.

Our engineers have detected degradation impacting Code PR checks in our <a href="https://app.eu.snyk.io/">app.eu.snyk.io</a> and <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environments. Customers may encounter failures or other issues related to Code PR checks within these environments. The Snyk Incident Response has been invoked and our Engineers are investigating.

Our engineers identified degradation in our Open Source and Container testing at 08:57 UTC and promptly applied a fix to restore service at 09:10 UTC. Customers using our <a href="https://app.snyk.io/">app.snyk.io</a> environment may have noticed a degradation of CLI, API and SCM testing during this time. The service has now been restored, and our engineers anticipate no further issues.

Snyk Engineers have implemented a fix and all services remain stable after a period of monitoring. The Snyk incident response has been stood down. The incident is now resolved.

Our engineers have implemented a fix, and initial indications show that the issue has been mitigated. We are continuing to monitor the situation to ensure the platform's stability before standing down the incident.

Our Engineers have identified increased error rates across all products within the <a href="https://app.eu.snyk.io/">app.eu.snyk.io</a> environment. Customers may observe latency and/or errors when using <a href="https://app.eu.snyk.io/">app.eu.snyk.io</a>. The Snyk Incident Response has been invoked and our Engineers are investigating.