Snyk Outage History

Snyk is up right now

Pingoru has recorded 109 incidents for Snyk: 109 in the last 12 months and 26 in the last 90 days.

Source: status.snyk.io

109incidents recorded
109last 12 months
26last 90 days
37 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct12
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct51%
Pingoru began tracking Snyk in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610365 of 720 (51%)
May 202614413 of 744 (55%)
June 202610439 of 720 (61%)
July 20266116 of 744 (16%)
August 2026996 of 744 (13%)
September 20265170 of 720 (24%)
October 202612294 of 579 (51%)

Incidents, newest first

Minor October 23, 2026 Snyk Support portal degradation 6h 5m Support Portal

Started Oct 23, 2026, 03:56 AM UTC· resolved Oct 23, 2026, 10:02 AM UTC

  1. identified Oct 23, 2026, 03:56 AM UTC

    Snyk Support portal is experiencing a degradation of service. Users may not be able to log in to the portal at support.snyk.io to create or view support cases. Other options to create support cases may also be impacted. We have identified that this appears to be due to a related incident on the 3rd party provider. We will monitor and provide updates as they are available.

  2. monitoring Oct 23, 2026, 06:20 AM UTC

    The 3rd party provider has implemented a fix, and initial testing indicates that it is successful. The Snyk Support portal should now be available, however we'll keep monitoring for a short period to ensure full service is maintained

  3. resolved Oct 23, 2026, 10:02 AM UTC

    There have been no further interruptions to our service, declaring the incident as resolved.

Read the full incident report →

Minor October 20, 2026 PR Check Invalid Credential Error 2h 58m Snyk Code, Snyk Code, Snyk Code, Snyk Code and 1 more

Started Oct 20, 2026, 04:33 PM UTC· resolved Oct 20, 2026, 07:31 PM UTC

  1. investigating Oct 20, 2026, 04:33 PM UTC

    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.

  2. investigating Oct 20, 2026, 05:16 PM UTC

    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.

  3. identified Oct 20, 2026, 05:53 PM UTC

    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.

  4. monitoring Oct 20, 2026, 06:22 PM UTC

    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.

  5. resolved Oct 20, 2026, 07:31 PM UTC

    Post-mitigation monitoring confirms that all Snyk services are operating normally and remain stable. The incident response team has stood down, and this incident is now resolved.

Read the full incident report →

Minor October 17, 2026 Snyk Code Performance Degraded in SNYK-US-02 2d 20h Snyk Code, Snyk Code

Started Oct 17, 2026, 01:43 AM UTC· resolved Oct 19, 2026, 10:02 PM UTC

  1. investigating Oct 17, 2026, 01:43 AM UTC

    Snyk Engineers are investigating an issue affecting Snyk Code performance including scans and PR checks in the Multi-tenant SNYK-US-01 environment. The Snyk Incident Response has been enacted.

  2. investigating Oct 17, 2026, 02:05 AM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 17, 2026, 02:06 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Oct 17, 2026, 02:30 AM UTC

    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.

  5. resolved Oct 19, 2026, 10:02 PM UTC

    All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor October 15, 2026 PR Checks and Imports Degraded in SNYK-US-01 1h 7m Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source and 2 more

Started Oct 15, 2026, 08:39 PM UTC· resolved Oct 15, 2026, 09:47 PM UTC

  1. identified Oct 15, 2026, 08:39 PM UTC

    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.

  2. monitoring Oct 15, 2026, 09:04 PM UTC

    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.

  3. monitoring Oct 15, 2026, 09:09 PM UTC

    The import backlog has been processed. Services are operating within normal ranges. Snyk engineers continue to monitor the environment.

  4. resolved Oct 15, 2026, 09:47 PM UTC

    All services remain operational during the monitoring period. The Snyk Incident response has been stood down.

Read the full incident report →

Minor October 13, 2026 GitLab Cloud Integration Degraded 1d 1h Snyk Code, Snyk Code, Snyk Code, Snyk Code and 6 more

Started Oct 13, 2026, 07:32 AM UTC· resolved Oct 14, 2026, 08:53 AM UTC

  1. identified Oct 13, 2026, 07:32 AM UTC

    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.

  2. monitoring Oct 13, 2026, 08:10 AM UTC

    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.

  3. resolved Oct 14, 2026, 08:53 AM UTC

    GitLab are still monitoring their services, but we have seen no further impact on Snyk integrations in the last 24 hours. This incident has been resolved, and the Snyk Incident Response has been stood down.

Read the full incident report →

Minor October 8, 2026 Snyk Open Source and Container Degradation 21h 5m Snyk Container, Snyk Open Source

