Snyk Status

Snyk Tests for Gradle projects Degradation

Identified - Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks.
The investigation is ongoing under the Snyk Incident Response process.
May 22, 2026 - 02:29 UTC

SNYK-US-01 (app.snyk.io) Degraded Performance

Snyk AppRisk Operational

Snyk Code Operational

Snyk Container Operational

Snyk IaC Operational

Snyk Open Source Degraded Performance

Snyk Learn Operational

Evo by Snyk Operational

SNYK-US-02 (app.us.snyk.io) Operational

Snyk AppRisk Operational

Snyk Code Operational

Snyk Container Operational

Snyk IaC Operational

Snyk Open Source Operational

Snyk Learn Operational

Evo by Snyk Operational

SNYK-EU-01 (app.eu.snyk.io) Operational

Snyk AppRisk Operational

Snyk Code Operational

Snyk Container Operational

Snyk IaC Operational

Snyk Open Source Operational

Snyk Learn Operational

Evo by Snyk Operational

SNYK-AU-01 (app.au.snyk.io) Degraded Performance

Snyk AppRisk Operational

Snyk Code Operational

Snyk Container Operational

Snyk IaC Operational

Snyk Open Source Degraded Performance

Snyk Learn Operational

Evo by Snyk Operational

SNYK-GOV-01 (app.snykgov.io) Operational

Snyk Code Operational

Snyk Container Operational

Snyk IaC Operational

Snyk Open Source Operational

Snyk Support (support.snyk.io) Operational

Support Portal Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

May 22, 2026

Unresolved incident: Snyk Tests for Gradle projects Degradation.

May 21, 2026

Snyk Import and Recurring Test Degradation

Resolved - All services remain stable after the mitigation. The Snyk Incident Response has been stood down.
May 21, 17:16 UTC

Update - A fix has been deployed, and initial signs are positive.

We will continue to monitor service to ensure services remain stable.
May 21, 14:56 UTC

Identified - Success rates have now recovered. However, the environment remains under close monitoring while our investigation into the root cause and further mitigations continues.

We will keep you updated as we progress.
May 21, 12:22 UTC

Investigating - We're currently investigating degradation affecting our app.snyk.io environment.

Customers may experience slowness and/or failures affecting project imports and recurring tests.

The Snyk Incident Response has been invoked.
May 21, 11:37 UTC

May 20, 2026

Supply Chain Compromise on @antv being investigated for more than 300 packages in npm ecosystem

Resolved - Customer 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 ecosystem, we used this incident to alert customers that they may have projects using the affected package versions.

Snyk Systems: Snyk’s security team has reviewed Snyk's systems, and there is no indication of compromise to Snyk systems, products, or infrastructure. As this issue does not impact the availability or operation of Snyk services, we are resolving this Status Page incident.

Going forward, customer-facing updates, affected package information, and remediation guidance for this issue will be provided through the Snyk Trust Center and related security resources. Snyk will continue to monitor for additional related advisories and update customer-facing resources as needed.
May 20, 14:57 UTC

Update - We are continuing to investigate this issue.
May 19, 21:39 UTC

Update - The Compromised Packages list is now available at https://security.snyk.io/antv-supply-chain-compromise-may-2026
May 19, 10:44 UTC

Update - Our blog post is now available: Mini Shai-Hulud Hits AntV
May 19, 09:13 UTC

Update - Customers can now assess potential impact in the Snyk app by visiting: Analytics → Reports → Zero-Day → Active Security Incident Assessment for Antv Supply Chain Compromise - May 2026

Please continue to refer to the Snyk Trust Center for the latest official updates and customer communications.
May 19, 08:51 UTC

Update - The Snyk Trust Center has been updated.
May 19, 08:45 UTC

Update - Update:
Snyk is continuing to investigate and respond to the ongoing supply chain compromise of @antv and other packages.

