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-US-02 (app.us.snyk.io) ? Operational
Snyk AppRisk ? Operational
Snyk Code ? Operational
Snyk Container ? Operational
Snyk IaC ? Operational
Snyk Open Source ? 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-AU-01 (app.au.snyk.io) ? Operational
Snyk AppRisk ? Operational
Snyk Code ? Operational
Snyk Container ? Operational
Snyk IaC ? Operational
Snyk Open Source ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 8, 2024

No incidents reported today.

Sep 7, 2024

No incidents reported.

Sep 6, 2024

No incidents reported.

Sep 5, 2024
Resolved - All scheduled Recurring Tests are running as expected.

The Snyk Incident Response has been stood down.

Sep 5, 15:09 UTC
Update - Our engineers have verified that all daily Recurring Tests planned for September 4th have been successfully completed.

The daily Recurring Tests scheduled for today will begin shortly.

Weekly Recurring Tests remain unaffected and are proceeding as expected.

Sep 5, 12:51 UTC
Monitoring - Our engineers have identified that Recurring Tests were delayed within our app.snyk.io environment.

Customers may observe that their daily Recurring Tests from the 4th of September are delayed or have not executed as expected.

Our engineers have found and fixed the issue that caused the delay and all missed tests will be rescheduled to run today.

Sep 5, 08:20 UTC
Resolved - All scheduled Recurring Tests are running as expected.

The Snyk Incident Response has been stood down.

Sep 5, 15:08 UTC
Update - Our engineers have confirmed that daily Recurring Tests scheduled to execute on the 4th of September have almost completed. There was an issue which we identified and resolved that caused part of the daily Recurring Tests no to execute.

Customers may notice that their daily Recurring Tests are delayed or have not initiated.

The daily Recurring Tests that failed to execute will run as part of today's schedule starting at 14:00 UTC.

Weekly Recurring Tests are unaffected.

Sep 5, 12:50 UTC
Monitoring - Our Engineers took the decision to cancel the delayed daily Recurring Tests scheduled for the 2nd of September, to prevent them from causing a knock-on delay to the tests scheduled for the 3rd of September. As a result, all tests planned for the 3rd of September completed without issue.

We continue to monitor the progress of today's Recurring Tests to ensure there are no further delays.

Weekly Recurring Tests continue to execute as normal and have been unaffected by this incident.

Sep 4, 07:43 UTC
Update - Our Engineer's investigations remain ongoing. Actions were taken which helped to reduce the delays slightly, however, this has not been as significant as we had hoped.

We will keep you updated as the investigation progresses.

Sep 3, 10:19 UTC
Investigating - Our Engineers have identified that daily Recurring Tests are delayed within our app.eu.snyk.io environment.

Customers may observe some delays to their daily Recurring Tests.

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

Sep 3, 08:43 UTC
Resolved - Our engineers have implemented a fix that has resolved the issue.

We do not anticipate any further impact.

The Snyk Incident Response has now been stood down.

Sep 5, 07:14 UTC
Identified - Snyk Engineers have identified a small number of Issues Reporting displaying an incorrect current status. Snyk has enacted our Incident Response. Our Engineers have confirmed the issue and are taking steps to mitigate it.
Sep 4, 17:55 UTC
Sep 4, 2024
Sep 3, 2024
Sep 2, 2024

No incidents reported.

Sep 1, 2024

No incidents reported.

Aug 31, 2024

No incidents reported.

Aug 30, 2024

No incidents reported.

Aug 29, 2024
Resolved - Our Engineers have deployed a fix, which has proved successful.

No further impact is expected and the Snyk Incident Response has now been stood down.

Aug 29, 14:58 UTC
Update - The cause of the issue has now been identified and our Engineers are working to deploy a fix.

We will provide a further update once the fix has been implemented.

Aug 29, 14:02 UTC
Investigating - Our Engineers have identified that non-Github SCM integrations are behaving unexpectedly.

Customers may experience their non-Github SCM integrations resetting, removing all credentials after the 'save' button has been selected under Pull Requests->Automatic fix pull requests settings. As a workaround to this, customers can re-enter their credentials.

Our Engineers have confirmed no projects are lost as a result of this behaviour.

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

Aug 29, 13:50 UTC
Resolved - Our Engineers identified that between 10:18 and 11:46 UTC Bitbucket server integrations were degraded, affecting customers using our app.snyk.io environment.

Customers may have experienced Bitbucket integration resets when making changes, among other Bitbucket integration-related errors.

