Snyk incident

Degraded Performance SNYK-US-01

Major Resolved View vendor source →

Snyk experienced a major incident on June 22, 2026 affecting Snyk AppRisk and Snyk Code and 1 more component, lasting 1d 23h. The incident has been resolved; the full update timeline is below.

Started
Jun 22, 2026, 10:21 PM UTC
Resolved
Jun 24, 2026, 09:34 PM UTC
Duration
1d 23h
Detected by Pingoru
Jun 22, 2026, 10:21 PM UTC

Affected components

Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source

Update timeline

  1. identified Jun 22, 2026, 10:21 PM UTC

    Our engineering team is currently investigating reports of degraded performance in the SNYK-US-01 US Multi-tenant environment (app.snyk.io). We are actively working to isolate the cause and will provide updates as we the investigation progresses.

  2. identified Jun 22, 2026, 11:06 PM UTC

    Snyk engineers are continuing their investigation. We have applied initial mitigation steps and are seeing signs of recovery, though some performance degradation persists. Our teams remain focused on a full resolution, and we will share another update shortly.

  3. identified Jun 23, 2026, 12:52 AM UTC

    Snyk Engineering is continuing to investigate the issue. Mitigation steps are progressing but will take some time to be fully effective. Current scope of effect: * Customers may notice increased latency across the Snyk UI platform, as well as API, CLI, SCM based projects and PR Checks. * Due to the increased latency, some tests may be observed to timeout and fail. * There is currently no known observed impact to analytics and reporting. This issue is not affecting other environments. We will continue to work on mitigation efforts and provide updates as the issue progresses.

  4. monitoring Jun 23, 2026, 02:34 AM UTC

    Mitigation steps have been completed and are showing immediate improvements in success rate and latency, and are burning down the backlog. We will maintain a period of monitoring for continued stability.

  5. monitoring Jun 23, 2026, 10:53 AM UTC

    We are continuing our monitoring throughout today to ensure services remain stable.

  6. resolved Jun 24, 2026, 09:34 PM UTC

    This incident has been resolved.