Affected packages: Current findings indicate that multiple npm packages have been identified as affected, including packages within the @antv/* namespace and related packages outside the AntV namespace.

Scope: Over 639 malicious package versions across more than 323 unique packages, with numbers subject to change

Cause: Investigations indicate the issue was caused by a compromised npm maintainer account, enabling automated malicious package publishing.

Immediate action you can take:
-Review dependency trees and lockfiles for affected packages, including packages within the @antv/* namespace and additional impacted npm packages size-sensor, echarts-for-react, timeago.js., canvas-nest.js
-Pin to pre-May 19 versions, run npm install --ignore-scripts, rotate all credentials.

We will update here as soon as we have additional information or links
May 19, 07:55 UTC

Investigating - Current scope appears to be: over 630 malicious package versions across more than 315 unique packages, with the AntV suite heavily impacted.
This incident relates to compromised third-party open source packages in the npm ecosystem. There is no indication that Snyk systems, products, or infrastructure were compromised.
As an active investigation, this is subject to change.
We are currently working on confirming the known scope and providing vulnerability advice, reporting, blog, and Trust Center updates.
Please subscribe to this incident for further updates as they become available. Links to additional resources will be provided here.
May 19, 05:29 UTC

Jira Integration Degraded

Resolved - We are no longer observing any impact affecting Jira integration workflows.

The Snyk Incident Response has been stood down.
May 20, 10:51 UTC

Monitoring - A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.
May 19, 19:47 UTC

Identified - Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.
May 19, 15:35 UTC

Investigating - We're currently investigating an issue affecting the Jira integration. Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform.

The Snyk Security In Jira Cloud integration is unaffected.

The Snyk Incident Response has been invoked.
May 19, 14:19 UTC

Scan and Recurring Test Degradation

Resolved - We observed no further impact during our monitoring period.

The Snyk Incident Response has now been stood down.
May 20, 08:06 UTC

Update - 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.
May 19, 20:09 UTC

Investigating - 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.
May 19, 17:08 UTC

May 19, 2026

Service Degradation on US-01 (app.snyk.io)

Resolved - We have identified and deployed a fix restoring normal service.

The Snyk Incident Response has been stood down.
May 19, 14:27 UTC

Update - Our investigation into the root cause remains ongoing. We are currently seeing a reduced frequency of the issue and are continuing to monitor performance closely.

Further updates will be provided as our investigation progresses.
May 19, 11:22 UTC

Update - Our investigations into the root cause remain ongoing.

We will keep you updated with our progress.
May 18, 14:57 UTC

Investigating - Snyk Engineers have identified degraded performance in the Multi-Tenant US-01 environment (app.snyk.io), affecting multiple services. The investigation is ongoing under the Snyk Incident Response process.
May 18, 12:12 UTC

May 18, 2026

Snyk PR Degradation

Resolved - Following 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 details, please follow: Service Degradation on US-01 (app.snyk.io).
May 18, 12:53 UTC

Investigating - We're currently investigating intermittent degradation affecting PR events.

This is affecting GitHub, GitLab, Bitbucket Cloud and Bitbucket Server integrations.

The Snyk Incident Response has been invoked.
May 18, 11:19 UTC

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026

No incidents reported.

May 14, 2026

No incidents reported.

May 13, 2026

Reporting PDF Degraded

Resolved - Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.
May 13, 19:01 UTC

Investigating - Snyk engineers are investigating degraded performance with the Reporting PDF in the Snyk-US-01 multi-tenant environment. Customers may observe longer generation times or failures to generate reports.
May 13, 14:49 UTC

May 12, 2026

Snyk Recurring Tests Delayed

Resolved - We 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.
May 12, 07:20 UTC

Update - We continue to see improvements as a result of the mitigation actions taken. However, we will monitor to ensure services fully recover.
May 11, 14:19 UTC

Identified - We have identified the root cause of the delays and implemented mitigations.

Some customers may still experience delayed daily recurring tests while these changes fully propagate

We will continue to monitor the situation to ensure the mitigations have been successful.
May 8, 13:02 UTC

Update - We are continuing to investigate the root cause of the delays.

Customers may still experience delays affecting a small percentage of daily recurring tests.
May 7, 13:19 UTC

Investigating - Snyk engineers have noticed delays in a small percentage of daily recurring tests in the Multi-Tenant Synk-US-01 (app.snyk.io) environment. The impact is limited to daily tests; weekly tests remain unaffected.

Snyk engineers are investigating the issue.
May 6, 15:32 UTC

May 11, 2026

GitHub Integration Service Degraded

Resolved - The 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.
May 11, 14:41 UTC

Identified - We are currently experiencing degraded performance with our GitHub integrations due to an ongoing, broader service disruption on GitHub’s end. Our team is actively monitoring the situation and will automatically restore full connectivity as soon as the upstream issue is resolved.
May 11, 14:35 UTC

May 10, 2026

No incidents reported.

May 9, 2026

Planned Maintenance Scheduled for 9th of May 2026

Completed - The maintenance work is now complete. Snyk is now available.
May 9, 15:33 UTC

Verifying - We’re working through the final tasks and we expect to complete maintenance on time.
May 9, 15:13 UTC

Update - Maintenance is under way and progressing as expected.
May 9, 14:22 UTC

Update - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 9, 14:01 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 9, 14:00 UTC

Update - We’re about to commence scheduled maintenance. During this time Snyk services may be unavailable for up to 3 hours and users of PR checks, CLI, API, and UI will be impacted. Thanks for your patience while we complete this essential work.

Regular updates will be posted to the status page throughout the maintenance window.
May 9, 13:45 UTC

Update - Maintenance will begin as scheduled in 50 minutes.
May 9, 13:10 UTC

Scheduled - Maintenance is scheduled to take place between the following times:
Saturday 9th May 2026 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 be able to access Snyk services. We understand that our availability may be critical to your business operations and we have planned our maintenance activity to minimize disruption.

We continue with our established maintenance schedule, happening every 3 months on the second Saturday of the month.

Upcoming maintenance windows:
11th April 2026 (already communicated)
9th May 2026
8th August 2026
14th November 2026

We will confirm each of these events nearer the time and wherever possible we will provide you with at least 30 days’ advance notice.

We have a support page summarizing what you can expect during the downtime, and to suggest mitigations you could consider. On the day of maintenance, our team will keep you informed of our progress via updates at status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team.

We appreciate your understanding as we work to improve your experience as a valued customer.
Apr 9, 16:01 UTC

May 8, 2026

CLI Monitor Degredation

Resolved - CLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.
May 8, 21:51 UTC

Monitoring - Snyk engineers are currently investigating degraded performance in Multi-Tenant Snyk US-01. Customers may experience failures with the CLI Monitor. Our engineers have implemented a mitigation strategy and have observed an increase in the CLI Monitor's success rate. We are actively monitoring the environment.
May 8, 19:09 UTC