Snyk outage history

Snyk engineers are observing a degradation affecting Snyk Test in the SNYK-US-01 multi-tenant environment. Customers may observe timeouts and errors with Snyk Test. Our engineers are aware, and the incident response has been enacted.

We have identified that the failures are linked to elevated load on a backend data service in our SNYK-US-01 environment. This is causing Snyk Test and other dependency and container scan operations to fail, time out or return errors. Following further investigation, we have confirmed that Snyk Code and Snyk IaC are not affected. The impact is limited to Snyk Open Source and Snyk Container. Our engineers are applying mitigations to restore normal service. We will keep you updated with our progress.

Snyk engineers have mitigated the underlying cause of the Snyk Test failures. Tests are now succeeding within normal durations across the environment. Snyk Engineers will continue monitoring system stability.

Services have remained stable throughout the weekend, and we do not expect any further impact. The Snyk Incident Response has been stood down.

Snyk Support portal is experiencing a degradation of service. Users may not be able to log in to the portal at support.snyk.io to create or view support cases. Other options to create support cases may also be impacted. We have identified that this appears to be due to a related incident on the 3rd party provider. We will monitor and provide updates as they are available.

The 3rd party provider has implemented a fix, and initial testing indicates that it is successful. The Snyk Support portal should now be available, however we'll keep monitoring for a short period to ensure full service is maintained

There have been no further interruptions to our service, declaring the incident as resolved.

Snyk Engineers identified a degradation that affected Snyk Container in SNYK-US-01 Multi-Tenant environment. Customers may experience intermittent errors when executing imports. Our engineers are aware, and recovery efforts are underway.

Our engineers are continuing work to restore full service to Snyk Container within our SNYK-US-01 environment. Customers may continue to experience intermittent errors when importing projects. Retrying the operation may succeed. We will keep you updated with our progress.

Our Engineers have taken steps to mitigate the impact, and we are seeing service improve for Snyk Container within our SNYK-US-01 environment. Customers may still experience the occasional error when importing projects. Retrying the operation may succeed. We will continue to monitor throughout the weekend and will post an update on Monday, 26th October.

We have had to reverse the mitigation applied earlier to protect other services in the SNYK-US-01 environment. As a result, customers may again experience intermittent errors when importing projects. Retrying the operation may succeed. Our engineers are continuing work to restore full service, and we will keep you updated with our progress.

Services have recovered, and Snyk Container is operating normally in SNYK-US-01 . Services have remained stable throughout our monitoring period. The Snyk Incident Response has been stood down.

Snyk engineers are investigating reports of "Invalid Credential" errors affecting Snyk Code PR checks across all environments. Our incident response team has been activated, and we are working to resolve the issue as quickly as possible.

Our engineering team is continuing to investigate the incident. In addition to blocked PR checks, customers may experience delays with recurring tests, and other features utilizing the Workspaces Service may be affected. Current impact appears to be isolated to GitHub and GitHub Enterprise workspaces. We will provide further updates as the investigation progresses.

Our engineering team has identified the root cause of the incident and is preparing a fix. We do not yet have an estimated time for deployment, but we will share updates as soon as they become available.

Snyk engineers have deployed a fix across all environments, and all services have returned to normal operation. We will continue monitoring system stability to ensure the issue is fully resolved.

Post-mitigation monitoring confirms that all Snyk services are operating normally and remain stable. The incident response team has stood down, and this incident is now resolved.

Snyk Engineers are investigating an issue affecting Snyk Code performance including scans and PR checks in the SNYK-US-02 environment. The Snyk Incident Response has been enacted.

We are continuing to investigate this issue.

A fix has been successfully deployed and all systems are now operating as expected. Our team will continue to monitor the environment to ensure stability.

All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.

Snyk engineers are investigating degraded performance affecting PR Checks and Imports in the multi-tenant SNYK-US-01 environment. The incident response protocol has been activated. The issue has been identified, and mitigation steps are currently underway.

Snyk engineers have deployed a mitigation, and PR checks are currently operating within normal parameters. The backlog of imports is being actively processed, and we are closely monitoring both the queue and the overall health of the environment.

