Snyk incident: Partial Test Degradation

Affected components

• Snyk Code
• Snyk Container
• Snyk IaC
• Snyk Open Source

1. resolvedJul 24, 2026, 10:34 UTC

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

2. monitoringJul 23, 2026, 20:59 UTC

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

3. investigatingJul 23, 2026, 19:59 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• MongoDB Atlas: Cluster connectivity issues in Azure westusMajor · Jul 23, 2026, 16:21 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident NotificationMajor · Jul 23, 2026, 19:14 UTC
• Grafana Cloud: Errors creating new Slack integration for Grafana IRMMajor · Jul 24, 2026, 09:17 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Plaid: Transaction Updates DelayedMinor · Jul 22, 2026, 14:58 UTC
• Calendly: Users Unable to Log In to Calendly due to blank Login PageMinor · Jul 23, 2026, 21:21 UTC
• Notion: Automation processing delaysMinor · Jul 24, 2026, 07:20 UTC
• dbt Cloud: Scheduled jobs are intermittently affected by job failures caused by 403 errorMinor · Jul 24, 2026, 07:58 UTC

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history