Skip to content
Snyk · SecurityMay 19, 2026, 17:08 UTC

Scan and Recurring Test Degradation

MinorNot disclosedUpdated 18h ago
May 19, 17:08 UTCMay 20, 08:06 UTC
Duration
14h 58m
Impact
Minor
Root cause
Not disclosed
Snyk, 90 days
18 incidents
Affected
Snyk CodeSnyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk CodeSNYK-US-01 (app.snyk.io) - Snyk Open Source
Status page

Final update

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

Timeline

  1. Resolved · May 20, 08:06 UTC
    We observed no further impact during our monitoring period. The Snyk Incident Response has now been stood down.
  2. Investigating · May 19, 20:09 UTC
    We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will provide further updates as they become available.
  3. Investigating · May 19, 17:08 UTC
    Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures, including Recurring Tests, within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.

More from Snyk

Full history
StartedIncidentDuration
Sep 2114:43 UTCSnyk Code Services Degraded in MT-US-013h 24m
Sep 1806:40 UTCSnyk Daily Recurring Tests Delayed2d 23h
Sep 914:37 UTCImports and PR Checks Degraded2h 25m
Aug 3014:32 UTCPartial Broker Service Degradation2d 16h
Aug 3012:20 UTCPartial Broker Service Degradation1h 12m
Aug 2012:42 UTCSnyk Code Degradation0m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.