The import backlog has been processed. Services are operating within normal ranges. Snyk engineers continue to monitor the environment.

All services remain operational during the monitoring period. The Snyk Incident response has been stood down.

We are aware of an incident affecting the GitLab Cloud service, which is impacting Git operations. As a result, customers using GitLab Cloud integrations may see actions such as imports and scans in Snyk Open Source and Snyk Code time out or fail. We will share an update as soon as there is more information.

GitLab have reported that services are recovering, and Snyk integration actions are working normally again. If any operations failed earlier, they should now complete as normal when re-run. We will continue to monitor and will post here if anything changes.

GitLab are still monitoring their services, but we have seen no further impact on Snyk integrations in the last 24 hours. This incident has been resolved, and the Snyk Incident Response has been stood down.

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.

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.

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

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.

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

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

We have observed no further impact during our monitoring period. The Snyk Incident Response has been stood down.

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.

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.

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.

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.

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

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

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.

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.

We're no longer observing delays affecting the Issues API V3 service. The Snyk Incident Response has been stood down.

Our Engineers observed a recurrence of the impact reported in our earlier incident . We've deployed a further fix and are monitoring closely to confirm stability before considering this resolved.

During monitoring, we observed a brief recurrence of impact. This has now been resolved, and we're continuing to monitor closely.

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Our Engineers are investigating degradation affecting Snyk Open Source, across our app.snyk.io environment. Customers may see CLI errors on Secrets and dependency graph scans. The Snyk Incident Response has been invoked.

We've identified an increase in impact. Some Secrets PR checks are still showing as failed, despite the underlying scan completing successfully. We're continuing to investigate and will share more as soon as we have it.

We've deployed a fix and are now monitoring closely to confirm full resolution.

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Snyk engineers are investigating an issue affecting Snyk Code flows and Snyk Secrets in the Multi-Tenant US-01 environment. The Snyk Incident Response has been enacted.

Snyk Engineers have identified the root cause and are deploying a fix to production. We will update when the fix is fully deployed.

The fix has been deployed, and Snyk Code tests are completing. We are currently processing the remaining backlog.

A fix has been successfully deployed, resolving the issue. All systems are operating as expected, and our team continues to monitor the environment to ensure stability.

All services remain stable. The incident is now resolved.

Our Engineers are investigating degradation which is impacting Recurring Tests. Customers may observe that daily Recurring Tests have not executed as scheduled for yesterday's (17th September) run. We expect these tests to be executed during today's schedule. Weekly recurring tests are scheduled as expected. The Snyk Incident Response has been invoked.

We're continuing to monitor today's scheduled Recurring Tests closely to ensure there are no further delays. We'll share another update once we can confirm all tests have completed successfully.

No further delays have been observed, and all Recurring Tests have now been completed as expected. The Snyk Incident Response has been stood down.

We're currently investigating reports of degradation affecting some Imports and PR Checks across the Snyk platform. Full impact analysis is currently underway, we will provide further details as the incident progresses. The Snyk Incident Response has been invoked.

Our investigations remain ongoing. We will keep you updated with our progress.

Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.

Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.

A fix has been applied, and error rates connecting to our broker servers have dropped back to normal levels. Connections via brokered integrations are functioning as expected. We are continuing to monitor performance to ensure full stability.

The fix is deployed across all environments. We're continuing to monitor for any further stability issues.

No further impact has been observed throughout the monitoring period. The Snyk Incident Response has been stood down.

Our engineering team has detected an issue impacting customers using brokered integrations. Some customers are currently reporting errors when attempting to connect to our broker servers. At this time, only a subset of customers is affected. We are actively measuring the impact of this service degradation and investigating the root cause. We will provide another update as soon as we have more information.

A fix has been applied, and error rates connecting to our broker servers have dropped back to normal levels. Connections via brokered integrations are functioning as expected. We are continuing to monitor performance to ensure full stability.

Our Engineers identified a degradation that affected Snyk Code. Customers may have observed errors with CLI testing between 08:55 UTC and 11:20 UTC.

The issue has been mitigated, and service has been restored.