Minor impactResolvedDevOps

Snyk incident: Snyk Code (SAST) Scan service degraded

Snyk reported this minor-impact incident on its official status page on Jun 19, 2026, 20:13 UTC. It was resolved after 2h.

Right now Snyk is degraded. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Jun 19, 2026, 20:13 UTC
started
Jun 19, 2026, 22:13 UTC
resolved
2h
duration
Minor
impact

Affected components

  • Snyk Code
  1. resolvedJun 19, 2026, 22:13 UTC

    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.

  2. investigatingJun 19, 2026, 20:13 UTC

    We are currently experiencing an unexpected issue affecting our SAST scans and certain API triggered tests. Our engineering team is actively monitoring the situation to fully understand the impact and isolate the root cause. While we work to restore full functionality, some users may experience intermittent or immediate failures in their running scans and automated test suites. 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.

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

Snyk incident on Jun 19, 2026: Snyk Code (SAST) Scan service degraded · APIStatus.watch