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
We've deployed a fix and are now monitoring closely to confirm full resolution.
investigating
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.
investigating
Our Engineers are investigating degradation affecting Snyk Open Source, across our <a href="https://app.snyk.io/">app.snyk.io</a> environment.
Customers may see CLI errors on Secrets and dependency graph scans.
The Snyk Incident Response has been invoked.
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.
identified
The fix has been deployed, and Snyk Code tests are completing. We are currently processing the remaining backlog.
identified
Snyk Engineers have identified the root cause and are deploying a fix to production. We will update when the fix is fully deployed.
identified
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.
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.
identified
Our Engineers are investigating degradation which is impacting Recurring Tests.
Customers may observe that daily Recurring Tests have not executed as scheduled for yesterday's (17th September) run. We expect these tests to be executed during today's schedule. Weekly recurring tests are scheduled as expected.
The Snyk Incident Response has been invoked.
Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
identified
Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.
investigating
Our investigations remain ongoing.
We will keep you updated with our progress.
investigating
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.
Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open Source
monitoring
The fix is deployed across all environments. We're continuing to monitor for any further stability issues.
monitoring
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.
Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
investigating
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 of this service degradation and investigating the root cause. We will provide another update as soon as we have more information.
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.
