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.
May 2026
GitHub Integration Service Degraded
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are currently experiencing degraded performance with our GitHub integrations due to an ongoing, broader service disruption on GitHub’s end. Our team is actively monitoring the situation and will automatically restore full connectivity as soon as the upstream issue is resolved.
CLI Monitor Degredation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk engineers are currently investigating degraded performance in Multi-Tenant Snyk US-01. Customers may experience failures with the CLI Monitor. Our engineers have implemented a mitigation strategy and have observed an increase in the CLI Monitor's success rate. We are actively monitoring the environment.
Issues API Delays
minorSource not attested
Last archived state: resolved
View archived record details
identified
Snyk engineers have identified latency affecting a small subset of customers. Affected customers may observe a delay in Issues API data freshness. Our engineers are investigating the issue. Impact is limited to the Multi-Tenant Snyk-US-01 environment.
Snyk Recurring Tests Delayed
minorSource not attested
Last archived state: resolved
View archived record details
identified
We continue to see improvements as a result of the mitigation actions taken. However, we will monitor to ensure services fully recover.
identified
We have identified the root cause of the delays and implemented mitigations.
Some customers may still experience delayed daily recurring tests while these changes fully propagate
We will continue to monitor the situation to ensure the mitigations have been successful.
investigating
We are continuing to investigate the root cause of the delays.
Customers may still experience delays affecting a small percentage of daily recurring tests.
investigating
Snyk engineers have noticed delays in a small percentage of daily recurring tests in the Multi-Tenant Synk-US-01 (app.snyk.io) environment. The impact is limited to daily tests; weekly tests remain unaffected.
Snyk engineers are investigating the issue.
April 2026
Reports PDF Export Degraded
minorSource 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.
GitHub integration service degraded
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting our GitHub Cloud app integrations. This is resulting from a broader service degradation on GitHub’s end, which is impacting github.com and their external API services. We are monitoring their progress closely and will restore full connectivity as soon as GitHub resolves the underlying issue.
Snyk recurring tests showing slow performance
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our investigation into the degradation affecting Recurring Tests is ongoing.
Some customers may continue to notice that a small percentage of their Recurring Tests are not executing as scheduled.
identified
We are continuing to observe the degradation affecting our Recurring Tests, and our investigations remain ongoing.
Some customers may notice that a small percentage of their Recurring Tests are not executing as scheduled.
identified
We have observed further degradation and are investigating.
Customers may observe a small percentage of Recurring Tests not executing as scheduled.
monitoring
We are no longer observing delays affecting Recurring Tests.
Monitoring is now underway to ensure there are no further delays during today's schedule.
investigating
We are continuing our mitigation efforts. However, customers will continue to experience delays and, in some cases, failures of their scheduled recurring tests.
Further updates will follow.
investigating
We have identified the root cause of the degraded performance affecting recurring tests and are working towards a fix.
Customers will continue to experience delays and, in some cases, failures of their scheduled recurring tests.
We will continue to keep you updated with our progress.
investigating
Our investigations remain ongoing. However, we are still observing degradation affecting our daily and weekly recurring tests.
We will continue to keep you updated with our progress.
investigating
We’ve identified a regression impacting our recurring test performance. Specifically, both daily and weekly test suites are showing increased latency.
Users affected by this degradation may see some tests failing intermittently or, in some cases, failing to execute entirely.
Our engineers are currently investigating the root cause, and a fix is being prioritized. We will provide another update once the stabilization patch is deployed.
Snyk Code Test Degraded
minorSource not attested
Last archived state: resolved
View archived record details
identified
Snyk engineers are continuing to deploy the mitigation to the affected environment. The mitigation has been applied to the SNYK-US-01 region.
investigating
We are investigating an issue where Snyk Code Tests are receiving degraded performance. Affected users might see Snyk Code Test fail on their scans and pull requests even if there are no known vulnerabilities. We are currently working on a fix and will give a further update shortly.
Snyk Issues API Degraded
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating the issue.
CLI Test and Monitor Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk Engineers have successfully deployed a mitigation. We will continue to monitor the environment throughout the weekend to ensure ongoing stability and performance.
identified
We are investigating reports of degraded performance affecting CLI tests within the Snyk-US-01 multi-tenant environment. Our incident response process has been activated, and we have identified specific mitigation steps. We will provide further updates as we work toward a resolution.
