Snyk Outage History

95 incidents recorded over the last 365 days, 92 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Snyk status89.81% uptime history

Every Recorded Snyk Incident

Snyk incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 29, 2026Planned Maintenance Scheduled for 29th of August 2026Maintenance is scheduled to take place between the following times: Saturday 29th of August from 2:00PM UTC to 5:00PM UTC 07:00 PDT / 10:00 EDT / 15:00 BST / 16:00 CEST / 12:00 AEST (+1) During this time, you will not…3h 0mScheduled
Aug 20, 2026Snyk Code DegradationThe issue has been mitigated, and service has been restored.0 minResolved
Aug 19, 2026GitHub Cloud App ErrorSnyk engineers have deployed a fix and have confirmed the GitHub Cloud App installation is working as expected. The incident is now resolved.1h 5mResolved
Aug 17, 2026GitHub Integration DegradationSnyk engineers have confirmed service recovery. The incident is now resolved.4h 40mResolved
Aug 11, 2026SAST Push Test Failing in SNYK-US-01All systems remain stable during the monitoring period after the mitigation was implemented. The incident response has been stood down.7h 0mResolved
Aug 5, 2026SNYK-US-01 Test Service DegradationWe observed no further impact during the monitoring period. The Snyk Incident Response has been stood down.36h 2mResolved
Aug 5, 2026Degraded performance on Security.snyk.io with 502 responses.No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.9h 7mResolved
Aug 4, 2026Snyk Open Source .NET Tests FailingOur engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.1h 21mResolved
Jul 23, 2026Partial Test DegradationNo further errors have been observed during our monitoring period. The Snyk Incident Response has now been stood down.14h 35mResolved
Jul 23, 2026Temporary Degradation of Open Source and ContainerWe had a brief recurrence of yesterday's <a href="https://status.snyk.io/incidents/n0mqq1rwbmgw">incident</a>, affecting customers in two short windows: 14:27–14:36 UTC 14:37–14:42 UTC Service has now recovered…0 minResolved
Jul 22, 2026Temporary Degradation of Open Source and ContainerNo further impact was observed during our monitoring period. Customers should re-import any imports that errored or failed during the outage window. The Snyk Incident Response has been stood down.21h 28mResolved
Jul 14, 2026Workspaces Service & Code PR Checks DegradedAll services remain stable. The incident is now resolved.1h 54mResolved
Jul 14, 2026API Routes DegradationA fix has been deployed, and all systems are performing normally. This incident has been marked as resolved.2h 18mResolved
Jul 10, 2026Snyk Partial Test DegradationThe incident has been resolved after we have monitored the overall performance.6h 26mResolved
Jun 24, 2026Degraded Peformance Affecting SNYK-US-01This incident has been resolved.14h 35mResolved
Jun 22, 2026Degraded Performance SNYK-US-01This incident has been resolved.47h 13mResolved
Jun 19, 2026Third-Party Vendor Security Incident (Klue)Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence…448h 11mResolved
Jun 19, 2026Snyk Code (SAST) Scan service degradedThe 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…2h 0mResolved
Jun 17, 2026Degradation affecting app.snyk.ioNo further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.11h 27mResolved
Jun 16, 2026Data Freshness delay in Issues API for customers on app.snyk.ioBoth the Issues API data freshness and reporting data freshness have been fully restored and are operating normally. Our investigation is now complete, and the Snyk Incident Response has been stood down. We apologise…149h 20mResolved
Jun 9, 2026Degradation Affecting app.snyk.ioNo further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.2h 51mResolved
Jun 8, 2026Email-to-Case Temporarily DisabledServices have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.38h 35mResolved
Jun 2, 2026Snyk Recurring Test Email NotificationWe are no longer observing delays affecting Recurring Tests. All tests have caught up, and services are operating normally. The Snyk Incident Response has now been stood down.45h 1mResolved
Jun 1, 2026Snyk Code DegradationBetween 12:03 and 12:04 UTC today (1st June 2026), Snyk experienced a brief period of degradation affecting Snyk Code scans and custom Rule Extension tests. This impacted scans run via the CLI, IDE plugins, CLI uploads…0 minResolved
May 23, 2026GitHub Cloud App Integration Service DegradationThe intermittent issues affecting repository scans, project imports, and Pull Request status checks have been fully resolved. The root cause was an upstream degradation with GitHub Cloud app installation token…11h 2mResolved
May 22, 2026PR Checks DegradedSnyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.1h 47mResolved
May 22, 2026Snyk Tests for Gradle projects DegradationWe have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.106h 51mResolved
May 21, 2026Snyk Import and Recurring Test DegradationAll services remain stable after the mitigation. The Snyk Incident Response has been stood down.5h 38mResolved
May 19, 2026Scan and Recurring Test DegradationWe observed no further impact during our monitoring period. The Snyk Incident Response has now been stood down.14h 57mResolved
May 19, 2026Jira Integration DegradedWe are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.20h 32mResolved
May 19, 2026Supply Chain Compromise on  @antv being investigated for more than 300 packages in npm ecosystemCustomer Projects: This Status Page incident, “Supply Chain Compromise on AntV,” was opened to share customer-facing updates regarding a third-party compromise within the AntV ecosystem. Because AntV is a Snyk-supported…33h 28mResolved
May 18, 2026Service Degradation on US-01 (app.snyk.io)We have identified and deployed a fix restoring normal service. The Snyk Incident Response has been stood down.26h 15mResolved
May 18, 2026Snyk PR DegradationFollowing our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution…1h 33mResolved
May 13, 2026Reporting PDF DegradedSnyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.4h 12mResolved
May 11, 2026GitHub Integration Service DegradedThe upstream issues at GitHub have been resolved. Our engineering team has verified full recovery, and all Snyk GitHub integrations are operating normally. The Snyk Incident Response has been stood down.6 minResolved
May 9, 2026Planned Maintenance Scheduled for 9th of May 2026The maintenance work is now complete. Snyk is now available.3h 0mScheduled
May 8, 2026CLI Monitor DegredationCLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.2h 42mResolved
May 6, 2026Issues API DelaysOur Engineers deployed a fix, and we're no longer observing delays affecting the Issues API data freshness. The Snyk Incident Response has been stood down.11h 44mResolved
May 6, 2026Snyk Recurring Tests DelayedWe are no longer observing delays affecting our Recurring Tests as a result of the mitigation actions taken. The Snyk Incident Response has now been stood down.135h 48mResolved
Apr 29, 2026Reports PDF Export DegradedWe've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.4h 17mResolved
Apr 23, 2026GitHub integration service degradedUpstream GitHub issues are resolved. Snyk engineers have verified system recovery and confirmed that no further impact remains. Incident response has been stood down.1h 21mResolved
Apr 21, 2026Snyk recurring tests showing slow performanceWe are no longer observing degradation affecting Recurring Tests. The Snyk Incident Response has now been stood down.329h 25mResolved
Apr 20, 2026Snyk Code Test DegradedA fix has been implemented for the Snyk Test failures. Service for Code Scans (SAST) has returned to normal operations.58 minResolved
Apr 17, 2026Snyk Issues API DegradedThis outage has now been resolved and all systems are operational.11 minResolved
Apr 17, 2026CLI Test and Monitor DegradationA fix has been implemented for the Snyk Code Test failures. The service for Code Scans (SAST) has returned to normal operations.67h 42mResolved
Apr 15, 2026Reports PDF Export DegradedWe've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.16h 0mResolved
Apr 13, 2026Snyk Recurring Tests DegradedThere have been no further issues observed throughout the monitoring period, and we're confident the issue has now been resolved. The Snyk Incident Response has been stood down.42h 14mResolved
Apr 11, 2026Planned Maintenance Scheduled for 11th of April 2026We’re pleased to announce that today’s planned maintenance activity is now complete and all services are back online. Our apologies for the overrun, but thank you for your patience.3h 0mScheduled
Apr 9, 2026Service Degradation on US-01 (app.snyk.io)No further issues have been observed during our monitoring period across the Multi-Tenant US-01 environment (app.snyk.io). The Snyk Incident Response has been stood down.4h 38mResolved
Apr 7, 2026PR Check Failures - Snyk-US-02Snyk engineers have mitigated the intermittent failures. Snyk is no longer observing any failed requests or elevated response times. The Snyk Incident Response has been stood down.14 minResolved
Mar 31, 2026Snyk Recurring Tests DegradedWe are no longer experiencing delays affecting recurring tests. The Snyk Incident Response has now been stood down.25h 26mResolved
Mar 31, 2026Snyk GitHub Cloud App Integrations DegradedNo further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.3h 16mResolved
Mar 24, 2026Free Users Unable to Sign up for SnykOur Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform. The Snyk Incident Response has been invoked. We will keep you updated with our progress.23 minResolved
Mar 23, 2026Degradation of Bitbucket Cloud integration servicesWe have observed no further issues during our monitoring period. The Snyk Incident Response has now been stood down.56h 14mResolved
Mar 18, 2026Snyk Recurring Tests DegradedServices remain stable during the monitoring period. The Snyk Incident Response has been stood down.290h 8mResolved
Mar 17, 2026Snyk Go Scans DegradedNo further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.3h 21mResolved
Mar 16, 2026Free Users Unable to Sign up for SnykOur Engineers have deployed, and we are no longer observing issues affecting the sign-up process. The Snyk Incident Response has now been stood down.1h 15mResolved
Mar 13, 2026Snyk Reporting (Analytics) UnavailableNo further impact was observed during our monitoring period. The Snyk Incident Response has now been stood down.3h 56mResolved
Mar 12, 2026Snyk Recurring Tests DegradedWe are no longer observing delays affecting our daily recurring tests, and all backlogs have now cleared. The Snyk Incident Response has now been stood down.93h 3mResolved
Mar 12, 2026PR Check DegradationNo further impact has been observed during our monitoring period. The Snyk Incident Response has now been stood down.120h 38mResolved
Mar 12, 2026Elevated Snyk PR Checks Processing Time across Different SCMsThis incident has been resolved. Any PR Checks that have been hanging should be closed and reopened.1h 2mResolved
Mar 9, 2026Snyk service disruptionThis incident has been resolved.15 minResolved
Mar 6, 2026Bitbucket (cloud) Integration DegradationAll services have recovered and are operating normally after the third party took mitigation steps to restore services.2h 22mResolved
Mar 3, 2026Github Integration DegradationAll services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.1h 3mResolved
Mar 3, 2026IDE Plugin Scans not triggeringThe Snyk engineering team has implemented the fix in the v1.1303.1 CLI release. You can find more details at the following link: https://github.com/snyk/cli/releases/tag/v1.1303.1. The Snyk incident response has been…22h 18mResolved
Mar 3, 2026Open Source testing and snapshots degraded in US-02 (app.us.snyk.io)No further recurrence has been detected. Snyk Incident Response has been stood down.49 minResolved
Mar 2, 2026Snyk CLI Version 1.1303.0 Report Option IncidentSnyk engineers successfully deployed the fix across all environments. Services are functioning normally, and the Snyk Incident Response team has been stood down.24h 7mResolved
Feb 24, 2026Data Freshness Issue Impacting Inventory PageOur Engineers have identified the root cause and managed to immediately implement a fix that addressed the issue. The Inventory data is now up to date.1h 18mResolved
Feb 19, 2026Support Case email integration degradedThis incident has been resolved.2h 47mResolved
Feb 17, 2026Snyk Assist DegradedOur Engineers have completed their initial investigation, during which we have established that there was no impact on our customer base. The Snyk Incident Response has now been stood down.27 minResolved
Feb 13, 2026GitLab Project Testing DegradedOur Engineers have implemented a fix to ensure no further impact to services. The Snyk Incident Response has now been stood down.2h 49mResolved
Feb 11, 2026Import and PR check failing for PIPSnyk engineers have confirmed that all services are restored after mitigation activities were completed. The Snyk incident response team has been stood down.1h 11mResolved
Feb 11, 2026Recurring Tests DegradedSnyk engineers have been monitoring the environment and are no longer seeing delays affecting our daily recurring tests. The Snyk incident response has been stood down.219h 21mResolved
Feb 9, 2026GitHub Integration DegradationAll services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.38 minResolved
Jan 30, 2026Snyk Recurring Tests DegradedOur Engineers have implemented a fix, and are no longer observing delays affecting Recurring Tests. The Snyk Incident Response has been stood down.65h 48mResolved
Jan 29, 2026Project import on US-01 region intermittently completes with "Project could not be created"Our Engineers have implemented a fix and are confident this incident is now resolved. The Snyk Incident Response has now been stood down.2h 52mResolved
Jan 28, 2026Snyk Code DegradationSnyk engineers monitored the environment after the mitigation was deployed and have observed normal operations. The Snyk Incident Response has been stood down.7h 15mResolved
Jan 28, 2026Snyk Iac Terraform Cloud Integration DegradedWe have observed no further issues during our monitoring period. The Snyk Incident Response has now been stood down.1h 5mResolved
Jan 26, 2026Snyk Issues API DegradedOur Engineers are aware of the degradation affecting our Issues API between 11:45 and 12:34 UTC. Customers may have experienced degradation affecting the Issues API during this window. Services have now recovered, and…0 minResolved
Jan 22, 2026Third Party Outage Affecting Snyk OperationsGitHub have confirmed service restoration, and all Snyk services have recovered. The Snyk incident Response has been stood down.53 minResolved
Jan 21, 2026Snyk BitBucket Server Broker Integrations DegradedAll affected customers should upgrade to Universal Broker version 5.4.9 to restore service. The Snyk Incident Response has now been stood down.42h 13mResolved
Jan 21, 2026Snyk CLI DegradationAffected customers can restore service by upgrading to the latest stable Snyk CLI release: v1.1302.1. The Snyk Incident Response has now been stood down.48h 47mResolved
Jan 16, 2026Container scans are degraded for images containing JAR filesNo further impact has been observed throughout the monitoring period. The Snyk Incident Response has been stood down.67h 10mResolved
Jan 15, 2026Snyk Recurring Tests DegradedSnyk engineers have been monitoring the environment and confirmed that all systems are operating within normal baselines. The incident response has been stood down.33h 2mResolved
Jan 13, 2026Snyk Code DegradationWe have observed no further impact on services during our monitoring period. The Snyk Incident Response has been stood down.1h 17mResolved
Jan 7, 2026Snyk SCM/API Import DegradationEvent queues have normalised, confirming that all pending imports have completed. We are now observing standard processing times. The Snyk Incident Response team has been stood down.50 minResolved
Dec 29, 2025Partial Degradation of Reachability AnalysisBetween 10:22 and 10:46 UTC on Monday, December 29th, Snyk experienced a partial degradation of backend systems that calculate <a href="https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/reachability-analysis"…1h 0mResolved
Dec 27, 2025Open Source Maven scans degradedThe fix has been successfully implemented, and we are no longer observing any degradation in the Maven scans. Our Incident Response has been stood down.22h 41mResolved
Dec 24, 2025Recurring Tests are DegradedAll recurring tests that were missed on December 23 have now completed successfully.14h 42mResolved
Dec 23, 2025GitHub Cloud Integrations DegradedOur Engineers have observed no further impact, this Incident is now Resolved. The Snyk Incident Response has now been stood down.1h 21mResolved
Dec 18, 2025PNPM project testing and import degraded for SCM scans in regional environmentsThis incident has now been resolved. The Snyk Incident Response has now been stood down.456h 2mResolved
Dec 15, 2025Bitbucket Cloud DegradationWe have identified the root cause of the incident and established that this affects only a small subset of customers. We will be reaching out to those customers in due course. However, as a workaround, customers can…70h 10mResolved
Dec 8, 2025Snyk Open Source and Container DegradationOur Engineers have observed no further impact during our monitoring period. We can confirm that our Snyk Code product would have also experienced degradation as a result of this incident. The Snyk Incident Response…58 minResolved
Dec 2, 2025Errors When Using Broker Image 5.3.0The Snyk Incident response has been stood down. This incident is now resolved.54 minResolved
Nov 28, 2025Snyk UI DegradedThe fix has been successfully implemented, and we are no longer observing any degradation in the Snyk UI. Our Incident Response has been stood down.1h 23mResolved

How to Read This Snyk Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Snyk acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Snyk outage in this window ran 19d, against a mean recovery of 1d 12h. If you depend on Snyk in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.