Snyk

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

1. investigating 2026-10-20 16:33 UTC

   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.

2. investigating 2026-10-20 17:16 UTC

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

3. identified 2026-10-20 17:53 UTC

   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.

4. monitoring 2026-10-20 18:22 UTC

   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.

5. resolved 2026-10-20 19:31 UTC

   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.

Excerpts are shortened. Read the full incident on Snyk's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-17 01:43 UTC

   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.

2. investigating 2026-10-17 02:05 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-17 02:06 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-10-17 02:30 UTC

   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.

5. resolved 2026-10-19 22:02 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk API & Web, Snyk Secrets

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-15 20:39 UTC

   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.

2. monitoring 2026-10-15 21:04 UTC

   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.

3. monitoring 2026-10-15 21:09 UTC

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

4. resolved 2026-10-15 21:47 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-13 07:32 UTC

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

2. monitoring 2026-10-13 08:10 UTC

   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.

3. resolved 2026-10-14 08:53 UTC

   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.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-08 10:03 UTC

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

2. monitoring 2026-10-08 11:24 UTC

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

3. resolved 2026-10-09 07:08 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-07 15:04 UTC

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

2. identified 2026-10-07 15:50 UTC

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

3. monitoring 2026-10-07 16:29 UTC

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

4. resolved 2026-10-08 17:42 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. monitoring 2026-10-06 22:53 UTC

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

2. resolved 2026-10-06 23:58 UTC

   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.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 14:37 UTC

   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.

2. identified 2026-10-06 16:14 UTC

   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.

3. monitoring 2026-10-06 18:05 UTC

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

4. resolved 2026-10-07 12:34 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-10-03 19:49 UTC

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

2. monitoring 2026-10-06 06:32 UTC

   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.

3. resolved 2026-10-08 12:56 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Secrets

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. monitoring 2026-09-28 14:26 UTC

   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.

2. monitoring 2026-09-29 12:53 UTC

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

3. resolved 2026-10-01 12:33 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Secrets

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-28 07:51 UTC

   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.

2. investigating 2026-09-28 08:36 UTC

   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.

3. monitoring 2026-09-28 11:15 UTC

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

4. resolved 2026-09-28 12:15 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-21 14:43 UTC

   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.

2. identified 2026-09-21 16:10 UTC

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

3. identified 2026-09-21 16:47 UTC

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

4. monitoring 2026-09-21 17:33 UTC

   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.

5. resolved 2026-09-21 18:07 UTC

   All services remain stable. The incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-18 06:40 UTC

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

2. monitoring 2026-09-18 11:05 UTC

   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.

3. resolved 2026-09-21 06:02 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

1. investigating 2026-09-09 14:37 UTC

   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.

2. investigating 2026-09-09 15:29 UTC

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

3. identified 2026-09-09 15:47 UTC

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

4. resolved 2026-09-09 17:02 UTC

   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.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. monitoring 2026-08-30 14:32 UTC

   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.

2. monitoring 2026-08-31 15:02 UTC

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

3. resolved 2026-09-02 06:42 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-30 12:20 UTC

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

2. resolved 2026-08-30 13:31 UTC

   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.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-20 12:42 UTC

   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.

2. resolved 2026-08-20 12:43 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

1. investigating 2026-08-19 18:30 UTC

   Snyk Engineers are investigating an issue affecting customers who are installing the GitHub Cloud App. Customers who already have the app installed are not impacted.

2. identified 2026-08-19 18:56 UTC

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

3. resolved 2026-08-19 19:35 UTC

   Snyk engineers have deployed a fix and have confirmed the GitHub Cloud App installation is working as expected. The incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk API & Web, Snyk API & Web, Snyk API & Web, Snyk API & Web

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. identified 2026-08-17 15:01 UTC

   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.

2. resolved 2026-08-17 19:42 UTC

   Snyk engineers have confirmed service recovery. The incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk IaC, Snyk Open Source

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-08-11 14:54 UTC

   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.

2. identified 2026-08-11 16:05 UTC

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

3. monitoring 2026-08-11 18:52 UTC

   Snyk engineers have deployed a fix, and all services have been restored. We are monitoring the environment to ensure stability.

4. resolved 2026-08-11 21:55 UTC

   All systems remain stable during the monitoring period after the mitigation was implemented. The incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk API & Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-08-05 19:26 UTC

   Snyk engineers are observing increased latency affecting Test Services in the SNYK-US-01 environment. Our Incident Response process has been enacted. Our engineers are investigating the issue. Thank you.

2. investigating 2026-08-05 20:51 UTC

   Snyk engineers remain engaged under an incident footing. Our engineers are implementing mitigation measures to mitigate the impact. Further updates to follow.

3. monitoring 2026-08-05 22:54 UTC

   Snyk engineers have implemented a mitigation. Test latency has returned to normal ranges. Our engineers are monitoring the environment.