Started Oct 08, 2026, 10:03 AM UTC· resolved Oct 09, 2026, 07:08 AM UTC

  1. investigating Oct 08, 2026, 10:03 AM UTC

    Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our app.au.snyk.io 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.

  2. monitoring Oct 08, 2026, 11:24 AM UTC

    Our engineers have applied a fix, and services have recovered across our app.au.snyk.io 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.

  3. resolved Oct 09, 2026, 07:08 AM UTC

    Services have remained stable throughout our monitoring period, and the Snyk Incident Response has been stood down.

Read the full incident report →

Minor October 7, 2026 Snyk CLI Tests - 504 Gateway Timeouts 1d 2h Snyk Open Source

Started Oct 07, 2026, 03:04 PM UTC· resolved Oct 08, 2026, 05:42 PM UTC

  1. investigating Oct 07, 2026, 03:04 PM UTC

    Our engineers are investigating a recurrence of the incident on 6th October (see here). We are again seeing failures affecting CLI tests for customers within our app.snyk.io 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.

  2. identified Oct 07, 2026, 03:50 PM UTC

    Our engineering team has identified the root cause of the issue and is actively taking steps to resolve it.

  3. monitoring Oct 07, 2026, 04:29 PM UTC

    Snyk engineers have completed mitigation efforts, and the environment is currently being monitored.

  4. resolved Oct 08, 2026, 05:42 PM UTC

    We have observed no further impact during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor October 6, 2026 Snyk CLI SCA Scans Degraded due to Enrichment of Test Failure 1h 5m Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 more

Started Oct 06, 2026, 10:53 PM UTC· resolved Oct 06, 2026, 11:58 PM UTC

  1. monitoring Oct 06, 2026, 10:53 PM UTC

    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.

  2. resolved Oct 06, 2026, 11:58 PM UTC

    We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor October 3, 2026 Issues API V3 Service - Degraded 4d 17h Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

Started Oct 03, 2026, 07:49 PM UTC· resolved Oct 08, 2026, 12:56 PM UTC

  1. identified Oct 03, 2026, 07:49 PM UTC

    We have identified an issue causing degraded performance and response delays on Issues API V3 for a subset of users. 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.

  2. monitoring Oct 06, 2026, 06:32 AM UTC

    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.

  3. resolved Oct 08, 2026, 12:56 PM UTC

    We're no longer observing delays affecting the Issues API V3 service. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor September 28, 2026 Snyk CLI Scans Degraded 2d 22h Snyk Open Source, Snyk Secrets

Started Sep 28, 2026, 02:26 PM UTC· resolved Oct 01, 2026, 12:33 PM UTC

  1. monitoring Sep 28, 2026, 02:26 PM UTC

    Our Engineers observed a recurrence of the impact reported in our earlier incident. We've deployed a further fix and are monitoring closely to confirm stability before considering this resolved.

  2. monitoring Sep 29, 2026, 12:53 PM UTC

    During monitoring, we observed a brief recurrence of impact. This has now been resolved, and we're continuing to monitor closely.

  3. resolved Oct 01, 2026, 12:33 PM UTC

    No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor September 21, 2026 Snyk Code Services Degraded in MT-US-01 3h 24m Snyk Code

Started Sep 21, 2026, 02:43 PM UTC· resolved Sep 21, 2026, 06:07 PM UTC

  1. identified Sep 21, 2026, 02:43 PM UTC

    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.

  2. identified Sep 21, 2026, 04:10 PM UTC

    Snyk Engineers have identified the root cause and are deploying a fix to production. We will update when the fix is fully deployed.

  3. identified Sep 21, 2026, 04:47 PM UTC

    The fix has been deployed, and Snyk Code tests are completing. We are currently processing the remaining backlog.

  4. monitoring Sep 21, 2026, 05:33 PM UTC

    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.

  5. resolved Sep 21, 2026, 06:07 PM UTC

    All services remain stable. The incident is now resolved.

Read the full incident report →

Minor September 18, 2026 Snyk Daily Recurring Tests Delayed 2d 23h Snyk Container, Snyk Open Source

Started Sep 18, 2026, 06:40 AM UTC· resolved Sep 21, 2026, 06:02 AM UTC

  1. identified Sep 18, 2026, 06:40 AM UTC

    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.

  2. monitoring Sep 18, 2026, 11:05 AM UTC

    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.

  3. resolved Sep 21, 2026, 06:02 AM UTC

    No further delays have been observed, and all Recurring Tests have now been completed as expected. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor September 9, 2026 Imports and PR Checks Degraded 2h 25m Snyk Code, Snyk Code, Snyk Code, Snyk Code and 6 more

Started Sep 09, 2026, 02:37 PM UTC· resolved Sep 09, 2026, 05:02 PM UTC

  1. investigating Sep 09, 2026, 02:37 PM UTC

    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.

  2. investigating Sep 09, 2026, 03:29 PM UTC

    Our investigations remain ongoing. We will keep you updated with our progress.

  3. identified Sep 09, 2026, 03:47 PM UTC

    Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.

  4. resolved Sep 09, 2026, 05:02 PM UTC

    Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.

