Snyk Outage History

Snyk experienced intermittent failures with their GitHub Cloud App integration for 11.1 hours, affecting repository scans, project imports, and Pull Request status checks across all Snyk products (Open Source, Code, Container, and IaC). The issue was caused by an upstream degradation with GitHub Cloud app installation token authentication, which was resolved on GitHub's side. During the incident, customers could sometimes work around failures by manually re-running scans or retrying imports.

Snyk experienced degraded performance across all Open Source environments, causing PR Checks and recurring test failures. Engineers identified the root cause and deployed a global fix. The incident lasted 1.8 hours with minor impact classification.

Snyk experienced degradation affecting their app.snyk.io environment for 5.7 hours, causing slowness and failures in project imports and recurring tests across all major components (Code, AppRisk, IaC, Container, and Open Source). The issue was resolved through a deployed fix, with service rates recovering and remaining stable after mitigation.

Snyk experienced scan failures affecting Code Scan and Open Source Reachability scans, including recurring tests, within their Multi-tenant Snyk-US-01 environment for 15 hours. The incident impacted Snyk Open Source and Snyk Code services, preventing users from running security scans on their code and dependencies. Engineers successfully mitigated the Open Source issues first, then resolved the remaining Code Scan performance degradation after continued monitoring confirmed system stability.

Snyk's Jira integration experienced a 20.6-hour outage that prevented users from managing Jira integrations, viewing associated Jira tickets on Snyk issues, or creating new Jira tickets through the platform. The incident affected multiple Snyk components including Open Source, Container, Code, and IaC services, while the Snyk Security In Jira Cloud integration remained unaffected. Engineers identified the root cause, deployed a fix to production, and confirmed full resolution after monitoring the restored integration workflows.

A supply chain compromise affected over 630 malicious package versions across more than 315 unique npm packages, with the AntV suite heavily impacted due to a compromised npm maintainer account that enabled automated malicious package publishing. Snyk's Open Source service was affected as it monitors these third-party packages, though Snyk's own systems and infrastructure were not compromised. The incident was resolved after 33.5 hours with Snyk providing vulnerability reporting, remediation guidance through their Trust Center, and tools for customers to assess potential impact in their projects.

Snyk experienced degraded performance in their US-01 environment (app.snyk.io) for 26.3 hours, affecting all major services including IaC, Open Source, Container, Code, and AppRisk. Engineers identified and deployed a fix that restored normal service, with the incident response team standing down after resolution.

Snyk experienced intermittent degradation affecting pull request events across GitHub, GitLab, Bitbucket Cloud, and Bitbucket Server integrations, impacting Snyk Open Source and Snyk Code services. The incident lasted 1.6 hours and was resolved when it was determined to be related to an existing broader service degradation issue. Updates were consolidated to a separate incident tracking page for centralized communication.

Snyk's PDF reporting functionality experienced degraded performance in the US-01 environment for 4.2 hours, causing longer generation times and failures when customers attempted to generate reports. The issue affected all major Snyk components including IaC, Open Source, Container, Code, and AppRisk services. Engineers successfully deployed a mitigation that restored normal PDF report generation functionality.

Snyk's GitHub integration service experienced degraded performance for 10 minutes due to a broader service disruption on GitHub's platform. The incident affected all major Snyk components including Open Source, Container, Code, IaC, and AppRisk services that rely on GitHub connectivity. Service was automatically restored once the upstream GitHub issues were resolved, with Snyk's engineering team confirming full recovery across all integrations.