4. resolved 2026-08-07 07:29 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-08-05 04:28 UTC

   We are investigating degraded performance on the snyk Vuln DB page, security.snyk.io Currently, the /vuln page is working, but some individual vulnerability reports are returning 502 responses. Testing and Reporting is not affected.

2. monitoring 2026-08-05 04:57 UTC

   We have implemented a fix. Service has returned to normal levels. We are monitoring for stability

3. investigating 2026-08-05 05:34 UTC

   Monitoring has shown that the fix was only temporarily successful and the issue has recurred. We are continuing to investigate.

4. investigating 2026-08-05 10:00 UTC

   Our investigations into the root cause remain ongoing. We will keep you updated on our progress.

5. monitoring 2026-08-05 12:51 UTC

   A fix has been deployed to production, and we're closely monitoring the system.

6. resolved 2026-08-05 13:35 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-08-04 13:07 UTC

   We've identified an issue affecting all .NET project workflows, including import, retest, and pull request checks. The Snyk Incident Response has been invoked, and our engineering team are investigating.

2. identified 2026-08-04 13:44 UTC

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

3. resolved 2026-08-04 14:29 UTC

   Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-07-23 19:59 UTC

   We are currently experiencing partial degradation for some tests across all product lines. We will provide updates as they become available.

2. monitoring 2026-07-23 20:59 UTC

   The system has recovered and Snyk Engineers are currently monitoring the platform.

3. resolved 2026-07-24 10:34 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 14:56 UTC

   We had a brief recurrence of yesterday's incident , affecting customers in two short windows: 14:27–14:36 UTC 14:37–14:42 UTC Service has now recovered. Customers should re-import any imports that errored or failed during these windows.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. monitoring 2026-07-22 09:41 UTC

   From 09:08 to 09:30 UTC customers may have experienced errors when executing imports for Snyk Open Source or Snyk Container. Additionally, some customers may have experienced issues when attempting to view Project details for these project types. The Snyk Incident response was...

2. resolved 2026-07-23 07:09 UTC

   No further impact was observed during our monitoring period. Customers should re-import any imports that errored or failed during the outage window. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk API & Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-07-14 18:18 UTC

   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.

2. monitoring 2026-07-14 18:58 UTC

   Our engineers have identified the root cause and deployed a mitigation, returning services to fully operational status. We will continue to monitor the environment to ensure stability.

3. resolved 2026-07-14 20:12 UTC

   All services remain stable. The incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk API & Web

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-07-14 17:56 UTC

   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.

2. resolved 2026-07-14 20:14 UTC

   A fix has been deployed, and all systems are performing normally. This incident has been marked as resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Open Source

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-07-10 13:41 UTC

   We are currently experiencing partial degradation for some tests including dep graph with risk score and/or reachability, Secrets, SBOM and SCM SAST. We will provide updates as they become available.

2. identified 2026-07-10 15:45 UTC

   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.

3. monitoring 2026-07-10 19:14 UTC

   Snyk Engineers have implemented a fix and we are currently monitoring the outcomes. We will provide updates as they become available.

4. resolved 2026-07-10 20:08 UTC

   The incident has been resolved after we have monitored the overall performance.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source, Snyk Learn, Snyk API & Web

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-06-24 21:39 UTC

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

2. monitoring 2026-06-24 22:14 UTC

   Snyk engineers have identified the issue and deployed a mitigation to restore service. The team is now actively monitoring the environment to ensure continued stability.

3. monitoring 2026-06-25 12:14 UTC

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

4. resolved 2026-06-25 12:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. identified 2026-06-22 22:21 UTC

   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.

2. identified 2026-06-22 23:06 UTC

   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.

3. identified 2026-06-23 00:52 UTC

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

4. monitoring 2026-06-23 02:34 UTC

   Mitigation steps have been completed and are showing immediate improvements in success rate and latency, and are burning down the backlog. We will maintain a period of monitoring for continued stability.

5. monitoring 2026-06-23 10:53 UTC

   We are continuing our monitoring throughout today to ensure services remain stable.

6. resolved 2026-06-24 21:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk Code, Support Portal, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Learn, Snyk Learn, Snyk Learn, Snyk Learn, Evo by Snyk, Evo by Snyk, Evo by Snyk, Evo by Snyk

1. investigating 2026-06-19 23:15 UTC

   We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security...

2. monitoring 2026-06-22 22:12 UTC

   We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security...

3. resolved 2026-07-08 15:26 UTC

   Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data...

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code

1. investigating 2026-06-19 20:13 UTC

   We are currently experiencing an unexpected issue affecting our SAST scans and certain API triggered tests. Our engineering team is actively monitoring the situation to fully understand the impact and isolate the root cause. While we work to restore full functionality, some...

