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.
April 2026
Reports PDF Export Degraded
Source not attested
Last archived state: resolved
View archived record details
monitoring
Our Engineering team has implemented a fix and we are currently monitoring the behavior in the platform.
investigating
Our Engineers are investigating the degradation affecting PDF Export of Reports.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Snyk Recurring Tests Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We will continue to monitor services throughout today to ensure all Recurring Tests run as scheduled.
monitoring
Snyk engineers have successfully deployed a mitigation. Recurring tests have now resumed, and we are closely monitoring the environment to ensure continued stability.
identified
Snyk Engineering has identified a mitigation and is currently implementing it.
investigating
We're currently investigating degradation affecting Recurring Tests.
Since April 11th, customers may have been experiencing delays for some Recurring Tests.
The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Service Degradation on US-01 (app.snyk.io)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk engineers have implemented mitigation steps resulting in improved performance across the Multi-Tenant US-01 environment (app.snyk.io). We are currently monitoring the system closely to confirm a full and stable recovery.
investigating
The incident remains ongoing. Snyk engineers are treating this with the highest priority and are actively implementing mitigation strategies. We do not have an estimated time for restoration (ETR) at this moment, but we will provide updates as they become available. We appreciate your continued patience.
investigating
The incident remains in flight, with impact continuing in the Multi-Tenant US-01 environment (app.snyk.io). Snyk Engineers are working to restore service as quickly as possible.
investigating
The incident is ongoing. Snyk engineers continue to address the ongoing performance degradation in the Multi-Tenant US-01 environment (app.snyk.io). Mitigation efforts are underway, though response rates remain impacted for a portion of our customer base.
investigating
Our engineering teams are actively diagnosing the issues affecting the Multi-Tenant US-01 environment (app.snyk.io). We are working to restore service as quickly as possible and appreciate your patience.
investigating
Snyk engineers have identified degraded performance in the Multi-Tenant US-01 environment (app.snyk.io). All services are affected, and customers may experience failures when attempting to access this environment. The investigation is ongoing under the Snyk Incident Response process.
investigating
We are currently investigating the issue
PR Check Failures - Snyk-US-02
minorSource not attested
Last archived state: resolved
View archived record details
identified
Snyk engineers have detected intermittent PR check failures affecting the multi-tenant environment app.us.snyk.io. These failures are due to processing issues with GitHub and GitLab webhooks. The Snyk Incident Response has been enacted. Our engineers are investigating this matter further.
March 2026
Snyk Recurring Tests Degraded
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating degradation affecting Snyk Recurring Tests.
Some Customers may notice that their daily recurring tests are delayed.
The Snyk Incident Response has been invoked.
Snyk GitHub Cloud App Integrations Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are no longer observing degradation. However, we are monitoring the services to ensure they remain stable.
investigating
We are currently investigating a service degradation affecting customers using our GitHub Cloud App integration.
Customers may experience delays or failures affecting their Snyk scans.
The Snyk Incident Response has been invoked.
Free Users Unable to Sign up for Snyk
Source not attested
Last archived state: resolved
View archived record details
identified
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.
Degradation of Bitbucket Cloud integration services
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation is now live. Our team will remain in a monitoring phase through 6 PM UTC to ensure continued stability
identified
We have deployed a fix that enables a workaround for project imports using the BitBucket Connect App. As this rolls out, you may experience temporary failures with these imports for up to 30 minutes. If you experience an issue, we recommend waiting a few minutes before trying again.
identified
During our monitoring phase, we have become aware that customers using Bitbucket Connect App integrations may be unable to import new repositories.
We are investigating this and will keep you updated on our progress.
monitoring
A fix has been implemented, and we are now monitoring to ensure services fully recover.
identified
Customers using the Bitbucket Cloud integrations may see degradation in service affecting any use of the Bitbucket Cloud integrations, including:
Creating/Editing Bitbucket Integration,
Listing repos for import,
Import (via UI or API)
Tests, Recurring Tests, PR Checks
Fix PRs
We have identified the cause of the issue and are working towards remediation.
Snyk Recurring Tests Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our mitigation steps have been successful, and we're no longer observing delays affecting recurring tests.
We will continue to monitor to ensure services remain stable.
identified
To resolve the issues causing test delays and ensure system stability, we are temporarily reverting our recent Reachability engine updates for Java and JavaScript.
As a direct result of this rollback, customers may observe the following temporary effects:
Fluctuations in the Reachability status for Java and JavaScript vulnerabilities.
Changes to the corresponding Risk and Priority Scores.
investigating
Our Engineers have identified the likely root cause of the delays and are working to deploy a fix.
In the meantime, a small percentage of daily recurring tests may still be affected.
investigating
We're still observing delays affecting recurring tests, and our troubleshooting efforts remain ongoing.
We will provide a further update tomorrow.
investigating
Our Engineers are continuing their mitigation efforts. However, a small percentage of customers may continue to observe delays affecting daily recurring tests.
We will continue to keep you updated with our progress.
investigating
Delays are still affecting a small portion of our weekly and daily recurring tests.
We will continue to keep you updated on any progress.
investigating
We continue to observe delays affecting a small portion of daily and weekly recurring tests.
Our investigations remain ongoing, and we will have a further update to share after 16:00 UTC.
investigating
We're continuing to observe delays affecting a small portion of daily recurring tests.
We expect any missed tests from yesterday to be picked up during today's run.
Our investigations remain ongoing, and we will continue to keep you updated with our progress.
investigating
A small portion of daily recurring tests are still experiencing delays.
We will continue to keep you updated as we progress.
investigating
Our Engineers are investigating the 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. We will keep you updated with our progress.
Snyk Go Scans Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix, and initial signs suggest this has been successful.
We will continue to monitor to ensure services have fully recovered.
investigating
Our engineers are currently investigating a degradation affecting customers who have opted in to Full Source Code Analysis.
A small subset of affected customers may observe issues with importing, PR Checks, manual tests, and recurring tests for their Go projects.
The Snyk Incident Response has been invoked, and our investigations are underway.
