Snyk Status

Resolved: We're no longer observing delays affecting the Issues API V3 service.

The Snyk Incident Response has been stood down.

Monitoring: We have deployed a fix, and success rates have returned to normal, with requests no longer timing out. Response times have also improved significantly.

We are monitoring to make sure the service remains stable.

Identified: We have identified an issue affecting Issues API V3 that is causing response delays for some users. Overall service performance remains otherwise unaffected.

Our engineering team has isolated the cause and is actively working on a fix. We will share another update as soon as the patch is deployed.

Resolved: We're no longer observing delays affecting the Issues API V3 service.

The Snyk Incident Response has been stood down.

Monitoring: We have deployed a fix, and success rates have returned to normal, with requests no longer timing out. Response times have also improved significantly.

We are monitoring to make sure the service remains stable.

Identified: We have identified an issue affecting Issues API V3 that is causing response delays for some users. Overall service performance remains otherwise unaffected.

Our engineering team has isolated the cause and is actively working on a fix. We will share another update as soon as the patch is deployed.

Resolved: We're no longer observing delays affecting the Issues API V3 service.

The Snyk Incident Response has been stood down.

Monitoring: We have deployed a fix, and success rates have returned to normal, with requests no longer timing out. Response times have also improved significantly.

We are monitoring to make sure the service remains stable.

Identified: We have identified an issue affecting Issues API V3 that is causing response delays for some users. Overall service performance remains otherwise unaffected.

Our engineering team has isolated the cause and is actively working on a fix. We will share another update as soon as the patch is deployed.

Resolved: We're no longer observing delays affecting the Issues API V3 service.

The Snyk Incident Response has been stood down.

Monitoring: We have deployed a fix, and success rates have returned to normal, with requests no longer timing out. Response times have also improved significantly.

We are monitoring to make sure the service remains stable.

Identified: We have identified an issue affecting Issues API V3 that is causing response delays for some users. Overall service performance remains otherwise unaffected.

Our engineering team has isolated the cause and is actively working on a fix. We will share another update as soon as the patch is deployed.

Resolved: No further impact has been observed during our monitoring period.

The Snyk Incident Response has been stood down.

Monitoring: Snyk engineers have completed mitigation efforts, and the environment is currently being monitored.

Identified: Our engineering team has identified the root cause of the issue and is actively taking steps to resolve it. Impacted customers may experience testing slowdowns (up to 45 seconds) until mitigation efforts are complete.

Investigating: Our engineers are investigating failures affecting CLI tests for customers within our app.snyk.io environment.

Customers may experience 504 Gateway errors when running CLI tests.

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

Resolved: We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers have observed degradation affecting CLI SCA tests for customers.

Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.

The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.

Resolved: We have observed no further impact during our monitoring period.

The Snyk Incident Response has been stood down.

Monitoring: Snyk engineers have completed mitigation efforts, and the environment is currently being monitored.

Identified: Our engineering team has identified the root cause of the issue and is actively taking steps to resolve it.

Investigating: Our engineers are investigating a recurrence of the incident on 6th October (see here). We are again seeing failures affecting CLI tests for customers within our app.snyk.io environment.

Customers may experience 504 Gateway errors when running CLI tests.

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

Resolved: We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers have observed degradation affecting CLI SCA tests for customers.

Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.

The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.

Resolved: We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers have observed degradation affecting CLI SCA tests for customers.

Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.

The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.

Resolved: Services have remained stable throughout our monitoring period, and the Snyk Incident Response has been stood down.

Monitoring: Our engineers have applied a fix, and services have recovered across our app.au.snyk.io environment.

If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run.

We are continuing to monitor performance closely and will post here if anything changes.

Investigating: Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our app.au.snyk.io environment.

Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed.

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

Resolved: We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers have observed degradation affecting CLI SCA tests for customers.

Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.

The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.

Resolved: Services have remained stable throughout our monitoring period, and the Snyk Incident Response has been stood down.

Monitoring: Our engineers have applied a fix, and services have recovered across our app.au.snyk.io environment.

If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run.

We are continuing to monitor performance closely and will post here if anything changes.

Investigating: Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our app.au.snyk.io environment.

Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed.

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

Resolved: We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers have observed degradation affecting CLI SCA tests for customers.

Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.

The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.