2. resolved 2026-06-19 22:13 UTC

   The issue affecting SAST scans and API-driven automated tests has been successfully resolved, and all services have returned to normal status. Our engineering team identified the root cause as an expensive SQL query that triggered database degradation. The query has been...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. monitoring 2026-06-17 23:31 UTC

   Our engineers are investigating degradation affecting app.snyk.io. This impacts user-initiated events such as imports, manual retests, PR checks, CLI, API endpoints on the app.snyk.io environment. Other environments are unaffected. The Snyk Incident Response has identified and...

2. resolved 2026-06-18 10:59 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-06-16 04:52 UTC

   Engineering have detected a delay in data affecting Issue API results on the app.snyk.io environment. Project data, UI based Reporting, and Export API are not affected. We are investigating and will report back here with any updates.

2. investigating 2026-06-16 18:21 UTC

   Snyk Engineering has identified a data freshness delay within Issues Reporting. Our teams are actively investigating the root cause, and we will provide further updates as the situation progresses.

3. investigating 2026-06-18 15:00 UTC

   We are no longer observing delays affecting our reporting data freshness. However, the Issues API data freshness remains delayed, and our investigation into this is ongoing. We will provide a further update as soon as we have more information.

4. resolved 2026-06-22 10:12 UTC

   Both the Issues API data freshness and reporting data freshness have been fully restored and are operating normally. Our investigation is now complete, and the Snyk Incident Response has been stood down. We apologise for any inconvenience this may have caused and thank you for...

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-06-09 11:22 UTC

   Our engineers are investigating degradation affecting app.snyk.io. Customers may experience continuous loading and/or slowness when accessing the Snyk UI. This may also impact the testing of projects. The Snyk Incident Response has been invoked.

2. monitoring 2026-06-09 12:15 UTC

   A fix has been implemented, and initial signs are positive. We will continue to monitor to ensure services fully recover and remain stable.

3. resolved 2026-06-09 14:14 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Support Portal

1. identified 2026-06-08 15:47 UTC

   Please note that the ability to create or reply to cases via email has been temporarily turned off. If you need to log a new issue or update an existing case, please do so directly through the ticketing portal. We will let you know as soon as email functionality is restored....

2. monitoring 2026-06-09 14:13 UTC

   We have re-enabled the email-to-case feature, allowing customers to create and reply to cases via email. Monitoring is now underway to ensure the services remains stable.

3. resolved 2026-06-10 06:22 UTC

   Services have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Container, Snyk Open Source

1. monitoring 2026-06-02 09:37 UTC

   During our recent Recurring Tests, we observed that some email notifications were not sent to alert customers to new vulnerabilities. All Recurring Tests have completed successfully, and customers can view their results within the Snyk UI. We have now implemented a fix. Email...

2. monitoring 2026-06-02 12:47 UTC

   We are observing delays affecting some Daily Recurring Tests as a result of our mitigation actions.

3. resolved 2026-06-04 06:39 UTC

   We are no longer observing delays affecting Recurring Tests. All tests have caught up, and services are operating normally. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code

1. resolved 2026-06-01 14:17 UTC

   Between 12:03 and 12:04 UTC today (1st June 2026), Snyk experienced a brief period of degradation affecting Snyk Code scans and custom Rule Extension tests. This impacted scans run via the CLI, IDE plugins, CLI uploads, as well as PR Checks. Services have now fully recovered....

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

Names an upstream provider: GitHub.

1. investigating 2026-05-23 08:43 UTC

   We are currently investigating reports of intermittent failures affecting our GitHub Cloud App integration, specifically impacting repository scans, project imports, and Pull Request status checks. During this time, customers may see failures on PR checks, recurring tests and...

