- Detected by Pingoru
- Apr 29, 2026, 03:43 PM UTC
- Resolved
- Apr 29, 2026, 08:00 PM UTC
- Duration
- 4h 17m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 3 updates
-
investigating Apr 29, 2026, 03:43 PM UTC
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.
-
monitoring Apr 29, 2026, 05:25 PM UTC
Our Engineering team has implemented a fix and we are currently monitoring the behavior in the platform.
-
resolved Apr 29, 2026, 08:00 PM UTC
We've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 04:34 PM UTC
- Resolved
- Apr 23, 2026, 05:56 PM UTC
- Duration
- 1h 21m
Affected: Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSupport PortalSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk LearnSnyk LearnSnyk LearnSnyk Learn
Timeline · 2 updates
-
investigating Apr 23, 2026, 04:34 PM UTC
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.
-
resolved Apr 23, 2026, 05:56 PM UTC
Upstream GitHub issues are resolved. Snyk engineers have verified system recovery and confirmed that no further impact remains. Incident response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 03:07 PM UTC
- Resolved
- Apr 20, 2026, 04:05 PM UTC
- Duration
- 58m
Affected: Snyk Code
Timeline · 3 updates
-
investigating Apr 20, 2026, 03:07 PM UTC
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.
-
identified Apr 20, 2026, 03:24 PM UTC
Snyk engineers are continuing to deploy the mitigation to the affected environment. The mitigation has been applied to the SNYK-US-01 region.
-
resolved Apr 20, 2026, 04:05 PM UTC
A fix has been implemented for the Snyk Test failures. Service for Code Scans (SAST) has returned to normal operations.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 11:23 PM UTC
- Resolved
- Apr 17, 2026, 11:34 PM UTC
- Duration
- 11m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 2 updates
-
investigating Apr 17, 2026, 11:23 PM UTC
We are currently investigating the issue.
-
resolved Apr 17, 2026, 11:34 PM UTC
This outage has now been resolved and all systems are operational.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 08:21 PM UTC
- Resolved
- Apr 20, 2026, 04:04 PM UTC
- Duration
- 2d 19h
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 3 updates
-
identified Apr 17, 2026, 08:21 PM UTC
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.
-
monitoring Apr 17, 2026, 09:22 PM UTC
Snyk Engineers have successfully deployed a mitigation. We will continue to monitor the environment throughout the weekend to ensure ongoing stability and performance.
-
resolved Apr 20, 2026, 04:04 PM UTC
A fix has been implemented for the Snyk Code Test failures. The service for Code Scans (SAST) has returned to normal operations.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 02:58 PM UTC
- Resolved
- Apr 15, 2026, 09:12 AM UTC
- Duration
- 1d 18h
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 5 updates
-
investigating Apr 13, 2026, 02:58 PM UTC
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.
-
identified Apr 13, 2026, 05:49 PM UTC
Snyk Engineering has identified a mitigation and is currently implementing it.
-
monitoring Apr 13, 2026, 09:55 PM UTC
Snyk engineers have successfully deployed a mitigation. Recurring tests have now resumed, and we are closely monitoring the environment to ensure continued stability.
-
monitoring Apr 14, 2026, 09:59 AM UTC
We will continue to monitor services throughout today to ensure all Recurring Tests run as scheduled.
-
resolved Apr 15, 2026, 09:12 AM UTC
There have been no further issues observed throughout the monitoring period, and we're confident the issue has now been resolved. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 02:38 PM UTC
- Resolved
- Apr 09, 2026, 07:17 PM UTC
- Duration
- 4h 38m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSnyk Learn
Timeline · 8 updates
-
investigating Apr 09, 2026, 02:38 PM UTC
We are currently investigating the issue
-
investigating Apr 09, 2026, 02:50 PM UTC
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 Apr 09, 2026, 03:11 PM UTC
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 Apr 09, 2026, 03:45 PM UTC
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 Apr 09, 2026, 04:20 PM UTC
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 Apr 09, 2026, 04:56 PM UTC
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.
-
monitoring Apr 09, 2026, 05:44 PM UTC
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.
-
resolved Apr 09, 2026, 07:17 PM UTC
No further issues have been observed during our monitoring period across the Multi-Tenant US-01 environment (app.snyk.io). The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 05:13 PM UTC
- Resolved
- Apr 07, 2026, 05:28 PM UTC
- Duration
- 14m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 2 updates
-
identified Apr 07, 2026, 05:13 PM UTC
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.
-
resolved Apr 07, 2026, 05:28 PM UTC
Snyk engineers have mitigated the intermittent failures. Snyk is no longer observing any failed requests or elevated response times. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 09:46 AM UTC
- Resolved
- Mar 31, 2026, 01:02 PM UTC
- Duration
- 3h 16m
Affected: Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 3 updates
-
investigating Mar 31, 2026, 09:46 AM UTC
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.
-
monitoring Mar 31, 2026, 11:29 AM UTC
We are no longer observing degradation. However, we are monitoring the services to ensure they remain stable.
-
resolved Mar 31, 2026, 01:02 PM UTC
No further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 05:21 PM UTC
- Resolved
- Mar 24, 2026, 05:45 PM UTC
- Duration
- 23m
Timeline · 2 updates
-
identified Mar 24, 2026, 05:21 PM UTC
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.
-
resolved Mar 24, 2026, 05:45 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 12:45 AM UTC
- Resolved
- Mar 25, 2026, 09:00 AM UTC
- Duration
- 2d 8h
Affected: 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 Source
Timeline · 6 updates
-
identified Mar 23, 2026, 12:45 AM UTC
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.
-
monitoring Mar 23, 2026, 08:26 AM UTC
A fix has been implemented, and we are now monitoring to ensure services fully recover.
-
identified Mar 23, 2026, 12:18 PM UTC
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.
-
identified Mar 23, 2026, 02:05 PM UTC
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.
-
monitoring Mar 24, 2026, 04:37 PM UTC
The mitigation is now live. Our team will remain in a monitoring phase through 6 PM UTC to ensure continued stability
-
resolved Mar 25, 2026, 09:00 AM UTC
We have observed no further issues during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 10:54 AM UTC
- Resolved
- Mar 17, 2026, 02:16 PM UTC
- Duration
- 3h 21m
Affected: Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 4 updates
-
investigating Mar 17, 2026, 10:54 AM UTC
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.
-
monitoring Mar 17, 2026, 12:00 PM UTC
We have implemented a fix, and initial signs suggest this has been successful. We will continue to monitor to ensure services have fully recovered.
-
monitoring Mar 17, 2026, 02:15 PM UTC
No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.
-
resolved Mar 17, 2026, 02:16 PM UTC
No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 08:17 AM UTC
- Resolved
- Mar 13, 2026, 12:13 PM UTC
- Duration
- 3h 56m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 3 updates
-
investigating Mar 13, 2026, 08:17 AM UTC
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.
-
monitoring Mar 13, 2026, 08:26 AM UTC
A fix has been implemented, and initial signs suggest this has been successful. We are now monitoring to ensure services remain stable.
-
resolved Mar 13, 2026, 12:13 PM UTC
No further impact was observed during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:04 PM UTC
- Resolved
- Mar 17, 2026, 02:43 PM UTC
- Duration
- 5d
Affected: Snyk CodeSnyk Open Source
Timeline · 4 updates
-
identified Mar 12, 2026, 02:04 PM UTC
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.
-
monitoring Mar 13, 2026, 07:33 AM UTC
A fix has been deployed, and initial signs suggest this has been successful. We are currently monitoring to ensure services remain stable.
-
monitoring Mar 17, 2026, 10:12 AM UTC
We are continuing with monitoring throughout today to make sure our services continue to remain stable.
-
resolved Mar 17, 2026, 02:43 PM UTC
No further impact has been observed during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:30 AM UTC
- Resolved
- Mar 12, 2026, 03:32 AM UTC
- Duration
- 1h 2m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 3 updates
-
investigating Mar 12, 2026, 02:30 AM UTC
Our Engineers have determined a degradation of PR/MR Checks that is causing delays for the processing times. We are currently investigating the cause and will provide updates on scope of impact as our investigation proceeds.
-
investigating Mar 12, 2026, 02:59 AM UTC
We are still investigating the cause of the delays, but have identified that this appears to be affecting only the customers on app.snyk.io.
-
resolved Mar 12, 2026, 03:32 AM UTC
This incident has been resolved. Any PR Checks that have been hanging should be closed and reopened.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 12:43 PM UTC
- Resolved
- Mar 09, 2026, 12:58 PM UTC
- Duration
- 15m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSnyk Learn
Timeline · 3 updates
-
investigating Mar 09, 2026, 12:43 PM UTC
Our engineers identified an issue causing service disruption between 11:53 AM and 12:44 PM GMT. The services have now been fully restored, and our engineers will continue monitoring the situation to ensure there are no further disruptions.
-
monitoring Mar 09, 2026, 12:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 09, 2026, 12:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 02:54 AM UTC
- Resolved
- Mar 06, 2026, 05:16 AM UTC
- Duration
- 2h 22m
Affected: 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 Source
Timeline · 2 updates
-
identified Mar 06, 2026, 02:54 AM UTC
Snyk engineers have identified a service degradation across all cloud Bitbucket integrations, caused by a third-party incident. This issue is affecting all tests and projects on Bitbucket Cloud and Bitbucket Cloud App integrations. We are tracking the third party incident for updates.
-
resolved Mar 06, 2026, 05:16 AM UTC
All services have recovered and are operating normally after the third party took mitigation steps to restore services.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 07:10 PM UTC
- Resolved
- Mar 03, 2026, 08:13 PM UTC
- Duration
- 1h 3m
Affected: 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 LearnSnyk LearnSnyk LearnSnyk Learn
Timeline · 2 updates
-
identified Mar 03, 2026, 07:10 PM UTC
Snyk engineers identified service degradation across all GitHub integrations, caused by a third-party incident. The Snyk incident response has been activated, and engineers are actively monitoring the issue.
-
resolved Mar 03, 2026, 08:13 PM UTC
All services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 04:54 PM UTC
- Resolved
- Mar 04, 2026, 03:13 PM UTC
- Duration
- 22h 18m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Code
Timeline · 2 updates
-
identified Mar 03, 2026, 04:54 PM UTC
Snyk engineers are currently investigating performance issues affecting IDE plugins. Customers may encounter scan not triggering when Snyk Code is enabled in their IDE settings. The Snyk team is working on a fix, which is expected to be released on March 4th as part of the regularly scheduled CLI update. As a workaround, customers can downgrade the IDE plugin to a previous version. JetBrains: v2.19.0 VSCode: v2.28.1 Eclipse: v3.7.0 Visual Studio: v2.7.0 https://docs.snyk.io/developer-tools/snyk-ide-plugins-and-extensions/compatibility-matrix After the fix is released, customers need to update the CLI to 1.1303.1 to use the latest IDE plugin versions.
-
resolved Mar 04, 2026, 03:13 PM UTC
The Snyk engineering team has implemented the fix in the v1.1303.1 CLI release. You can find more details at the following link: https://github.com/snyk/cli/releases/tag/v1.1303.1. The Snyk incident response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 12:47 AM UTC
- Resolved
- Mar 03, 2026, 01:36 AM UTC
- Duration
- 49m
Affected: Snyk Open Source
Timeline · 4 updates
-
investigating Mar 03, 2026, 12:47 AM UTC
* We have detected an issue that is causing a degradation in Open Source scans and projects on app.us.snyk.io * Affected services including Importing, Retests, Loading Projects, Pr Checks * Loading projects may show “Something went wrong” and importing projects may show “project could not be created” Currently other environments appear to be unaffected. We are investigating and will report regularly with updates including any changes in scope.
-
investigating Mar 03, 2026, 01:05 AM UTC
CLI: `snyk montior` for opensource testing and saving to the snyk Ui is currently affected. `snyk test` by CLI are working We are continuing to investigate the cause of the issue
-
monitoring Mar 03, 2026, 01:16 AM UTC
A fix has been implemented and performance has been restored. We will maintain a period of monitoring.
-
resolved Mar 03, 2026, 01:36 AM UTC
No further recurrence has been detected. Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 04:53 PM UTC
- Resolved
- Mar 03, 2026, 05:01 PM UTC
- Duration
- 1d
Affected: 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 LearnSnyk LearnSnyk LearnSnyk Learn
Timeline · 4 updates
-
identified Mar 02, 2026, 04:53 PM UTC
Snyk has identified an issue affecting customers who are using Snyk CLI Version 1.1303.0 with the —report option for static analysis. Affected customers are advised to revert to the previous version of Snyk CLI, 1.1302.1, which is unaffected by this problem. Snyk engineers are currently investigating this issue as part of their Incident Response process.
-
identified Mar 02, 2026, 07:07 PM UTC
Snyk engineers have identified a path to resolution and are preparing the fix.
-
identified Mar 02, 2026, 09:42 PM UTC
Snyk engineers are preparing the identified fix, which is expected to be deployed tomorrow, March 3rd.
-
resolved Mar 03, 2026, 05:01 PM UTC
Snyk engineers successfully deployed the fix across all environments. Services are functioning normally, and the Snyk Incident Response team has been stood down.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 01:56 PM UTC
- Resolved
- Feb 24, 2026, 03:14 PM UTC
- Duration
- 1h 18m
Affected: Snyk AppRisk
Timeline · 2 updates
-
investigating Feb 24, 2026, 01:56 PM UTC
Our Engineers have identified an issue affecting the freshness of information displayed on the Inventory page. The Snyk Incident Response has been invoked, and our investigations are progressing.
-
resolved Feb 24, 2026, 03:14 PM UTC
Our Engineers have identified the root cause and managed to immediately implement a fix that addressed the issue. The Inventory data is now up to date.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 10:58 PM UTC
- Resolved
- Feb 20, 2026, 01:45 AM UTC
- Duration
- 2h 47m
Affected: 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 LearnSnyk LearnSnyk LearnSnyk Learn
Timeline · 3 updates
-
identified Feb 19, 2026, 10:58 PM UTC
Currently we are experiencing some difficulties with case creation from Email. Please use the support portal support.snyk.io for all case creation Email replies to existing cases do not appear to be impacted, however we recommend using the support portal for vital communications We will advise when the service returns to normal
-
monitoring Feb 20, 2026, 12:50 AM UTC
A fix has been applied, and Emails should be working again as normal. We will continue to monitor performance for a short time
-
resolved Feb 20, 2026, 01:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 03:37 PM UTC
- Resolved
- Feb 17, 2026, 04:04 PM UTC
- Duration
- 27m
Affected: Snyk Learn
Timeline · 2 updates
-
investigating Feb 17, 2026, 03:37 PM UTC
Our Engineers are investigating the degradation affecting Snyk Assist. Customers will experience failures when attempting to use the Snyk Assist functionality. The Snyk Incident Response has been invoked.
-
resolved Feb 17, 2026, 04:04 PM UTC
Our Engineers have completed their initial investigation, during which we have established that there was no impact on our customer base. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 12:56 PM UTC
- Resolved
- Feb 13, 2026, 03:46 PM UTC
- Duration
- 2h 49m
Affected: Snyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 2 updates
-
identified Feb 13, 2026, 12:56 PM UTC
Our engineers are aware of a degradation that impacted project retesting triggered by code changes in GitLab between 11:20 UTC on 12 February and 11:40 UTC on 13 February. The Snyk Incident Response process has been invoked, and the issue is under active investigation.
-
resolved Feb 13, 2026, 03:46 PM UTC
Our Engineers have implemented a fix to ensure no further impact to services. The Snyk Incident Response has now been stood down.
Read the full incident report →