Snyk incidents — Vendor Status Watch

Imports and PR Checks Degraded [resolved]

Wed, 09 Sep 2026 14:37:30 +0000

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.

Partial Broker Service Degradation [resolved]

Sun, 30 Aug 2026 14:32:12 +0000

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

Partial Broker Service Degradation [resolved]

Sun, 30 Aug 2026 12:20:00 +0000

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 Code Degradation [resolved]

Thu, 20 Aug 2026 12:42:34 +0000

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

GitHub Cloud App Error [resolved]

Wed, 19 Aug 2026 18:30:11 +0000

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

GitHub Integration Degradation [resolved]

Mon, 17 Aug 2026 15:01:40 +0000

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

SAST Push Test Failing in SNYK-US-01 [resolved]

Tue, 11 Aug 2026 14:54:41 +0000

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

SNYK-US-01 Test Service Degradation [resolved]

Wed, 05 Aug 2026 19:26:35 +0000

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

Degraded performance on Security.snyk.io with 502 responses. [resolved]

Wed, 05 Aug 2026 04:28:27 +0000

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

Snyk Open Source .NET Tests Failing [resolved]

Tue, 04 Aug 2026 13:07:28 +0000

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.

Partial Test Degradation [resolved]

Thu, 23 Jul 2026 19:59:56 +0000

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

Temporary Degradation of Open Source and Container [resolved]

Thu, 23 Jul 2026 14:56:12 +0000

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.

Temporary Degradation of Open Source and Container [resolved]

Wed, 22 Jul 2026 09:41:58 +0000

No further impact was observed during our monitoring period. Customers should re-import any imports that errored or failed during the outage window. The Snyk Incident Response has been stood down.

Workspaces Service & Code PR Checks Degraded [resolved]

Tue, 14 Jul 2026 18:18:29 +0000

All services remain stable. The incident is now resolved.

API Routes Degradation [resolved]

Tue, 14 Jul 2026 17:56:21 +0000

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

Snyk Partial Test Degradation [resolved]

Fri, 10 Jul 2026 13:41:21 +0000

The incident has been resolved after we have monitored the overall performance.

Degraded Peformance Affecting SNYK-US-01 [resolved]

Wed, 24 Jun 2026 21:39:29 +0000

This incident has been resolved.

Degraded Performance SNYK-US-01 [resolved]

Mon, 22 Jun 2026 22:21:03 +0000

This incident has been resolved.

Third-Party Vendor Security Incident (Klue) [resolved]

Fri, 19 Jun 2026 23:15:30 +0000

Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data within, was found. All impacted customers were notified directly and the data involved is consistent with what was disclosed in our June 22 blog post (https://snyk.io/blog/when-a-vendors-breach-becomes-yours-lessons-from-the-klue-incident/).

Snyk Code (SAST) Scan service degraded [resolved]

Fri, 19 Jun 2026 20:13:09 +0000

The issue affecting SAST scans and API-driven automated tests has been successfully resolved, and all services have returned to normal status. Our engineering team identified the root cause as an expensive SQL query that triggered database degradation. The query has been mitigated, and performance has stabilized. Thank you for your patience while we worked through this.

Degradation affecting app.snyk.io [resolved]

Wed, 17 Jun 2026 23:31:53 +0000

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

Data Freshness delay in Issues API for customers on app.snyk.io [resolved]

Tue, 16 Jun 2026 04:52:04 +0000

Both the Issues API data freshness and reporting data freshness have been fully restored and are operating normally. Our investigation is now complete, and the Snyk Incident Response has been stood down. We apologise for any inconvenience this may have caused and thank you for your patience throughout.

Degradation Affecting app.snyk.io [resolved]

Tue, 09 Jun 2026 11:22:25 +0000

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

Email-to-Case Temporarily Disabled [resolved]

Mon, 08 Jun 2026 15:47:49 +0000

Services have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.

Snyk Recurring Test Email Notification [resolved]

Tue, 02 Jun 2026 09:37:52 +0000

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.

Snyk Code Degradation [resolved]

Mon, 01 Jun 2026 14:17:15 +0000

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.

GitHub Cloud App Integration Service Degradation [resolved]

Sat, 23 May 2026 08:43:03 +0000

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.

PR Checks Degraded [resolved]

Fri, 22 May 2026 17:26:29 +0000

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.

Snyk Tests for Gradle projects Degradation [resolved]

Fri, 22 May 2026 02:29:36 +0000

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

Snyk Import and Recurring Test Degradation [resolved]

Thu, 21 May 2026 11:37:49 +0000

All services remain stable after the mitigation. The Snyk Incident Response has been stood down.