- Detected by Pingoru
- Jun 09, 2026, 11:22 AM UTC
- Resolved
- Jun 09, 2026, 02:14 PM UTC
- Duration
- 2h 51m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 3 updates
-
investigating Jun 09, 2026, 11:22 AM UTC
Our engineers are investigating degradation affecting app.snyk.io. Customers may experience continuous loading and/or slowness when accessing the Snyk UI. This may also impact the testing of projects. The Snyk Incident Response has been invoked.
-
monitoring Jun 09, 2026, 12:15 PM UTC
A fix has been implemented, and initial signs are positive. We will continue to monitor to ensure services fully recover and remain stable.
-
resolved Jun 09, 2026, 02:14 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
- Jun 08, 2026, 03:47 PM UTC
- Resolved
- Jun 10, 2026, 06:22 AM UTC
- Duration
- 1d 14h
Affected: Support Portal
Timeline · 3 updates
-
identified Jun 08, 2026, 03:47 PM UTC
Please note that the ability to create or reply to cases via email has been temporarily turned off. If you need to log a new issue or update an existing case, please do so directly through the ticketing portal. We will let you know as soon as email functionality is restored. Thank you for your patience!
-
monitoring Jun 09, 2026, 02:13 PM UTC
We have re-enabled the email-to-case feature, allowing customers to create and reply to cases via email. Monitoring is now underway to ensure the services remains stable.
-
resolved Jun 10, 2026, 06:22 AM UTC
Services have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:37 AM UTC
- Resolved
- Jun 04, 2026, 06:39 AM UTC
- Duration
- 1d 21h
Affected: Snyk ContainerSnyk Open Source
Timeline · 3 updates
-
monitoring Jun 02, 2026, 09:37 AM UTC
During our recent Recurring Tests, we observed that some email notifications were not sent to alert customers to new vulnerabilities. All Recurring Tests have completed successfully, and customers can view their results within the Snyk UI. We have now implemented a fix. Email notifications will resume with the next scheduled run.
-
monitoring Jun 02, 2026, 12:47 PM UTC
We are observing delays affecting some Daily Recurring Tests as a result of our mitigation actions.
-
resolved Jun 04, 2026, 06:39 AM UTC
We are no longer observing delays affecting Recurring Tests. All tests have caught up, and services are operating normally. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 02:17 PM UTC
- Resolved
- Jun 01, 2026, 02:17 PM UTC
- Duration
- —
Affected: Snyk CodeSnyk Code
Timeline · 1 update
-
resolved Jun 01, 2026, 02:17 PM UTC
Between 12:03 and 12:04 UTC today (1st June 2026), Snyk experienced a brief period of degradation affecting Snyk Code scans and custom Rule Extension tests. This impacted scans run via the CLI, IDE plugins, CLI uploads, as well as PR Checks. Services have now fully recovered. Please retry any scans or tests that failed during this window.
Read the full incident report →
- Detected by Pingoru
- May 23, 2026, 08:43 AM UTC
- Resolved
- May 23, 2026, 07:46 PM UTC
- Duration
- 11h 2m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 2 updates
-
investigating May 23, 2026, 08:43 AM UTC
We are currently investigating reports of intermittent failures affecting our GitHub Cloud App integration, specifically impacting repository scans, project imports, and Pull Request status checks. During this time, customers may see failures on PR checks, recurring tests and imports. Because the issue is intermittent, manually re-running a scan or retrying an import may succeed. Our engineering team is actively analyzing system logs to pinpoint the root cause, and we will provide regular updates until full stability is restored
-
resolved May 23, 2026, 07:46 PM UTC
The intermittent issues affecting repository scans, project imports, and Pull Request status checks have been fully resolved. The root cause was an upstream degradation with GitHub Cloud app installation token authentication, which has now been mitigated on the GitHub side (ref: GitHub Incident k5z4d1v1tqmt). If you continue to experience issues with your PRs, imports, or repository scans, please reach out to our support team for further assistance.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 05:26 PM UTC
- Resolved
- May 22, 2026, 07:14 PM UTC
- Duration
- 1h 47m
Affected: Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 2 updates
-
identified May 22, 2026, 05:26 PM UTC
Snyk engineers have identified the root cause of degraded performance affecting Open Source across all environments, leading to PR Checks and recurring test failures. A fix is currently being rolled out globally. We will provide further updates as the deployment progresses.
-
resolved May 22, 2026, 07:14 PM UTC
Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 02:29 AM UTC
- Resolved
- May 26, 2026, 01:20 PM UTC
- Duration
- 4d 10h
Affected: Snyk Open SourceSnyk Open Source
Timeline · 4 updates
-
identified May 22, 2026, 02:29 AM UTC
Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks. The investigation is ongoing under the Snyk Incident Response process.
-
identified May 22, 2026, 02:52 PM UTC
Our Engineers have confirmed that the US-01 (app.snyk.io) environment has shown no further degradation following re-deployment and appears to be stable. Investigation into the AU-01 (app.au.snyk.io) environment is still ongoing, and we will provide a further update as we progress.
-
monitoring May 25, 2026, 11:26 PM UTC
Our Engineers have implemented a fix, and we're no longer observing the degradation on the AU-01 (app.au.snyk.io) environment. We will continue to monitor for ongoing stability.
-
resolved May 26, 2026, 01:20 PM UTC
We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 11:37 AM UTC
- Resolved
- May 21, 2026, 05:16 PM UTC
- Duration
- 5h 38m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 4 updates
-
investigating May 21, 2026, 11:37 AM UTC
We're currently investigating degradation affecting our app.snyk.io environment. Customers may experience slowness and/or failures affecting project imports and recurring tests. The Snyk Incident Response has been invoked.
-
identified May 21, 2026, 12:22 PM UTC
Success rates have now recovered. However, the environment remains under close monitoring while our investigation into the root cause and further mitigations continues. We will keep you updated as we progress.
-
identified May 21, 2026, 02:56 PM UTC
A fix has been deployed, and initial signs are positive. We will continue to monitor service to ensure services remain stable.
-
resolved May 21, 2026, 05:16 PM UTC
All services remain stable after the mitigation. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 05:08 PM UTC
- Resolved
- May 20, 2026, 08:06 AM UTC
- Duration
- 14h 57m
Affected: Snyk CodeSnyk Open Source
Timeline · 3 updates
-
investigating May 19, 2026, 05:08 PM UTC
Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures—including Recurring Tests—within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.
-
investigating May 19, 2026, 08:09 PM UTC
We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will provide further updates as they become available.
-
resolved May 20, 2026, 08:06 AM UTC
We observed no further impact during our monitoring period. The Snyk Incident Response has now been stood down.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:19 PM UTC
- Resolved
- May 20, 2026, 10:51 AM UTC
- Duration
- 20h 32m
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 · 4 updates
-
investigating May 19, 2026, 02:19 PM UTC
We're currently investigating an issue affecting Jira integrations. Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform. Jira Cloud integrations are unaffected. The Snyk Incident Response has been invoked.
-
identified May 19, 2026, 03:35 PM UTC
Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.
-
monitoring May 19, 2026, 07:47 PM UTC
A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.
-
resolved May 20, 2026, 10:51 AM UTC
We are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 05:29 AM UTC
- Resolved
- May 20, 2026, 02:57 PM UTC
- Duration
- 1d 9h
Affected: Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 12:12 PM UTC
- Resolved
- May 19, 2026, 02:27 PM UTC
- Duration
- 1d 2h
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 4 updates
-
investigating May 18, 2026, 12:12 PM UTC
Snyk Engineers have identified degraded performance in the Multi-Tenant US-01 environment (app.snyk.io), affecting multiple services. The investigation is ongoing under the Snyk Incident Response process.
-
investigating May 18, 2026, 02:57 PM UTC
Our investigations into the root cause remain ongoing. We will keep you updated with our progress.
-
investigating May 19, 2026, 11:22 AM UTC
Our investigation into the root cause remains ongoing. We are currently seeing a reduced frequency of the issue and are continuing to monitor performance closely. Further updates will be provided as our investigation progresses.
-
resolved May 19, 2026, 02:27 PM UTC
We have identified and deployed a fix restoring normal service. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 11:19 AM UTC
- Resolved
- May 18, 2026, 12:53 PM UTC
- Duration
- 1h 33m
Affected: Snyk CodeSnyk Open Source
Timeline · 2 updates
-
investigating May 18, 2026, 11:19 AM UTC
We're currently investigating intermittent degradation affecting PR events. This is affecting GitHub, GitLab, Bitbucket Cloud and Bitbucket Server integrations. The Snyk Incident Response has been invoked.
-
resolved May 18, 2026, 12:53 PM UTC
Following our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution details, please follow: Service Degradation on US-01 (app.snyk.io).
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 02:49 PM UTC
- Resolved
- May 13, 2026, 07:01 PM UTC
- Duration
- 4h 12m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 2 updates
-
investigating May 13, 2026, 02:49 PM UTC
Snyk engineers are investigating degraded performance with the Reporting PDF in the Snyk-US-01 multi-tenant environment. Customers may observe longer generation times or failures to generate reports.
-
resolved May 13, 2026, 07:01 PM UTC
Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 02:35 PM UTC
- Resolved
- May 11, 2026, 02:41 PM UTC
- Duration
- 6m
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 SourceEvo by SnykEvo by SnykEvo by SnykEvo by Snyk
Timeline · 2 updates
-
identified May 11, 2026, 02:35 PM UTC
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.
-
resolved May 11, 2026, 02:41 PM UTC
The upstream issues at GitHub have been resolved. Our engineering team has verified full recovery, and all Snyk GitHub integrations are operating normally. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 07:09 PM UTC
- Resolved
- May 08, 2026, 09:51 PM UTC
- Duration
- 2h 42m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 2 updates
-
monitoring May 08, 2026, 07:09 PM UTC
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.
-
resolved May 08, 2026, 09:51 PM UTC
CLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 08:45 PM UTC
- Resolved
- May 07, 2026, 08:30 AM UTC
- Duration
- 11h 44m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 2 updates
-
identified May 06, 2026, 08:45 PM UTC
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.
-
resolved May 07, 2026, 08:30 AM UTC
Our Engineers deployed a fix, and we're no longer observing delays affecting the Issues API data freshness. The Snyk Incident Response has been stood down.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 03:32 PM UTC
- Resolved
- May 12, 2026, 07:20 AM UTC
- Duration
- 5d 15h
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 5 updates
-
investigating May 06, 2026, 03:32 PM UTC
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.
-
investigating May 07, 2026, 01:19 PM UTC
We are continuing to investigate the root cause of the delays. Customers may still experience delays affecting a small percentage of daily recurring tests.
-
identified May 08, 2026, 01:02 PM UTC
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.
-
identified May 11, 2026, 02:19 PM UTC
We continue to see improvements as a result of the mitigation actions taken. However, we will monitor to ensure services fully recover.
-
resolved May 12, 2026, 07:20 AM UTC
We are no longer observing delays affecting our Recurring Tests as a result of the mitigation actions taken. The Snyk Incident Response has now been stood down.
Read the full incident report →
- 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 21, 2026, 06:58 PM UTC
- Resolved
- May 05, 2026, 12:23 PM UTC
- Duration
- 13d 17h
Affected: Snyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 9 updates
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 →
