Looking for an update now? Check the current status, or follow Snyk for future changes.
70.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
80%
30
6
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Snyk engineers have deployed a fix across all environments, and all services have returned to normal operation. We will continue monitoring system stability to ensure the issue is fully resolved.
identified
Our engineering team has identified the root cause of the incident and is preparing a fix. We do not yet have an estimated time for deployment, but we will share updates as soon as they become available.
investigating
Our engineering team is continuing to investigate the incident. In addition to blocked PR checks, customers may experience delays with recurring tests, and other features utilizing the Workspaces Service may be affected. Current impact appears to be isolated to GitHub and GitHub Enterprise workspaces. We will provide further updates as the investigation progresses.
investigating
Snyk engineers are investigating reports of "Invalid Credential" errors affecting Snyk Code PR checks across all environments. Our incident response team has been activated, and we are working to resolve the issue as quickly as possible.
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.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
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.
Snyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSnyk API & WebSnyk Secrets
monitoring
The import backlog has been processed. Services are operating within normal ranges. Snyk engineers continue to monitor the environment.
monitoring
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.
identified
Snyk engineers are investigating degraded performance affecting PR Checks and Imports in the multi-tenant SNYK-US-01 environment. The incident response protocol has been activated. The issue has been identified, and mitigation steps are currently underway.
Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
monitoring
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.
identified
We are aware of an incident affecting the GitLab Cloud service, which is impacting Git operations.
As a result, customers using GitLab Cloud integrations may see actions such as imports and scans in Snyk Open Source and Snyk Code time out or fail.
We will share an update as soon as there is more information.
Our engineers have applied a fix, and services have recovered across our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment.
If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run.
We are continuing to monitor performance closely and will post here if anything changes.
investigating
Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our <a href="https://app.au.snyk.io/">app.au.snyk.io</a> environment.
Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Snyk engineers have completed mitigation efforts, and the environment is currently being monitored.
identified
Our engineering team has identified the root cause of the issue and is actively taking steps to resolve it.
investigating
Our engineers are investigating a recurrence of the incident on 6th October (see <a href="https://status.snyk.io/incidents/wd2vnr5rzv3g">here</a>). We are again seeing failures affecting CLI tests for customers within our <a href="https://app.snyk.io/">app.snyk.io</a> 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.
Snyk CLI SCA Scans Degraded due to Enrichment of Test Failure
Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
monitoring
Our Engineers have observed degradation affecting CLI SCA tests for customers.
Customers may see this error "Test execution failed: Enrichment of Test Failed" when running CLI Open Source tests.
The root cause has been identified and a fix has been deployed. The Snyk Incident Response team will continue monitoring closely. We will keep you updated with further progress.
Snyk engineers have completed mitigation efforts, and the environment is currently being monitored.
identified
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.
investigating
Our engineers are investigating failures affecting CLI tests for customers within our <a href="https://app.snyk.io/">app.snyk.io</a> 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.
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.
identified
We have identified an issue affecting Issues API V3 that is causing response delays for some users. Overall service performance remains otherwise unaffected.
Our engineering team has isolated the cause and is actively working on a fix. We will share another update as soon as the patch is deployed.
During monitoring, we observed a brief recurrence of impact. This has now been resolved, and we're continuing to monitor closely.
monitoring
Our Engineers observed a recurrence of the impact reported in our earlier <a href="https://status.snyk.io/incidents/0mzlplq9xgvn">incident</a>.
We've deployed a further fix and are monitoring closely to confirm stability before considering this resolved.
Legacy Incident Archive
54 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
GitHub Cloud App Integration Service Degradation
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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 imports. Because the issue is intermittent, manually re-running a scan or retrying an import may succeed.
Our engineering team is actively analyzing system logs to pinpoint the root cause, and we will provide regular u...
PR Checks Degraded
minorSource not attested
Last archived state: resolved
View archived record details
identified
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.
Snyk Tests for Gradle projects Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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 progress.
identified
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 under the Snyk Incident Response process.
Snyk Import and Recurring Test Degradation
minorSource not attested
Last archived state: resolved
View archived record details
identified
A fix has been deployed, and initial signs are positive.
We will continue to monitor service to ensure services remain stable.
identified
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.
investigating
We're currently investigating degradation affecting our <a href="https://app.snyk.io/">app.snyk.io</a> environment.
Customers may experience slowness and/or failures affecting project imports and recurring tests.
The Snyk Incident Response has been invoked.
Scan and Recurring Test Degradation
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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 provide further updates as they become available.
investigating
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.
Jira Integration Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.
identified
Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.
investigating
We're currently investigating an issue affecting the <a href="https://docs.snyk.io/integrations/jira-and-slack-integrations/jira-integration">Jira integration</a>. Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform.
The <a href="https://docs.snyk.io/integrations/jira-and-slack-integrations/snyk-security-in-jira-cloud-integration">Snyk Security In Jira Cloud integration</a> is unaffected.
The Snyk Inc...
Supply Chain Compromise on @antv being investigated for more than 300 packages in npm ecosystem
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
The Compromised Packages list is now available at <a href="https://security.snyk.io/antv-supply-chain-compromise-may-2026">https://security.snyk.io/antv-supply-chain-compromise-may-2026</a>
investigating
Our blog post is now available: <a href="https://snyk.io/blog/mini-shai-hulud-antv-npm-supply-chain-attack/">Mini Shai-Hulud Hits AntV</a>
investigating
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 <a href="https://trust.snyk.io/updates">Snyk Trust Center</a> for the latest official updates and customer communications.
investigating
The <a href="https://trust.snyk.io/updates">Snyk Trust Center</a> has been updated.
investigating
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 related packages outside the AntV namespace.
Scope: Over 639 malicious package versions across more than 323 unique packages, with numbers subject to change
Cause: Investigations indicate the issue was caused by ...
investigating
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, products, or infrastructure were compromised.
As an active investigation, this is subject to change.
We are currently working on confirming the known scope and providing vulnerability advice, reporting, blog, and Trust Cen...
Service Degradation on US-01 (app.snyk.io)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
investigating
Our investigations into the root cause remain ongoing.
We will keep you updated with our progress.
investigating
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.
Snyk PR Degradation
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
Reporting PDF Degraded
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
