All Systems Operational

SNYK-US-01 (app.snyk.io) ? Operational
Snyk AppRisk ? Operational
Snyk Code ? Operational
Snyk Container ? Operational
Snyk IaC ? Operational
Snyk Open Source ? Operational
Snyk Learn ? 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
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
SNYK-AU-01 (app.au.snyk.io) ? Operational
Snyk AppRisk ? Operational
Snyk Code ? Operational
Snyk Container ? Operational
Snyk IaC ? Operational
Snyk Open Source ? Operational
Snyk Learn ? Operational
SNYK-GOV-01 (app.snykgov.io) ? Operational
Snyk Code ? Operational
Snyk Container ? Operational
Snyk IaC ? Operational
Snyk Open Source ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jul 18, 2025
Snyk Services Impacted
Resolved - This incident has been resolved after confirmation from our third party.
Snyk's Incident Response has been stood down.
Jul 18, 18:06 UTC
Identified - Our Incident Response team has identified several Snyk services impacted due to a third-party provider issue.
We are working with our third-party provider on this issue and will provide additional updates as they become available.
Jul 18, 16:52 UTC
Jul 17, 2025
Container Scanning in Pipelines Degraded
Resolved - Snyk engineers have monitored the fix, and all services are functioning as expected. The Snyk incident response has been stood down, and the incident is now resolved.
Jul 17, 21:15 UTC
Monitoring - Our engineers have deployed a fix to address the issue leading to failed scans.

We are now monitoring to ensure the success of the fix.
Jul 17, 11:40 UTC
Identified - Our Engineers have identified what they believe to be the root cause of the issue and are now working on a fix.

We will keep you updated with our progress.
Jul 17, 06:24 UTC
Investigating - Snyk is currently investigating reports of failed scans related to container images. The Snyk incident response team has been activated and investigating this issue further. Current impact scope appears to be limited to scans of locally built images within pipelines that use Snyk images, such as GitHub Actions and Bitbucket pipelines, when utilizing the latest CLI version (1.1298.0).
Jul 16, 20:13 UTC
Jul 16, 2025
Weekly Recurring Tests Degraded
Resolved - All Recurring Tests are now up to date and running as expected.

The Snyk Incident Response has now been stood down.
Jul 16, 08:10 UTC
Update - Our Engineers have confirmed that all services have returned to normal.

Missed Recurring Tests within our app.snyk.io environment are currently being re-run. We will provide a further update once these have been completed.
Jul 14, 11:31 UTC
Update - The cause of the incorrectly quarantined projects has been resolved.
We are still working on restoring projects with a weekly retest schedule that were quarantined since the start of the issue, so that these projects can be scheduled for their next weekly recurring test.

Customers can also still trigger a manual test for affected projects via the project page in the UI

This may result in some projects which were correctly quarantined being re-activated - however these would then be quarantined again by the usual process.
Please note that quarantined tests do not affect the Active/Inactive status of the projects.
Jul 10, 07:50 UTC
Update - We are continuing to work on a fix for this issue: The cause of the incorrect quarantine has been resolved and we are working on restoring the recurring test cadence for affected projects
Jul 10, 00:06 UTC
Identified - Snyk engineers have identified an issue affecting recurring weekly project tests across all environments. Customers may observe that some tests are being incorrectly quarantined. The Snyk Incident Response has been activated, and a fix is being deployed.
Jul 9, 20:00 UTC
Jul 15, 2025

No incidents reported.

Jul 14, 2025
Snyk Platform Degradation
Resolved - Snyk experienced a performance degradation on the platform from 2:20 PM UTC to 2:40 PM UTC.
The issue is now resolved, and the platform is fully operational.
Jul 14, 15:18 UTC
Jul 13, 2025

No incidents reported.

Jul 12, 2025

No incidents reported.

Jul 11, 2025

No incidents reported.

Jul 10, 2025
Jul 9, 2025
Snyk Code Autofix AI degraded for users in Snyk’s US-01 (app.snyk.io) tenant.
Resolved - This incident has been resolved.
Jul 9, 14:02 UTC
Monitoring - We have identified the issue and implemented mitigation. Availability is back to normal and we are currently monitoring stability.
Jul 9, 13:58 UTC
Investigating - Snyk Engineering have detected that Snyk Code Autofix AI (previously known as Deepcode AI Fix) is currently degraded for all users in the US-01 tenant (those who login to the Snyk Portal via app.snyk.io or use the api.snyk.io endpoint). This issue started at UTC: Jul 09 13:52:34.380
Other tenants are not affected, and Snyk Code scanning is operational.
We are currently investigating and will share a further update with more information as soon as possible.
Jul 9, 13:36 UTC
Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025
Recurring Tests Degraded
Resolved - All Recurring Tests have run as scheduled, and we expect no further impact.

The Snyk Incident Response has been stood down.
Jul 4, 14:31 UTC
Update - Our Engineers would like to continue monitoring to ensure all Recurring Tests execute as expected on Wednesday and Thursday (2nd & 3rd July) before confirming the incident as resolved.

Customers on our app.snyk.io environment may observe that weekly Recurring Tests scheduled for the 25th & 26th of June did not initiate. We have taken the decision not to manually trigger these tests to prevent further delays. These tests can be manually triggered by customers if required.

Further updates will be provided if we observe any impact.
Jul 1, 08:23 UTC
Update - We will continue to monitor over the coming days to ensure there is no further impact on our Recurring Tests.

Further updates will be provided if we observe any impact.
Jun 30, 10:09 UTC
Monitoring - The engineering team has implemented a fix for the Recurring Test issues. Customers may continue to experience delays of around 24–48 hours, affecting their Recurring Tests.

We are actively monitoring the situation to confirm the fix is effective and to ensure all delays are resolved.
Jun 27, 14:08 UTC
Investigating - During our monitoring phase, we identified further impact to our weekly Recurring Tests.

Customers may notice that their scheduled weekly Recurring Tests have not initiated as expected.

Our Engineers are investigating the root cause of the issue.

We will continue to keep you updated on our progress.
Jun 27, 10:49 UTC
Monitoring - Our Engineers have deployed a fix to resolve the root cause of the incident.

All Recurring Tests (daily and weekly) scheduled for today will run as expected.

Weekly Recurring Tests that failed to execute on the 25th of June will be manually triggered and completed before the end of the day on the 27th of June.

We will continue to monitor throughout this evening and tomorrow to ensure all tests run as above.
Jun 26, 12:07 UTC
Update - Our investigations into the root cause of the incident remain ongoing.

We will continue to keep you updated on our progress.
Jun 26, 11:38 UTC
Investigating - Our Engineers have identified degradation affecting the Daily and Weekly Recurring Tests.

Customers may observe that Recurring Tests scheduled for the last 12 hours are not executing.

The Snyk Incident Response has been invoked, and our investigations are underway.
Jun 26, 08:44 UTC
← Incident History Powered by Atlassian Statuspage