Read the full incident report →

Minor August 30, 2026 Partial Broker Service Degradation 2d 16h Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk Code and 11 more

Started Aug 30, 2026, 02:32 PM UTC· resolved Sep 02, 2026, 06:42 AM UTC

  1. monitoring Aug 30, 2026, 02:32 PM UTC

    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.

  2. monitoring Aug 31, 2026, 03:02 PM UTC

    The fix is deployed across all environments. We're continuing to monitor for any further stability issues.

  3. resolved Sep 02, 2026, 06:42 AM UTC

    No further impact has been observed throughout the monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Notice August 20, 2026 Snyk Code Degradation 2h 25m Snyk Code, Snyk Code, Snyk Code, Snyk Code

Started Aug 20, 2026, 08:55 AM UTC· resolved Aug 20, 2026, 11:20 AM UTC

  1. investigating Aug 20, 2026, 12:42 PM UTC

    Our Engineers identified a degradation that affected Snyk Code. Customers may have observed errors with CLI testing between 08:55 UTC and 11:20 UTC.

  2. resolved Aug 20, 2026, 12:43 PM UTC

    The issue has been mitigated, and service has been restored.

Read the full incident report →

Notice August 19, 2026 GitHub Cloud App Error 1h 5m

Started Aug 19, 2026, 06:30 PM UTC· resolved Aug 19, 2026, 07:35 PM UTC

  1. investigating Aug 19, 2026, 06:30 PM UTC

    Snyk Engineers are investigating an issue affecting customers who are installing the GitHub Cloud App. Customers who already have the app installed are not impacted.

  2. identified Aug 19, 2026, 06:56 PM UTC

    Snyk Engineers have identified the root cause and are working on a mitigation.

  3. resolved Aug 19, 2026, 07:35 PM UTC

    Snyk engineers have deployed a fix and have confirmed the GitHub Cloud App installation is working as expected. The incident is now resolved.

Read the full incident report →

Minor August 17, 2026 GitHub Integration Degradation 4h 40m Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk and 24 more

Started Aug 17, 2026, 03:01 PM UTC· resolved Aug 17, 2026, 07:42 PM UTC

  1. identified Aug 17, 2026, 03:01 PM UTC

    Snyk is currently experiencing elevated error rates (up to 20%) due to an ongoing third-party incident with GitHub. Features dependent on GitHub integration are affected. We are actively monitoring the situation and will provide updates as GitHub resolves the issue.

  2. resolved Aug 17, 2026, 07:42 PM UTC

    Snyk engineers have confirmed service recovery. The incident is now resolved.

Read the full incident report →

Minor August 11, 2026 SAST Push Test Failing in SNYK-US-01 7h Snyk Code, Snyk IaC, Snyk Open Source

Started Aug 11, 2026, 02:54 PM UTC· resolved Aug 11, 2026, 09:55 PM UTC

  1. identified Aug 11, 2026, 02:54 PM UTC

    Snyk engineers have identified an issue affecting SAST Push tests in the Snyk-US-01 Multi-tenant environment. The root cause has been identified, and mitigation efforts are underway.

  2. identified Aug 11, 2026, 04:05 PM UTC

    Snyk Engineers are deploying a fix for the SAST Test Failures. Currently, Snyk Code (SAST) results are not updating in the UI. Projects are displaying issue counts and findings from their previous test rather than the latest scan. New scan results are being captured, and no data has been lost; affected projects will display current results once the fix is deployed and the next successful test completes.

  3. monitoring Aug 11, 2026, 06:52 PM UTC

    Snyk engineers have deployed a fix, and all services have been restored. We are monitoring the environment to ensure stability.

  4. resolved Aug 11, 2026, 09:55 PM UTC

    All systems remain stable during the monitoring period after the mitigation was implemented. The incident response has been stood down.

Read the full incident report →

Minor August 5, 2026 SNYK-US-01 Test Service Degradation 1d 12h Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC and 2 more

Started Aug 05, 2026, 07:26 PM UTC· resolved Aug 07, 2026, 07:29 AM UTC

  1. investigating Aug 05, 2026, 07:26 PM UTC

    Snyk engineers are observing increased latency affecting Test Services in the SNYK-US-01 environment. Our Incident Response process has been enacted. Our engineers are investigating the issue. Thank you.

  2. investigating Aug 05, 2026, 08:51 PM UTC

    Snyk engineers remain engaged under an incident footing. Our engineers are implementing mitigation measures to mitigate the impact. Further updates to follow.

  3. monitoring Aug 05, 2026, 10:54 PM UTC

    Snyk engineers have implemented a mitigation. Test latency has returned to normal ranges. Our engineers are monitoring the environment.

  4. resolved Aug 07, 2026, 07:29 AM UTC

    We observed no further impact during the monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor August 5, 2026 Degraded performance on Security.snyk.io with 502 responses. 9h 7m Snyk Container, Snyk Container, Snyk Container, Snyk Container and 11 more

