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