Snyk Status

Resolved: All recurring tests that were missed on December 23 have now completed successfully.

Monitoring: We are now actively monitoring the progress of all recurring tests to ensure successful completion.

We'll provide an update once all tests have completed successfully.

Identified: All recurring tests that previously failed to initiate have now been triggered.

We expect all tests to be completed by the end of the day on 25th December.

We'll provide a further update once all tests have completed.

Identified: We have amended the impact statement to reflect that daily Recurring Tests are also affected.

Identified: Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected.

We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday.

The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: All recurring tests that were missed on December 23 have now completed successfully.

Monitoring: We are now actively monitoring the progress of all recurring tests to ensure successful completion.

We'll provide an update once all tests have completed successfully.

Identified: All recurring tests that previously failed to initiate have now been triggered.

We expect all tests to be completed by the end of the day on 25th December.

We'll provide a further update once all tests have completed.

Identified: We have amended the impact statement to reflect that daily Recurring Tests are also affected.

Identified: Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected.

We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday.

The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Resolved: All recurring tests that were missed on December 23 have now completed successfully.

Monitoring: We are now actively monitoring the progress of all recurring tests to ensure successful completion.

We'll provide an update once all tests have completed successfully.

Identified: All recurring tests that previously failed to initiate have now been triggered.

We expect all tests to be completed by the end of the day on 25th December.

We'll provide a further update once all tests have completed.

Identified: We have amended the impact statement to reflect that daily Recurring Tests are also affected.

Identified: Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected.

We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday.

The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: All recurring tests that were missed on December 23 have now completed successfully.

Monitoring: We are now actively monitoring the progress of all recurring tests to ensure successful completion.

We'll provide an update once all tests have completed successfully.

Identified: All recurring tests that previously failed to initiate have now been triggered.

We expect all tests to be completed by the end of the day on 25th December.

We'll provide a further update once all tests have completed.

Identified: We have amended the impact statement to reflect that daily Recurring Tests are also affected.

Identified: Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected.

We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday.

The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: All recurring tests that were missed on December 23 have now completed successfully.

Monitoring: We are now actively monitoring the progress of all recurring tests to ensure successful completion.

We'll provide an update once all tests have completed successfully.

Identified: All recurring tests that previously failed to initiate have now been triggered.

We expect all tests to be completed by the end of the day on 25th December.

We'll provide a further update once all tests have completed.

Identified: We have amended the impact statement to reflect that daily Recurring Tests are also affected.

Identified: Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected.

We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday.

The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Monitoring: We have applied a fix for this issue, and projects are now testing and importing correctly.

• Customers who have been affected are advised to import the affected repos again to ensure that projects are correctly identified, and any projects that were not able to import due to this incident are imported correctly. There is no need to delete existing projects.

Identified: Our Engineers have identified the root cause and are now working on a solution.

We'll keep you updated with our progress.

Investigating: We have detected an issue that is causing SCM scans of PNPM projects to be mis-attributed to NPM or Yarn. This is only occurring in the regional hosted environments (customers that login on sites other than app.snyk.io) Symptoms:

• PNPM projects may be detected as NPM projects, or display import errors due to missing yarn.lock files.
• Customers using set-and-forget may notice that projects previously detected as PNPM are deactivated and new NPM projects are created.
• Customers may notice a change in dependency or vulnerability reports for these projects. This does not affect customers on app.snyk.io This does not affect customers using Snyk CLI to scan pnpm projects, where the PNPM option is enabled in snyk preview.

We will update with further information as it becomes available

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Monitoring: We have applied a fix for this issue, and projects are now testing and importing correctly.

• Customers who have been affected are advised to import the affected repos again to ensure that projects are correctly identified, and any projects that were not able to import due to this incident are imported correctly. There is no need to delete existing projects.

Identified: Our Engineers have identified the root cause and are now working on a solution.

We'll keep you updated with our progress.

Investigating: We have detected an issue that is causing SCM scans of PNPM projects to be mis-attributed to NPM or Yarn. This is only occurring in the regional hosted environments (customers that login on sites other than app.snyk.io) Symptoms:

• PNPM projects may be detected as NPM projects, or display import errors due to missing yarn.lock files.
• Customers using set-and-forget may notice that projects previously detected as PNPM are deactivated and new NPM projects are created.
• Customers may notice a change in dependency or vulnerability reports for these projects. This does not affect customers on app.snyk.io This does not affect customers using Snyk CLI to scan pnpm projects, where the PNPM option is enabled in snyk preview.

We will update with further information as it becomes available

Monitoring: We have applied a fix for this issue, and projects are now testing and importing correctly.

• Customers who have been affected are advised to import the affected repos again to ensure that projects are correctly identified, and any projects that were not able to import due to this incident are imported correctly. There is no need to delete existing projects.

Identified: Our Engineers have identified the root cause and are now working on a solution.

We'll keep you updated with our progress.

Investigating: We have detected an issue that is causing SCM scans of PNPM projects to be mis-attributed to NPM or Yarn. This is only occurring in the regional hosted environments (customers that login on sites other than app.snyk.io) Symptoms:

• PNPM projects may be detected as NPM projects, or display import errors due to missing yarn.lock files.
• Customers using set-and-forget may notice that projects previously detected as PNPM are deactivated and new NPM projects are created.
• Customers may notice a change in dependency or vulnerability reports for these projects. This does not affect customers on app.snyk.io This does not affect customers using Snyk CLI to scan pnpm projects, where the PNPM option is enabled in snyk preview.

We will update with further information as it becomes available

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.

Resolved: Our Engineers have observed no further impact, this Incident is now Resolved.

The Snyk Incident Response has now been stood down.

Investigating: Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations.

Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities.

The Snyk Incident Response has been invoked, and our investigations are underway.