Snyk Status

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Identified: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

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

Monitoring: 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

Identified: 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.