Snyk Status

Recurring Tests are Degraded

Identified - Our Engineers have identified the cause of the degradation and are now working on remediation steps.

Customers may observe that scheduled tests continue to complete at a slower rate than expected.

Further updates will follow.
Apr 02, 2025 - 13:41 UTC

Update - Our Engineers are still investigating the cause of the degradation to our recurring tests within the app.au.snyk.io environment.

Further updates will follow.
Mar 31, 2025 - 14:14 UTC

Investigating - Our Engineers have identified that recurring tests within our app.au.snyk.io environment are degraded.

Customers within the above environment may observe that scheduled tests are completing at a slower rate than expected.

The Snyk Incident Response has been invoked, and we are investigating.
Mar 28, 2025 - 13:56 UTC

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) Degraded Performance

Snyk AppRisk Operational

Snyk Code Degraded Performance

Snyk Container Degraded Performance

Snyk IaC Degraded Performance

Snyk Open Source Degraded Performance

Snyk Learn Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Apr 3, 2025

No incidents reported today.

Apr 2, 2025

Unresolved incident: Recurring Tests are Degraded.

Apr 1, 2025

MT-AU project duplication for some CLI Monitored projects

Resolved - Our Engineers have confirmed that the underlying issue has now been resolved.

The Snyk Incident Response has been stood down.
Apr 1, 13:19 UTC

Identified - Snyk is aware of an issue that impacted customers using the custom branches feature where a subset of projects created using the CLI across the Open Source and Snyk Code products have been duplicated.
The issue caused project duplication, and occurred between 28/03/2025 at 11:00 UTC and 31/03/2025 at 06:30 UTC.

Duplication is no longer happening, and Snyk is working to de-duplicate the affected projects.
Mar 31, 11:10 UTC

Snyk Support services degraded, impacting login, case view and creation, community discussion, and support replies

Resolved - Support services are fully operational.
Snyk incident response is standing down
Apr 1, 06:12 UTC

Monitoring - A fix has been identified and deployed. All support services are restored. We are currently monitoring the results
Apr 1, 03:45 UTC

Investigating - Service to the Snyk support portal (support.snyk.io) is currently degraded.
Customers will not be able to log in to the support portal, view or create cases, use the community discussion, or search knowledge articles.
Customers can create a case by sending an email to support@snyk.io; however, Snyk Support is currently unable to reply to cases.
The service is supported by a third-party vendor, and we are diligently working with them to resolve the issue and restore service.
We will provide an update on this page once the issue is resolved or if there is a material development.
Apr 1, 01:44 UTC

Mar 31, 2025

Mar 30, 2025

No incidents reported.

Mar 29, 2025

No incidents reported.

Mar 28, 2025

Mar 27, 2025

No incidents reported.

Mar 26, 2025

No incidents reported.

Mar 25, 2025

No incidents reported.

Mar 24, 2025

Snyk CLI Upload Reporting Issue

Resolved - The fix has been deployed, and our Engineers have observed no further issues.

The Snyk Incident Response has now been stood down.
Mar 24, 11:39 UTC

Update - A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.

We will keep you updated with our progress.
Mar 21, 14:29 UTC

Identified - Synk Engineers have identified an issue affecting Snyk-US-02, Snyk-EU-01, and Snyk-AU-01. No impact has been observed, and there is a low expectation that this will occur. However, the potential impact occurs when new code vulnerabilities are introduced after March 19th; customers utilizing the Snyk code report (CLI Upload) may observe that previously found issues will be given new identities. As a consequence, these issues will not be ignorable. Snyk engineers are working towards mitigation.
Mar 20, 16:11 UTC

Jira Integration Ticket Creation Failure

Resolved - The fix has been deployed, and our Engineers have observed no further issues.

The Snyk Incident Response has now been stood down.
Mar 24, 10:23 UTC

Update - A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.

We recognise the impact this is having and appreciate your patience while we work to resolve it.

We will keep you updated with our progress.
Mar 21, 14:29 UTC

Update - Our engineers have pinpointed the cause of the problem and are actively working on a solution.

The fix is complex, therefore, it may take a few days for this to reach the production environment.

We will keep you updated on our progress.
Mar 20, 10:33 UTC

Update - Snyk Engineers are preparing the fix. However, no timeline is available at this time. Once available, the fix will be deployed. Additional details to follow.
Mar 19, 20:46 UTC

Identified - Our Engineers have identified the root cause and are taking steps to mitigate the issue.
Mar 19, 20:16 UTC

Investigating - Snyk Engineers are investigating an issue affecting Jira ticket creation using the Jira Integration via the Snyk UI. Customers may observe "Could not get fields" error message when attempting to create Jira tickets via the UI.
Mar 19, 19:02 UTC

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

Snyk Code PR Checks Delayed

Resolved - No further issues have been observed during the monitoring phase, and our Engineers are confident the issue is now resolved.

The Snyk Incident Response has been stood down.
Mar 21, 15:46 UTC

Monitoring - A fix has been deployed, and we are now monitoring to ensure its success.
Mar 21, 15:25 UTC

Investigating - Our Engineers have identified that Snyk PR checks are degraded.

Customers may experience PR Check delays when using Snyk Code.

The Snyk Incident Response has been invoked, and we are investigating.
Mar 21, 15:18 UTC

Mar 20, 2025

AppRisk Integrations Degraded

Resolved - No further issues have been observed during our monitoring phase.

The Snyk Incident Response has now been stood down.
Mar 20, 16:30 UTC

Monitoring - Our Engineers have deployed a fix and are now monitoring to ensure this has been successful.
Mar 20, 15:41 UTC

Identified - Our Engineers have identified that AppRisk integrations are currently degraded.

Customers may observe that integrations within AppRisk have not run as scheduled and that profiles may show up as 'Failed'.

The Snyk Incident Response has been invoked, and we are investigating.
Mar 20, 15:18 UTC