2. resolved 2026-05-23 19:46 UTC

   The intermittent issues affecting repository scans, project imports, and Pull Request status checks have been fully resolved. The root cause was an upstream degradation with GitHub Cloud app installation token authentication, which has now been mitigated on the GitHub side (ref:...

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

1. identified 2026-05-22 17:26 UTC

   Snyk engineers have identified the root cause of degraded performance affecting Open Source across all environments, leading to PR Checks and recurring test failures. A fix is currently being rolled out globally. We will provide further updates as the deployment progresses.

2. resolved 2026-05-22 19:14 UTC

   Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Open Source

1. identified 2026-05-22 02:29 UTC

   Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks. The investigation is ongoing...

2. identified 2026-05-22 14:52 UTC

   Our Engineers have confirmed that the US-01 (app.snyk.io) environment has shown no further degradation following re-deployment and appears to be stable. Investigation into the AU-01 (app.au.snyk.io) environment is still ongoing, and we will provide a further update as we...

3. monitoring 2026-05-25 23:26 UTC

   Our Engineers have implemented a fix, and we're no longer observing the degradation on the AU-01 (app.au.snyk.io) environment. We will continue to monitor for ongoing stability.

4. resolved 2026-05-26 13:20 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-05-21 11:37 UTC

   We're currently investigating degradation affecting our app.snyk.io environment. Customers may experience slowness and/or failures affecting project imports and recurring tests. The Snyk Incident Response has been invoked.

2. identified 2026-05-21 12:22 UTC

   Success rates have now recovered. However, the environment remains under close monitoring while our investigation into the root cause and further mitigations continues. We will keep you updated as we progress.

3. identified 2026-05-21 14:56 UTC

   A fix has been deployed, and initial signs are positive. We will continue to monitor service to ensure services remain stable.

4. resolved 2026-05-21 17:16 UTC

   All services remain stable after the mitigation. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Open Source

1. investigating 2026-05-19 17:08 UTC

   Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures—including Recurring Tests—within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.

2. investigating 2026-05-19 20:09 UTC

   We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will...

3. resolved 2026-05-20 08:06 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

1. investigating 2026-05-19 14:19 UTC

   We're currently investigating an issue affecting the Jira integration . Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform. The Snyk Security In Jira Cloud integration is unaffected. The...

2. identified 2026-05-19 15:35 UTC

   Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.

3. monitoring 2026-05-19 19:47 UTC

   A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.

4. resolved 2026-05-20 10:51 UTC

   We are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source

1. investigating 2026-05-19 05:29 UTC

   Current scope appears to be: over 630 malicious package versions across more than 315 unique packages, with the AntV suite heavily impacted. This incident relates to compromised third-party open source packages in the npm ecosystem. There is no indication that Snyk systems,...

2. investigating 2026-05-19 07:55 UTC

   Update: Snyk is continuing to investigate and respond to the ongoing supply chain compromise of @antv and other packages. Affected packages: Current findings indicate that multiple npm packages have been identified as affected, including packages within the @antv/* namespace and...

3. investigating 2026-05-19 08:45 UTC

   The Snyk Trust Center has been updated.

4. investigating 2026-05-19 08:51 UTC

   Customers can now assess potential impact in the Snyk app by visiting: Analytics → Reports → Zero-Day → Active Security Incident Assessment for Antv Supply Chain Compromise - May 2026 Please continue to refer to the Snyk Trust Center for the latest official updates and customer...

5. investigating 2026-05-19 09:13 UTC

   Our blog post is now available: Mini Shai-Hulud Hits AntV

6. investigating 2026-05-19 10:44 UTC

   The Compromised Packages list is now available at https://security.snyk.io/antv-supply-chain-compromise-may-2026

7. investigating 2026-05-19 21:39 UTC

   We are continuing to investigate this issue.

8. resolved 2026-05-20 14:57 UTC

   Customer Projects: This Status Page incident, “Supply Chain Compromise on AntV,” was opened to share customer-facing updates regarding a third-party compromise within the AntV ecosystem. Because AntV is a Snyk-supported ecosystem, we used this incident to alert customers that...

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-05-18 12:12 UTC

   Snyk Engineers have identified degraded performance in the Multi-Tenant US-01 environment (app.snyk.io), affecting multiple services. The investigation is ongoing under the Snyk Incident Response process.

2. investigating 2026-05-18 14:57 UTC

   Our investigations into the root cause remain ongoing. We will keep you updated with our progress.

3. investigating 2026-05-19 11:22 UTC

   Our investigation into the root cause remains ongoing. We are currently seeing a reduced frequency of the issue and are continuing to monitor performance closely. Further updates will be provided as our investigation progresses.

4. resolved 2026-05-19 14:27 UTC

   We have identified and deployed a fix restoring normal service. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk Code, Snyk Open Source

Names an upstream provider: GitHub.

1. investigating 2026-05-18 11:19 UTC

   We're currently investigating intermittent degradation affecting PR events. This is affecting GitHub, GitLab, Bitbucket Cloud and Bitbucket Server integrations. The Snyk Incident Response has been invoked.

2. resolved 2026-05-18 12:53 UTC

   Following our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution details, please follow: Service Degradation on US-01...

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-05-13 14:49 UTC

   Snyk engineers are investigating degraded performance with the Reporting PDF in the Snyk-US-01 multi-tenant environment. Customers may observe longer generation times or failures to generate reports.

2. resolved 2026-05-13 19:01 UTC

   Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

Started during GitHub: Incident with high errors on Git Operations.

1. resolved 2026-05-11 14:41 UTC

   The upstream issues at GitHub have been resolved. Our engineering team has verified full recovery, and all Snyk GitHub integrations are operating normally. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-05-08 21:51 UTC

   CLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-05-07 08:30 UTC

   Our Engineers deployed a fix, and we're no longer observing delays affecting the Issues API data freshness. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Affected: Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

1. investigating 2026-05-06 15:32 UTC

   Snyk engineers have noticed delays in a small percentage of daily recurring tests in the Multi-Tenant Synk-US-01 (app.snyk.io) environment. The impact is limited to daily tests; weekly tests remain unaffected. Snyk engineers are investigating the issue.

2. investigating 2026-05-07 13:19 UTC

   We are continuing to investigate the root cause of the delays. Customers may still experience delays affecting a small percentage of daily recurring tests.

3. identified 2026-05-08 13:02 UTC

   We have identified the root cause of the delays and implemented mitigations. Some customers may still experience delayed daily recurring tests while these changes fully propagate We will continue to monitor the situation to ensure the mitigations have been successful.

4. identified 2026-05-11 14:19 UTC

   We continue to see improvements as a result of the mitigation actions taken. However, we will monitor to ensure services fully recover.

5. resolved 2026-05-12 07:20 UTC

   We are no longer observing delays affecting our Recurring Tests as a result of the mitigation actions taken. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-29 20:00 UTC

   We've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

Started during GitHub: Incident with multiple GitHub services.

1. resolved 2026-04-23 17:56 UTC

   Upstream GitHub issues are resolved. Snyk engineers have verified system recovery and confirmed that no further impact remains. Incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-05-05 12:23 UTC

   We are no longer observing degradation affecting Recurring Tests. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-20 16:05 UTC

   A fix has been implemented for the Snyk Test failures. Service for Code Scans (SAST) has returned to normal operations.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-17 23:34 UTC

   This outage has now been resolved and all systems are operational.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-20 16:04 UTC

   A fix has been implemented for the Snyk Code Test failures. The service for Code Scans (SAST) has returned to normal operations.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-16 09:15 UTC

   We've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-15 09:12 UTC

   There have been no further issues observed throughout the monitoring period, and we're confident the issue has now been resolved. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-09 19:17 UTC

   No further issues have been observed during our monitoring period across the Multi-Tenant US-01 environment (app.snyk.io). The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-07 17:28 UTC

   Snyk engineers have mitigated the intermittent failures. Snyk is no longer observing any failed requests or elevated response times. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-04-01 12:57 UTC

   We are no longer experiencing delays affecting recurring tests. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

1. resolved 2026-03-31 13:02 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-24 17:45 UTC

   Our Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-25 09:00 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-30 15:39 UTC

   Services remain stable during the monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-17 14:16 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-16 15:26 UTC

   Our Engineers have deployed, and we are no longer observing issues affecting the sign-up process. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-13 12:13 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-16 11:58 UTC

   We are no longer observing delays affecting our daily recurring tests, and all backlogs have now cleared. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-17 14:43 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-12 03:32 UTC

   This incident has been resolved. Any PR Checks that have been hanging should be closed and reopened.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-09 12:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-06 05:16 UTC

   All services have recovered and are operating normally after the third party took mitigation steps to restore services.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-03 20:13 UTC

   All services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-04 15:13 UTC

   The Snyk engineering team has implemented the fix in the v1.1303.1 CLI release. You can find more details at the following link: https://github.com/snyk/cli/releases/tag/v1.1303.1. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-03 01:36 UTC

   No further recurrence has been detected. Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-03-03 17:01 UTC

   Snyk engineers successfully deployed the fix across all environments. Services are functioning normally, and the Snyk Incident Response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-24 15:14 UTC

   Our Engineers have identified the root cause and managed to immediately implement a fix that addressed the issue. The Inventory data is now up to date.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-20 01:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-17 16:04 UTC

   Our Engineers have completed their initial investigation, during which we have established that there was no impact on our customer base. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-13 15:46 UTC

   Our Engineers have implemented a fix to ensure no further impact to services. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-11 21:40 UTC

   Snyk engineers have confirmed that all services are restored after mitigation activities were completed. The Snyk incident response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-20 17:39 UTC

   Snyk engineers have been monitoring the environment and are no longer seeing delays affecting our daily recurring tests. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

Started during GitHub: Copilot Policy Propagation Delays.

Started during GitHub: Incident with Pull Requests.

Started during GitHub: Notifications are delayed.

1. resolved 2026-02-09 17:43 UTC

   All services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-02-02 07:08 UTC

   Our Engineers have implemented a fix, and are no longer observing delays affecting Recurring Tests. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-29 09:36 UTC

   Our Engineers have implemented a fix and are confident this incident is now resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-28 19:48 UTC

   Snyk engineers monitored the environment after the mitigation was deployed and have observed normal operations. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-28 11:54 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-26 13:13 UTC

   Our Engineers are aware of the degradation affecting our Issues API between 11:45 and 12:34 UTC. Customers may have experienced degradation affecting the Issues API during this window. Services have now recovered, and we do not expect any further impact.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

Started during GitHub: Disruption with some GitHub services.

1. resolved 2026-01-22 15:24 UTC

   GitHub have confirmed service restoration, and all Snyk services have recovered. The Snyk incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-23 08:02 UTC

   All affected customers should upgrade to Universal Broker version 5.4.9 to restore service. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-23 09:08 UTC

   Affected customers can restore service by upgrading to the latest stable Snyk CLI release: v1.1302.1. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-19 09:10 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-16 21:25 UTC

   Snyk engineers have been monitoring the environment and confirmed that all systems are operating within normal baselines. The incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-13 14:25 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-07 14:27 UTC

   Event queues have normalised, confirming that all pending imports have completed. We are now observing standard processing times. The Snyk Incident Response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-29 11:00 UTC

   Between 10:22 and 10:46 UTC on Monday, December 29th, Snyk experienced a partial degradation of backend systems that calculate Reachability for Snyk Code projects. This means a subset of projects tested during this time will be missing the reachability data. This data will be...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-28 07:48 UTC

   The fix has been successfully implemented, and we are no longer observing any degradation in the Maven scans. Our Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-25 02:23 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

1. resolved 2025-12-23 16:48 UTC

   Our Engineers have observed no further impact, this Incident is now Resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2026-01-06 07:14 UTC

   This incident has now been resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-18 13:54 UTC

   We have identified the root cause of the incident and established that this affects only a small subset of customers. We will be reaching out to those customers in due course. However, as a workaround, customers can re-import the affected projects. The Snyk Incident Response has...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-08 13:51 UTC

   Our Engineers have observed no further impact during our monitoring period. We can confirm that our Snyk Code product would have also experienced degradation as a result of this incident. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-12-02 20:45 UTC

   The Snyk Incident response has been stood down. This incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-28 14:59 UTC

   The fix has been successfully implemented, and we are no longer observing any degradation in the Snyk UI. Our Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-18 22:34 UTC

   All systems are operating normally. The Snyk incident response has been stood down, and this incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-13 08:32 UTC

   Services have fully recovered and remained stable. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-11 19:47 UTC

   This incident has been resolved and all our services are now performing as expected.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-10 20:54 UTC

   Affected services are back to normal. There was a small delay in the full propagation of the fix from the third-party vendor. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-08 23:16 UTC

   We are no longer observing errors since implementing the fix. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-29 17:27 UTC

   Snyk Engineers have deployed a fix. All services have returned to normal operations, and the Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-27 17:05 UTC

   Snyk engineers have deployed a fix addressing the Snyk Code Test service issue. Failed tests observed during the incident can be re-run. The incident response has been concluded.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-11-20 14:45 UTC

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

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-17 14:20 UTC

   Our Engineers have released a fix which has resolved the cause of the degradation. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-16 11:25 UTC

   Success rates have returned to normal and remain steady. We're confident the incident has now been resolved. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-15 15:37 UTC

   Snyk engineers have monitored the situation and observed no further issues. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-15 01:11 UTC

   Our Engineers have confirmed all services are operating normally. The Snyk incident response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-11 04:44 UTC

   We have not observed any further impact since deploying the fix. Snyk's incident response is being stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-10 08:21 UTC

   Our Engineers are aware of degradation which affected our app.snyk.io environment between 06:13 UTC and 07:36 UTC. A fix was implemented to resolve the degradation. During the outage window, customers may have experienced service degradation, affecting PR Checks and API related...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-09 16:40 UTC

   All services are operating within normal ranges. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-03 17:00 UTC

   Snyk Engineers have completed the emergency maintenance and all systems are operational.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-29 17:35 UTC

   All systems remain operational. This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-10-03 14:10 UTC

   Our Engineers have now deployed the fix to all Snyk environments, resolving the incident. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-29 13:41 UTC

   Our Engineers have implemented a fix resolving the issue. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-25 01:21 UTC

   Upstream service has updated their status that a fix is deployed and they are monitoring. We have not detected any anomalous customer impact to our services during this time.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-12 17:20 UTC

   Our engineers have confirmed that the backlog has been cleared and all services are operating normally. The Snyk Incident Response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-12 17:18 UTC

   Our engineers have confirmed that the backlog has been cleared and all services are operating normally. The Snyk Incident Response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-08 08:06 UTC

   No additional issues were observed during our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-09-03 00:58 UTC

   We have identified the issue and applied a mitigation. Snyk Assist is now available.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-28 14:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-21 06:32 UTC

   Services have remained stable throughout our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-20 08:37 UTC

   Services have remained stable throughout our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-18 20:22 UTC

   Snyk engineers have deployed a fix, and it has been verified that the fixes are now displaying. The incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-13 16:30 UTC

   Snyk engineers have implemented a fix that restored services for both manual and recurring tests. All systems are functioning normally. The incident response has been concluded.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-08-12 14:03 UTC

   All services have remained stable throughout the monitoring period. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-31 11:59 UTC

   Services have remained stable throughout our monitoring phase. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

1. resolved 2025-07-30 21:17 UTC

   All operations have returned to a normal state after mitigation steps were taken by our engineers. The Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-25 04:50 UTC

   A fix has been deployed and all environments are now loading the report correctly. Snyk Incident Response is being stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-22 15:33 UTC

   Our Snyk Engineers have monitored the fix and are observing that services are operating as expected. The incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-18 18:06 UTC

   This incident has been resolved after confirmation from our third party. Snyk's Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-17 21:15 UTC

   Snyk engineers have monitored the fix, and all services are functioning as expected. The Snyk incident response has been stood down, and the incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-14 15:18 UTC

   Snyk experienced a performance degradation on the platform from 2:20 PM UTC to 2:40 PM UTC. The issue is now resolved, and the platform is fully operational.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-16 08:10 UTC

   All Recurring Tests are now up to date and running as expected. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-09 14:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-01 04:57 UTC

   Atlassian has marked their incident as resolved. We have also observed that Snyk's services have returned to normal operation.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-26 17:21 UTC

   A fix was deployed by Snyk engineers. After monitoring, errors are no longer observed and all systems are operational. The Snyk incident response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-07-04 14:31 UTC

   All Recurring Tests have run as scheduled, and we expect no further impact. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-20 08:57 UTC

   No further issues were observed throughout our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-13 17:11 UTC

   This incident has been resolved after confirmation and verification on our side.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-12 22:13 UTC

   Our Engineering team has deployed a fix to address this issue. Our Monitoring shows no additional issues at this time, this incident is resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-12 19:40 UTC

   This incident has been resolved after confirmation from our third party. Snyk's Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-06-06 10:09 UTC

   The PR Experience backlog has been cleared, and customers should no longer observe delays with PR Comments and Inline Comments. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-29 12:52 UTC

   No additional issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-30 08:24 UTC

   Our Engineers have verified that the issue appears to be resolved. No Snyk intervention was required to restore service. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: GitHub.

Started during GitHub: We're experiencing errors.

1. resolved 2025-05-26 11:53 UTC

   The overall health of our services looks to be stable, transitioning the incident to Resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-23 16:22 UTC

   After monitoring the situation, Snyk Engineers have confirmed the issue is resolved. The Snyk Incident Response team has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-20 14:25 UTC

   Our engineers did not observe any customer impact during the monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-16 18:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-15 00:57 UTC

   This incident has been resolved and there is no further backlog

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-12 14:52 UTC

   A fix has been deployed, and our Engineers have confirmed this has resolved the incident. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-12 12:55 UTC

   Our Engineers have not detected any additional issues during the monitoring period and are confident that the problem has been resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-12 11:42 UTC

   Our Engineers are aware of a momentary drop in success rate affecting our app.au.snyk.io environment. During this time, customers using this environment may have noticed a temporary rise in error rates. A fix has been implemented, and we do not anticipate any further issues...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-08 18:14 UTC

   Our Engineering team has deployed a fix to address this issue and we do not observe any additional errors at this time. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-09 08:08 UTC

   This issue has been resolved, and customers should no longer encounter problems when installing the Bitbucket Cloud app. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-05-09 09:28 UTC

   No further issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-28 10:37 UTC

   No further errors were detected during the monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: Azure.

1. resolved 2025-04-24 08:29 UTC

   Following continued monitoring, we have not identified any further issues and have been unable to reproduce the problem. We are confident that the issue is resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

Names an upstream provider: AWS.

1. resolved 2025-04-15 11:37 UTC

   Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations. Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings. Our Engineers have initiated a rollback to a...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-22 06:58 UTC

   Our Engineers have confirmed that services have remained stable. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-09 18:06 UTC

   Snyk Engineers have confirmed services are operating normally after mitigation steps were taken. No additional impact is expected. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-09 22:53 UTC

   No further repeat of the issue was detected during scheduled re-scans. This incident is resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-01 06:12 UTC

   Support services are fully operational. Snyk incident response is standing down

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-01 13:19 UTC

   Our Engineers have confirmed that the underlying issue has now been resolved. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-04-07 07:11 UTC

   Our Engineers have implemented the remediation actions and are no longer observing issues with scheduled tests. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-21 15:46 UTC

   No further issues have been observed during the monitoring phase, and our Engineers are confident the issue is now resolved. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-24 11:39 UTC

   The fix has been deployed, and our Engineers have observed no further issues. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-20 16:30 UTC

   No further issues have been observed during our monitoring phase. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-24 10:23 UTC

   The fix has been deployed, and our Engineers have observed no further issues. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-19 13:27 UTC

   Our Engineers are confident the incident is now resolved. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-13 18:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-12 17:55 UTC

   We have identified the issue and have taken the required restorative actions. Al services impact have now been restored.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-10 12:08 UTC

   It has been confirmed that data freshness is now back to normal. The incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-14 14:09 UTC

   Our Engineers have deployed an additional fix, resolving the issue in our app.snyk.io environment. All environments are now operating as expected. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-06 13:35 UTC

   Our Engineers are confident that the implemented fix has successfully resolved the issue. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-03-05 20:28 UTC

   Snyk Technical Teams are aware of an issue that affected the Open Source Fix PR UI across all environments. Between 16:20 UTC and 20:00 UTC, customers may have observed a forbidden error when accessing the UI. Snyk Engineers applied a fix, and no further impact was observed. The...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-02-28 17:46 UTC

   We have released a fix for the failures of Imports, Retests and PR Checks for Go Module projects. Our Engineers are no longer observing impact. The incident response process has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-02-20 15:25 UTC

   Our Engineers have not observed any further issues, and they are confident that the steps implemented have resolved the incident. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-02-19 15:41 UTC

   Our Engineers are aware of a degradation of services between 12:54 GMT and 13:45 GMT, which affected our app.us.snyk.io environment. During this window, customers may have experienced errors or timeouts affecting Push Events, PR Checks & Manual Retests. A fix was applied to...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-02-13 13:42 UTC

   Our Engineers have successfully implemented a fix, resolving the incident. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-02-12 01:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-27 09:37 UTC

   During our monitoring period, no additional issues were detected. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-28 07:58 UTC

   No connectivity issues were detected during our monitoring period. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-24 16:23 UTC

   We identified and mitigated the root cause of the intermittent errors following co-op investigations with our cloud services provider. The incident has now been classified as resolved and no additional errors have been identified since approximately 11.20 UTC.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-27 11:42 UTC

   Customers impacted by the issue should update to CLI v1.1295.2. Those using CLI v1.1295.0 are not required to make any changes. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-24 15:30 UTC

   Atlassian has resolved their incident affecting Jira applications. Snyk Engineers have validated that no further impact is being observed. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-23 16:09 UTC

   During our monitoring phase, we have not observed any additional impact. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-22 08:58 UTC

   No further impact was observed during our monitoring phase, and our engineers are confident the incident has now been resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-17 11:29 UTC

   Our engineers have applied a fix that has been confirmed as successful. We do not anticipate any additional impact to Recurring Tests. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-13 13:19 UTC

   Our Engineers have implemented a fix, and testing has verified that the incident has now been resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-10 14:30 UTC

   The fix has been confirmed as successful and no further issues have been observed. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-10 09:49 UTC

   Our engineers identified degradation in our Open Source and Container testing at 08:57 UTC and promptly applied a fix to restore service at 09:10 UTC. Customers using our app.snyk.io environment may have noticed a degradation of CLI, API and SCM testing during this time. The...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2025-01-07 18:21 UTC

   Snyk Engineers have implemented a fix and all services remain stable after a period of monitoring. The Snyk incident response has been stood down. The incident is now resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-24 10:59 UTC

   Our Engineers have successfully implemented a fix to resolve the incident. We do not anticipate any further impact, and the Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-18 17:01 UTC

   Our engineers identified a delay in the update of our Snowflake data share. Customers utilizing the Snowflake data share feature might have noticed that the data was not updated from 16:30 UTC on December 17th until 16:55 UTC today, December 18th. A fix has been applied, and all...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-18 16:36 UTC

   The fix has been successfully applied, and our Engineers are no longer observing any issues The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-12 15:23 UTC

   Our Engineers have implemented a fix which has resolved the issue. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-11 14:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-05 10:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-04 08:00 UTC

   Our engineers have identified and implemented a fix that has proven successful. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-12-05 14:57 UTC

   During our monitoring period, no additional impact was detected. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-28 15:51 UTC

   Our engineers identified a performance issue with our v1 API endpoint between 9:30 and 10:30 UTC. During this period, customers may have experienced latency and/or timeouts with the v1 API endpoint. A fix was implemented by our Engineers to restore normal service.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-27 15:12 UTC

   We identified an issue which affected the AppRisk UI between 12:45 and 13:26 UTC. Customers using app.eu.snyk.io , app.us.snyk.io and app.au.snyk.io may have observed that the AppRisk UI had failed to load between these times. Our Engineers implemented a fix to restore the UI's...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-22 07:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-22 17:06 UTC

   Snyk has monitored and has confirmed the incident is now fully resolved. The incident response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-21 13:57 UTC

   Our Engineers have implemented a fix and we are no longer observing degraded PR checks. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-18 12:06 UTC

   Our engineers detected a performance degradation affecting the Snyk v3 API from 11:15 to 11:30 UTC. During this period, customers might have encountered latency or timeouts when accessing the v3 API. A fix has been applied by our engineers to address the issue, and we do not...

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-12 16:21 UTC

   All problematic issues identified under the incident and impacting access to the Snyk Support Portal have now been resolved.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-07 09:43 UTC

   Our Engineers identified and implemented a fix to restore service to the Snyk Platform. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-06 15:10 UTC

   Our Engineers have observed no further impact during the monitoring period. The Snyk Incident Response has been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.

1. resolved 2024-11-05 11:46 UTC

   No further issues have been observed and our Engineers are confident the issue has now been resolved. The Snyk Incident Response has now been stood down.

Excerpts are shortened. Read the full incident on Snyk's status page.