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.
August 2026
GitHub Cloud App Error
Source not attested
Last archived state: resolved
View archived record details
identified
Snyk Engineers have identified the root cause and are working on a mitigation.
investigating
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.
GitHub Integration Degradation
minorSource not attested
Last archived state: resolved
View archived record details
Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk API & WebSnyk API & WebSnyk API & WebSnyk API & Web
identified
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.
SAST Push Test Failing in SNYK-US-01
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk engineers have deployed a fix, and all services have been restored. We are monitoring the environment to ensure stability.
identified
Snyk Engineers are deploying a fix for the SAST Test Failures. Currently, Snyk Code (SAST) results are not updating in the UI. Projects are displaying issue counts and findings from their previous test rather than the latest scan. New scan results are being captured, and no data has been lost; affected projects will display current results once the fix is deployed and the next successful test completes.
identified
Snyk engineers have identified an issue affecting SAST Push tests in the Snyk-US-01 Multi-tenant environment. The root cause has been identified, and mitigation efforts are underway.
SNYK-US-01 Test Service Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk engineers have implemented a mitigation. Test latency has returned to normal ranges. Our engineers are monitoring the environment.
investigating
Snyk engineers remain engaged under an incident footing. Our engineers are implementing mitigation measures to mitigate the impact. Further updates to follow.
investigating
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.
Degraded performance on Security.snyk.io with 502 responses.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed to production, and we're closely monitoring the system.
investigating
Our investigations into the root cause remain ongoing.
We will keep you updated on our progress.
investigating
Monitoring has shown that the fix was only temporarily successful and the issue has recurred. We are continuing to investigate.
monitoring
We have implemented a fix. Service has returned to normal levels. We are monitoring for stability
investigating
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.
Snyk Open Source .NET Tests Failing
majorSource not attested
Last archived state: resolved
View archived record details
identified
Our engineering team have identified the root cause and are working on deploying a fix.
We will keep you updated on our progress.
investigating
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.
July 2026
Partial Test Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The system has recovered and Snyk Engineers are currently monitoring the platform.
investigating
We are currently experiencing partial degradation for some tests across all product lines.
We will provide updates as they become available.
Temporary Degradation of Open Source and Container
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 activated and corrective actions have returned operations to normal.
The team is continuing to monitor the situation.
Workspaces Service & Code PR Checks Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
API Routes Degradation
minorSource not attested
Last archived state: resolved
View archived record details
identified
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.
