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