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.
March 2026
Free Users Unable to Sign up for Snyk
Source not attested
Last archived state: resolved
View archived record details
investigating
Our Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Snyk Reporting (Analytics) Unavailable
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and initial signs suggest this has been successful.
We are now monitoring to ensure services remain stable.
investigating
Our Engineers are currently investigating the loss of Reporting (Analytics) across the Snyk Platform.
Customers will observe that reporting services are currently unavailable.
The Snyk Incident Response has been invoked, and our investigations are underway.
Snyk Recurring Tests Degraded
minorSource not attested
Last archived state: resolved
View archived record details
identified
Services are beginning to normalise. However, a small percentage of customers may continue to experience delays affecting their daily Recurring Tests as we work through the backlog.
We will continue to update you as we progress.
investigating
During our initial investigations, we identified that only a small portion of daily recurring tests are impacted. The affected tests are experiencing a delay relative to their usual schedule.
Our investigations remain ongoing, and we will continue to keep you updated with our progress.
investigating
Our Engineers are investigating degradation affecting Snyk Recurring Tests.
Some Customers may notice that their daily recurring tests have not executed as expected.
The Snyk Incident Response has been invoked, and our investigations have commenced.
PR Check Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing with monitoring throughout today to make sure our services continue to remain stable.
monitoring
A fix has been deployed, and initial signs suggest this has been successful.
We are currently monitoring to ensure services remain stable.
identified
Our Engineers are aware of the degradation affecting PR Checks.
Customers may observe that there are processing delays impacting their PR Checks, resulting in PR Checks getting stuck in a processing state.
The Snyk Incident Response has been invoked, and our investigations are underway.
