Update - A fix has been rolled out to production, we are currently monitoring it
Jan 27, 2023 - 13:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 27, 2023 - 13:15 UTC
Update - We have identified a potential fix and are in the process of rolling it out
Jan 27, 2023 - 13:13 UTC
Investigating - We are currently investigating this issue.
Jan 27, 2023 - 13:13 UTC
app.snyk.io website
Fetching
Past Incidents
Jan 30, 2023

No incidents reported today.

Jan 29, 2023
Resolved - This incident has been resolved.
Jan 29, 20:04 UTC
Update - Maintenance was successful and is complete.
Jan 29, 20:04 UTC
Update - The maintenance is being monitored, services should now be in working order.
Jan 29, 14:30 UTC
Update - The maintenance is now undergoing, interruptions in service imminent for a short period of time.
Jan 29, 14:18 UTC
Update - Due to a required change in behaviour meant to improve customer experience, we will be scheduling a maintenance window on Sunday, January 29th at 14:10 GMT that will last approximately three hours.

During the maintenance, it is possible that some of the core Snyk services will temporarily experience outages for short periods of time.

What are we changing?
We’ll make changes to the unique definition of a project, making it so the path to the target file is considered part of it.

Why are we doing this and what is the improvement in behaviour?
You will be able to use the CLI’s --project-name flag to apply the same name to multiple projects that have different target files. Normally this action would result in a “Failed due to duplicate project” error message with a 409 status code, but now it will not.

How will it affect you?
If you have been experiencing “Failed due to duplicate project” error messages upon trying to re-import an existing project, that may have been because the path or name of your target file has changed. Projects answering to this criteria can now be updated using snyk monitor successfully.

It is now possible to hold multiple projects that are of the same name and properties and only differ by the name/location of the project’s target file.

Jan 17, 14:58 UTC
Investigating - We are currently investigating this issue.
Jan 17, 14:57 UTC
Jan 28, 2023

No incidents reported.

Jan 27, 2023

Unresolved incident: Increased rate of 502 errors.

Jan 26, 2023

No incidents reported.

Jan 25, 2023
Resolved - This incident has been resolved.
Jan 25, 15:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 25, 15:10 UTC
Update - We have identified the cause of service degradation and have applied a remediation. We are currently monitoring the situation.
Jan 25, 15:04 UTC
Update - Degraded service across Open Source and Container. We are currently investigating this issue.
Jan 25, 14:55 UTC
Investigating - We are currently investigating this issue.
Jan 25, 14:53 UTC
Jan 24, 2023

No incidents reported.

Jan 23, 2023
Resolved - This incident has been resolved.
Jan 23, 20:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 10, 21:51 UTC
Update - Yesterday (2023-01-05) Snyk was made aware of a potential security incident via a tool in our supply chain: https://circleci.com/blog/january-4-2023-security-alert/

Investigations have found no indication of unauthorised access to Snyk resources. As a precautionary measure, all secrets and tokens stored within Snyk’s CircleCI have been rotated.

We will continue to monitor the situation.

Jan 6, 17:18 UTC
Update - As of this morning (2023-01-05) Snyk was made aware of a potential security incident (https://circleci.com/blog/january-4-2023-security-alert/) with a tool in our supply chain.

At present we have no indication of any breach of Snyk data or credentials. We are continuing to actively investigate this report.

Jan 5, 10:48 UTC
Investigating - We are currently investigating this issue.
Jan 5, 10:46 UTC
Jan 22, 2023

No incidents reported.

Jan 21, 2023

No incidents reported.

Jan 20, 2023

No incidents reported.

Jan 19, 2023

No incidents reported.

Jan 18, 2023

No incidents reported.

Jan 17, 2023
Jan 16, 2023

No incidents reported.