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
Scheduled Maintenance
Update - This is a reminder that Snyk will be performing planned maintenance this Saturday. In an update to previous communications, we are reducing the duration to 2 hours.

The start time is unchanged: Saturday February 8 2025 at 3:00 pm UTC
which corresponds to 02:00 AEDT (9/2/2025) / 15:00 GMT / 10:00 EST / 07:00 PST

Feb 05, 2025 - 15:20 UTC
Scheduled - As a valued Snyk customer, we are informing you about upcoming planned maintenance that will temporarily impact the availability of your SaaS services while we upgrade our cloud infrastructure.

Maintenance is scheduled to take place between the following times:

Saturday February 8 2025 from 3:00 pm UTC to 6:00 pm UTC
02:00 AEDT (9/2/2025) / 15:00 GMT / 10:00 EST / 07:00 PST

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.

For 2025, we intend to give you more time to plan by establishing a predictable maintenance schedule as follows: Every 3 months on the second Saturday of the month starting on February 8 2025:

* February 8 2025
* May 10 2025
* August 9 2025
* November 8 2025

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 put together a support page: https://support.snyk.io/s/article/Snyk-Maintenance---Planning-Guidance to summarize 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 https://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.

Jan 08, 2025 - 18:04 UTC
Past Incidents
Feb 7, 2025

No incidents reported today.

Feb 6, 2025

No incidents reported.

Feb 5, 2025

No incidents reported.

Feb 4, 2025

No incidents reported.

Feb 3, 2025

No incidents reported.

Feb 2, 2025

No incidents reported.

Feb 1, 2025

No incidents reported.

Jan 31, 2025

No incidents reported.

Jan 30, 2025

No incidents reported.

Jan 29, 2025

No incidents reported.

Jan 28, 2025
Resolved - No connectivity issues were detected during our monitoring period.

The Snyk Incident Response has now been stood down.

Jan 28, 07:58 UTC
Monitoring - Snyk Engineers have completed mitigating the incident and no longer observe the previous degradation. Snyk will continue to monitor the environment throughout the weekend to ensure stability before standing down our Incident Response.
Jan 24, 16:47 UTC
Identified - Snyk Engineers have identified the cause of degradation affecting our SCMs in the European environments. Our Engineers have taken steps to mitigate the issue and are no longer observing errors, timeouts, or traffic bursts. Synk Engineers are continuing their activities to fully mitigate this incident. Further updates to follow.
Jan 24, 16:28 UTC
Investigating - We have identified service degradation across our SCMs that is causing an impact on our services in our European environments. The Snyk Incident Response is now in flight and our Engineers are actively investigating to resolve. Further updates will follow.
Jan 24, 13:44 UTC
Jan 27, 2025
Resolved - Customers impacted by the issue should update to CLI v1.1295.2. Those using CLI v1.1295.0 are not required to make any changes.

The Snyk Incident Response has now been stood down.

Jan 27, 11:42 UTC
Monitoring - Customers using the latest CLI release (v1.1295.1) may observe their CLI scans failing. Snyk Engineers have confirmed that a new CLI (v1.1295.2) release is available for those customers using CLI (v1.1295.1). Customers currently on CLI (v1.1295.0) do not need to upgrade to (v1.1295.2).
Jan 24, 20:19 UTC
Update - We are continuing to investigate this issue.
Jan 24, 17:05 UTC
Update - Error rates have been confirmed as low and we can advise that the impact will only be experienced by a small subset of Snyk users. The Snyk incident response remains in flight and technical teams focused on working to resolve the issue. Further updates will be provided.
Jan 24, 15:57 UTC
Investigating - Our Engineers have identified degradation affecting CLI scans.

Some customers may observe their CLI scans failing when using the latest CLI release (v1.1295.1).

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

Jan 24, 09:53 UTC
Resolved - During our monitoring period, no additional issues were detected.

The Snyk Incident Response has now been stood down.

Jan 27, 09:37 UTC
Monitoring - We identified and mitigated the root cause of the intermittent errors following co-op investigations with our cloud services provider. We are monitoring the environment to ensure stability following the fix. No re-occurrences have been observed.
Jan 24, 17:17 UTC
Jan 26, 2025

No incidents reported.

Jan 25, 2025

No incidents reported.

Jan 24, 2025
Resolved - We identified and mitigated the root cause of the intermittent errors following co-op investigations with our cloud services provider. The incident has now been classified as resolved and no additional errors have been identified since approximately 11.20 UTC.
Jan 24, 16:23 UTC
Identified - We have identified intermittent connectivity errors impacting service stability across our US Environment. Our incident response process is now in flight and our Engineering teams are investigating the matter.

The impact is confirmed as minor, however, customers may well experience intermittent errors across the Snyk suite of products hosted in the US.

Our Engineers remain active and engaged and are working to resolve the problems noted above. Further updates will follow.

Jan 24, 12:23 UTC
Resolved - Atlassian has resolved their incident affecting Jira applications. Snyk Engineers have validated that no further impact is being observed. The Snyk Incident Response has been stood down.
Jan 24, 15:30 UTC
Investigating - Our Engineers have identified degradation affecting Snyk Security in Jira Cloud. We are aware Atlassian have reported issues affecting Jira applications.

Customers utilising Snyk Security in Jira Cloud may notice that vulnerabilities are not being populated within Security Containers.

The Snyk Incident Response has been invoked, and our Engineers are investigating. Initial indications suggest that the Snyk platform is operating as expected.

Jan 24, 09:38 UTC