Snyk Outage History

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

We have identified an issue causing degraded performance and response delays on Issues API V3 for a subset of users. 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.

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.

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.

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

Snyk Engineers have identified the root cause and are working on a mitigation.

Snyk is currently experiencing elevated error rates (up to 20%) due to an ongoing third-party incident with GitHub. Features dependent on GitHub integration are affected. We are actively monitoring the situation and will provide updates as GitHub resolves the issue.

Snyk engineers have identified an issue affecting SAST Push tests in the Snyk-US-01 Multi-tenant environment. The root cause has been identified, and mitigation efforts are underway.

Snyk Engineers are deploying a fix for the SAST Test Failures. Currently, Snyk Code (SAST) results are not updating in the UI. Projects are displaying issue counts and findings from their previous test rather than the latest scan. New scan results are being captured, and no data has been lost; affected projects will display current results once the fix is deployed and the next successful test completes.

Our engineering team have identified the root cause and are working on deploying a fix. We will keep you updated on our progress.

We have identified an issue affecting Workspaces Services and Code PR checks within the SNYK-EU-01 multi-tenant environment. Please note that Open Source and License features are unaffected and remain fully operational. Our engineering team is actively working on a resolution.

We are aware of intermittent failures affecting a subset of public-facing API routes. Our team has identified the issue and is actively deploying a mitigation. We will provide an update once the issue is resolved.

Snyk Engineers have identified the issue that was causing the degradation and are currently working on implementing a fix. We will provide updates as they become available.

Our engineering team is currently investigating reports of degraded performance in the SNYK-US-01 US Multi-tenant environment (app.snyk.io). We are actively working to isolate the cause and will provide updates as we the investigation progresses.

Snyk engineers are continuing their investigation. We have applied initial mitigation steps and are seeing signs of recovery, though some performance degradation persists. Our teams remain focused on a full resolution, and we will share another update shortly.

Snyk Engineering is continuing to investigate the issue. Mitigation steps are progressing but will take some time to be fully effective. Current scope of effect: * Customers may notice increased latency across the Snyk UI platform, as well as API, CLI, SCM based projects and PR Checks. * Due to the increased latency, some tests may be observed to timeout and fail. * There is currently no known observed impact to analytics and reporting. This issue is not affecting other environments. We will continue to work on mitigation efforts and provide updates as the issue progresses.