Started Aug 05, 2026, 04:28 AM UTC· resolved Aug 05, 2026, 01:35 PM UTC

  1. investigating Aug 05, 2026, 04:28 AM UTC

    We are investigating degraded performance on the snyk Vuln DB page, security.snyk.io Currently, the /vuln page is working, but some individual vulnerability reports are returning 502 responses. Testing and Reporting is not affected.

  2. monitoring Aug 05, 2026, 04:57 AM UTC

    We have implemented a fix. Service has returned to normal levels. We are monitoring for stability

  3. investigating Aug 05, 2026, 05:34 AM UTC

    Monitoring has shown that the fix was only temporarily successful and the issue has recurred. We are continuing to investigate.

  4. investigating Aug 05, 2026, 10:00 AM UTC

    Our investigations into the root cause remain ongoing. We will keep you updated on our progress.

  5. monitoring Aug 05, 2026, 12:51 PM UTC

    A fix has been deployed to production, and we're closely monitoring the system.

  6. resolved Aug 05, 2026, 01:35 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 →

Major August 4, 2026 Snyk Open Source .NET Tests Failing 1h 21m Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 more

Started Aug 04, 2026, 01:07 PM UTC· resolved Aug 04, 2026, 02:29 PM UTC

  1. investigating Aug 04, 2026, 01:07 PM UTC

    We've identified an issue affecting all .NET project workflows, including import, retest, and pull request checks. The Snyk Incident Response has been invoked, and our engineering team are investigating.

  2. identified Aug 04, 2026, 01:44 PM UTC

    Our engineering team have identified the root cause and are working on deploying a fix. We will keep you updated on our progress.

  3. resolved Aug 04, 2026, 02:29 PM UTC

    Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.

Read the full incident report →

Minor July 23, 2026 Partial Test Degradation 14h 35m Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source

Started Jul 23, 2026, 07:59 PM UTC· resolved Jul 24, 2026, 10:34 AM UTC

  1. investigating Jul 23, 2026, 07:59 PM UTC

    We are currently experiencing partial degradation for some tests across all product lines. We will provide updates as they become available.

  2. monitoring Jul 23, 2026, 08:59 PM UTC

    The system has recovered and Snyk Engineers are currently monitoring the platform.

  3. resolved Jul 24, 2026, 10:34 AM UTC

    No further errors have been observed during our monitoring period. The Snyk Incident Response has now been stood down.

Read the full incident report →

Notice July 23, 2026 Temporary Degradation of Open Source and Container 15m Snyk Container, Snyk Open Source

Started Jul 23, 2026, 02:27 PM UTC· resolved Jul 23, 2026, 02:42 PM UTC

  1. resolved Jul 23, 2026, 02:56 PM UTC

    We had a brief recurrence of yesterday's incident, affecting customers in two short windows: 14:27–14:36 UTC 14:37–14:42 UTC Service has now recovered. Customers should re-import any imports that errored or failed during these windows.

Read the full incident report →

Minor July 14, 2026 Workspaces Service & Code PR Checks Degraded 1h 54m Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC and 2 more

Started Jul 14, 2026, 06:18 PM UTC· resolved Jul 14, 2026, 08:12 PM UTC

  1. identified Jul 14, 2026, 06:18 PM UTC

    We have identified an issue affecting Workspaces Services and Code PR checks within the SNYK-EU-01 multi-tenant environment. Please note that Open Source and License features are unaffected and remain fully operational. Our engineering team is actively working on a resolution.

  2. monitoring Jul 14, 2026, 06:58 PM UTC

    Our engineers have identified the root cause and deployed a mitigation, returning services to fully operational status. We will continue to monitor the environment to ensure stability.

  3. resolved Jul 14, 2026, 08:12 PM UTC

    All services remain stable. The incident is now resolved.

Read the full incident report →

Minor July 14, 2026 API Routes Degradation 2h 18m Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC and 2 more

Started Jul 14, 2026, 05:56 PM UTC· resolved Jul 14, 2026, 08:14 PM UTC

  1. identified Jul 14, 2026, 05:56 PM UTC

    We are aware of intermittent failures affecting a subset of public-facing API routes. Our team has identified the issue and is actively deploying a mitigation. We will provide an update once the issue is resolved.

  2. resolved Jul 14, 2026, 08:14 PM UTC

    A fix has been deployed, and all systems are performing normally. This incident has been marked as resolved.

Read the full incident report →