Snyk

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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: Security incident or emergency response to a vulnerability. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.

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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.