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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Mar 24, 2025
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
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
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
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
Mar 19, 2025
Resolved - Our Engineers are confident the incident is now resolved.

The Snyk Incident Response has been stood down.

Mar 19, 13:27 UTC
Monitoring - Our Engineers have deployed a fix and are monitoring the situation to ensure its success.
Mar 19, 12:22 UTC
Investigating - Our Engineers have identified an issue impacting Snyk Learn.

Customers may notice that they are unable to log in to Snyk Learn.

The Snyk Incident Response has been invoked, and we are investigating.

Mar 19, 12:03 UTC
Mar 18, 2025

No incidents reported.

Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.

Mar 14, 2025
Resolved - Our Engineers have deployed an additional fix, resolving the issue in our app.snyk.io environment. All environments are now operating as expected.

The Snyk Incident Response has now been stood down.

Mar 14, 14:09 UTC
Identified - Our Engineers implemented a fix which has improved the error rate across our environments. However, our customers using our app.snyk.io environment may still experience issues when scanning JAR files.
Mar 13, 10:01 UTC
Update - Number of errors has dropped significantly since the mitigation was applied. We're continuing to monitor.
Mar 8, 15:17 UTC
Update - We've applied a mitigation to the issue, and will be monitoring it over the next few hours to ascertain its efficacy.
Mar 8, 11:52 UTC
Update - We have found a potential explanation for the failures, and are working to confirm it. We will share additional updates as we obtain more information.
Mar 8, 11:24 UTC
Update - We have found a potential explanation for the failures, and are working to confirm it. We will share additional updates as we obtain more information.
Mar 8, 11:23 UTC
Update - Failures are intermittent - users may experience tests on JAR files fail and succeed shortly after. We'll provide a full update as soon as we have additional details.
Mar 8, 10:16 UTC
Update - We're experiencing issues scanning JAR files in both Snyk Open Source and Snyk Container. The issue affects all environments.
Mar 8, 09:39 UTC
Investigating - We are currently investigating this issue.
Mar 8, 09:36 UTC
Mar 13, 2025
Resolved - This incident has been resolved.
Mar 13, 18:32 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 13, 18:20 UTC
Mar 12, 2025
Resolved - We have identified the issue and have taken the required restorative actions. Al services impact have now been restored.
Mar 12, 17:55 UTC
Identified - Our Engineers have identified that there is degradation affecting Snyk tests within our app.us.snyk.io environment.

Customers may observe degradation in testing functionality (manual and recurring), with some failing or not initiating as scheduled.

The Snyk Incident Response has been invoked and our Engineers are investigating.

Mar 12, 16:54 UTC
Mar 11, 2025

No incidents reported.

Mar 10, 2025
Resolved - It has been confirmed that data freshness is now back to normal. The incident has been resolved.
Mar 10, 12:08 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 10, 11:12 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 10, 09:47 UTC
Investigating - We are currently experiencing an incident that is causing a delay in the population of the data for both the Reporting page and REST Issues API. As a result, there may be a delay of up to one hour for the data to appear as expected.
Mar 10, 09:40 UTC