Our Engineers identified a fix, which has mitigated the impact to our customers.

Aug 29, 12:25 UTC
Aug 28, 2024
Resolved - Snyk Engineerings has taken actions to mitigate the delays in reporting. All systems are now operating within normal parameters. This incident is now resolved.
Aug 28, 23:18 UTC
Identified - Customers may observe delayed data in reports in the multi-tenant US environment (app.snyk.io). Snyk technical teams have identified the issue and are working to mitigate it.
Aug 28, 22:47 UTC
Resolved - Our Engineers have implemented a fix and are no longer seeing issues related to Evidence Graphs.

The Snyk Incident Response has been closed down.

Aug 28, 08:56 UTC
Update - Our Engineers have pinpointed the root cause of the issue. However, investigations are still in progress with an emphasis on finding a resolution.

Additional updates will be shared once a solution has been determined.

Aug 21, 13:30 UTC
Investigating - Our Engineers have identified that Insights Evidence graphs are failing to populate new data.

Customers may observe that Evidence graphs are not showing the most up-to-date information or are failing to load any information.

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

Aug 20, 08:36 UTC
Aug 27, 2024
Resolved - Recurring Tests continue to run as normal and we have observed no further issues.

The Snyk Incident Response has been stood down.

Aug 27, 08:37 UTC
Update - The missed weekly Recurring Test from the 17th of August will be executed as part of the normal run scheduled tomorrow.

The root cause was identified, and monitoring will remain ongoing to confirm no further issues during tomorrow's schedule.

Aug 23, 14:16 UTC
Update - Our Engineers have reported that the re-run of the failed weekly (17th August) Recurring Test has taken longer than expected and has, therefore, been aborted to prevent negatively impacting today's Recurring Tests.

We will provide a further update tomorrow on whether we will attempt to re-run the missed test.

Aug 22, 15:28 UTC
Update - The weekly Recurring Test scheduled for the 17th of August that failed to execute will be initiated shortly by our Engineers. This will ensure that all recurring tests are up to date and on schedule.
Aug 22, 13:01 UTC
Update - Our Engineers have confirmed that Recurring Tests continue to execute as expected. At the moment we are unsure if the missed Recurring Tests from Saturday the 17th of August will be executed before the next scheduled run (24th of August).

The Issues API has experienced no further data latency affecting responses.

We will continue to monitor the progress of our Recurring Tests and provide further updates in due course.

Aug 21, 10:44 UTC
Update - To help mitigate the data latency experienced with Issues API responses our Engineers reduced the Recurring Test rates throughout the weekend. This activity proved successful in completely resolving the data latency.

This affected our scheduled Recurring Tests for Saturday (17th of August), which were not executed. These will be manually executed at a later date (to be confirmed). All other Recurring Tests are running as scheduled.

Aug 19, 08:14 UTC
Update - Our Engineers have implemented a fix to reduce the data latency in the Issues API responses. Monitoring is underway to ensure the success of the applied fix.

Recurring tests continue to execute as expected.

Aug 16, 14:45 UTC
Update - Our Engineers have observed no further issues with recurring tests and are confident our customers should experience no further impact related to their recurring tests.

We are still observing some data latency affecting our Issues API responses, we're continuing to monitor this closely.

Aug 16, 08:01 UTC
Update - Monitoring remains ongoing, however, our Engineers are seeing a significant improvement regarding the data latency affecting Issues API responses. This is now only impacting a small percentage of projects.
Aug 15, 16:33 UTC
Monitoring - Our Engineers have implemented a fix for our recurring tests and are now monitoring to ensure all tests execute as expected.

We are still, however, observing data latency affecting Issues API responses.

We will share a further update once our monitoring period has been completed.

Aug 15, 16:04 UTC
Identified - Our Engineers have identified a potential fix which is currently under review. We will provide a further update shortly.
Aug 15, 13:57 UTC
Update - Our Engineers have confirmed that as a result of the recurring test delays we are observing data latency, which is affecting Issues API responses.
Aug 15, 08:32 UTC
Update - Customers can manually retest as manual testing is unaffected.
Aug 15, 07:55 UTC
Investigating - Our Engineers have identified that our recurring tests are delayed. This is affecting weekly and daily recurring test schedules.

Some customers may observe that their scheduled recurring tests have not executed as expected or are delayed.

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

Aug 15, 07:54 UTC
Aug 26, 2024

No incidents reported.

Aug 25, 2024

No incidents reported.