All Systems Operational
Platform Success Rate (US - Multi Tenant)
Fetching
Past Incidents
Feb 27, 2024
Resolved - Snyk Engineers have confirmed that the fix has been successful.

The Snyk incident process has now been stood down.

Feb 27, 17:02 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 27, 01:38 UTC
Update - We are investigating reports that SCM imports (or API based imports) into Snyk in the MT-AU environment are degraded.
Feb 27, 01:04 UTC
Investigating - We are currently investigating this issue.
Feb 27, 01:03 UTC
Feb 26, 2024
Resolved - Snyk Technical Teams deployed a fix and are now reporting all services have been restored, and no impact is currently being experienced. The Snyk Incident Response process has been stood down. This incident is now resolved.
Feb 26, 23:08 UTC
Identified - Snyk Technical Teams have confirmed that customers cannot download CSV from reporting. Snyk has identified the issue and is taking steps to mitigate the impact. Further updates to follow.
Feb 26, 20:39 UTC
Resolved - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced. This incident is now resolved.
Feb 26, 19:57 UTC
Monitoring - Snyk Monitoring Systems identified an issue with Reporting PDF missing data. Reports are displaying zeros for data and loading indicators across all instances. Snyk Technical Teams have now mitigated this issue and are monitoring the environment.
Feb 26, 17:25 UTC
Resolved - Snyk monitoring systems identified an outage to Snyk Code Scans. Snyk Technical Teams took steps to mitigate the issue. All functions are now operational and have remained stable throughout the monitoring period. The outage was from 12:35 to 13:15 UTC. This incident has been resolved.
Feb 26, 15:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 26, 13:21 UTC
Investigating - We are currently investigating this issue.
Feb 26, 13:11 UTC
Resolved - This incident has been resolved. Data in Reporting has returned to expected availability.
Feb 26, 12:34 UTC
Investigating - Snyk Monitoring tools have identified that there are currently delays impacting data retrieval affecting Snyk reporting for approximately 2% of projects. Some Customers may observe significant delays affecting reporting data.

The Snyk incident response process has been invoked.

Feb 23, 15:53 UTC
Feb 25, 2024

No incidents reported.

Feb 24, 2024

No incidents reported.

Feb 23, 2024
Resolved - Snyk Engineers have confirmed that the fix has been successful.

The Snyk incident process has now been stood down.

Feb 23, 13:55 UTC
Monitoring - Snyk Engineers have implemented a fix to restore stability to the Snyk User Interface. The remediation activities will have caused customers to be logged out of app.snyk.io, customers should log back in as normal.

Monitoring will continue to ensure the success of the implemented fix.

Feb 22, 13:50 UTC
Investigating - We are currently investigating this issue.
Feb 21, 19:24 UTC
Monitoring - Snyk Technical Teams have confirmed response times have stabilized and are monitoring the environment to ensure stability.
Feb 21, 17:26 UTC
Update - Snyk monitoring systems have identified intermittent latency affecting the Snyk User Interface. Customers may see intermittent slow response when using the Snyk User Interface. The Snyk Incident Response process has been evoked. Technical Teams have been engaged and are investigating the issue.
Feb 21, 17:19 UTC
Investigating - We are currently investigating this issue.
Feb 21, 17:15 UTC
Feb 22, 2024
Feb 21, 2024
Resolved - This incident has been resolved.
Feb 21, 11:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 21, 10:59 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 21, 10:40 UTC
Investigating - Users will have seen failures in their outbound webhooks from Snyk starting February 17th.
Feb 21, 10:40 UTC
Resolved - This incident has been resolved.
Feb 21, 07:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 18, 17:52 UTC
Identified - We have identified the issue and are working on mitigation.
Feb 18, 17:44 UTC
Update - We are continuing to investigate this issue.
Feb 18, 12:43 UTC
Investigating - Some users might experience errors when importing projects or running tests for Snyk Code projects using the Gitlab integration.
CLI and IDE operations remain unaffected.

Snyk engineering teams are actively investigating the issue.

Feb 17, 21:00 UTC
Feb 20, 2024

No incidents reported.

Feb 19, 2024
Resolved - Snyk Engineers have confirmed that the fix has been successful. Snyk Code analysis times have normalised.

The Snyk incident response has been stood down.

Feb 19, 16:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 06:58 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 06:39 UTC
Update - Snyk Engineering is currently investigating the causes behind the increased analysis times and possible solutions.
Users may still see longer than usual analysis times and timeouts for Snyk Code.
Open source tests with Reachability enabled will also be affected. However, standard Open Source tests are not affected.

Feb 19, 05:56 UTC
Investigating - We are currently investigating this issue.
Feb 19, 04:30 UTC
Resolved - Snyk Engineers have confirmed that the fix has been successful and no further impact is expected.

The Snyk incident response has been stood down.

Feb 19, 10:12 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 18, 12:31 UTC
Identified - Starting at 20:00 yesterday (2023-02-18), some users might have issues loading the Projects page or dashboard.
Feb 18, 12:15 UTC
Resolved - During the investigation, we identified an issue with internal monitoring systems. There was no actual customer impact.

The monitoring systems have been recovered and the Snyk incident response process has been stood down.

Feb 19, 09:35 UTC
Monitoring - Snyk Monitoring Systems identified that the Snyk platform was degraded between 08:12 and 08:23 UTC. Customers may have experienced downtime or delays during this timeframe. All services have fully recovered.

Investigations are now underway to identify the cause of the degradation.

Feb 19, 08:56 UTC
Feb 18, 2024
Resolved - This incident has been resolved. Data in the database has returned to normal availability. No lasting impact is expected.
Feb 18, 15:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 18, 14:33 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 18, 13:08 UTC
Investigating - The data in the Snyk vulnerability database is currently out of date. The most recent vulnerability information available was uploaded on 2024-02-14.
This means any new vulnerabilities added to our database since then will not be visible in Snyk products and will not be reported by scans.

Engineering teams are currently investigating.

Feb 18, 11:44 UTC
Feb 17, 2024
Completed - We have successfully completed the maintenance. Snyk is up and running, and normal operations can commence.
Feb 17, 21:00 UTC
In progress - Planned work is now underway and will end at around 21.00 GMT today.
Feb 17, 08:56 UTC
Scheduled - Upcoming planned maintenance

We have scheduled maintenance that will temporarily impact the availability of our SaaS services. These are significant enhancements to improve the long-term resilience of the Snyk platform.

Maintenance is currently scheduled to take place:
February 17th at 9 AM GMT to 9 PM GMT
March 2nd at 1 PM GMT to March 3rd 1 AM GMT
March 16th at 1 PM GMT to March 17th 1 AM GMT

We will provide prompt updates here if these dates are adjusted.

During these periods, you may not be able to access Snyk’s services, including the CLI, API, UI and PR checks. For more information on this please check out our Maintenance Guide https://support.snyk.io/hc/en-us/articles/16431412798621.

We understand that our services are important to your business operations and we have designed our maintenance process to minimize inconvenience to our customers. These maintenance windows enable us to upgrade the Snyk platform to our new, more robust and reliable service architecture, to better meet your business needs and to continue to scale in the future.

Follow along at status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team.

Feb 5, 20:04 UTC
Feb 16, 2024

No incidents reported.

Feb 15, 2024

No incidents reported.

Feb 14, 2024
Resolved - The Snyk Incident Response process has been stood down. All Recurring Tests have been re-activated and will run as expected today.
Feb 14, 09:20 UTC
Identified - The issue has been identified.
Feb 13, 15:03 UTC
Investigating - As part of mitigation efforts for the incident Snyk Reporting Data Delayed, the automated recurring tests for the 13th of February will be skipped. We expect tests to execute as usual from the 14th of February.
Feb 13, 15:03 UTC
Resolved - The Snyk Incident Response process has been stood down. There should be no further delays experienced with Reporting.
Feb 14, 08:24 UTC
Monitoring - The underlying remains resolved by the Snyk technical teams. The data flow delay for reporting is now recovered for the majority of projects. A small portion of projects may continue to observe some delay. Snyk technical teams are continuing to monitor the situation.
Feb 13, 18:30 UTC
Update - The underlying issue has been resolved. However, there is still a significant delay in the data flow as we process the backlog. This continues to cause latency for Reporting data. Engineering teams continue to review ways to expedite this.

Further updates to follow.

Feb 13, 15:58 UTC
Update - The underlying issue has been resolved. However, there is still a significant delay in the data flow as we process the backlog. This continues to affect latency for Reporting data. Engineering teams are investigating ways to expedite this.

Further updates to follow.

Feb 13, 14:55 UTC
Update - Snyk Technical Engineers have successfully implemented a fix. However, it is expected that the reporting backlog will take approximately 13 hours to clear.

Customers should be aware that Recurring Tests will also be significantly delayed.

Further updates to follow.

Feb 13, 13:22 UTC
Identified - Snyk Technical Engineers have successfully implemented a fix. However, it is expected that the reporting backlog will take approximately 13 hours to clear.

Further updates to follow.

Feb 13, 12:29 UTC
Monitoring - Snyk Technical Engineers have implemented a fix, initial observations suggest the fix has been successful, however, monitoring remains ongoing.
Feb 13, 10:32 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 13, 09:43 UTC
Investigating - Snyk Monitoring systems have identified that reporting across the Snyk platform is currently delayed by approximately 8 hours.

The Snyk incident response has been invoked and Engineers are troubleshooting the issue.

Further updates to follow.

Feb 13, 08:54 UTC
Feb 13, 2024
Resolved - The Snyk Incident Response process has been stood down. All services have been restored and no impact is currently being experienced.
Feb 13, 20:38 UTC
Monitoring - Snyk Engineers have deployed a fix. A monitoring period is now underway to ensure the incident has been successfully resolved.
Feb 13, 15:44 UTC
Identified - Snyk Engineers have identified and deployed a potential fix. Monitoring is underway to validate the success of the fix.

Further updates to follow.

Feb 13, 14:27 UTC
Update - Snyk Technical Engineers are continuing with troubleshooting activities to identify the cause of the below impact.

The Snyk Security in Jira Cloud Integration is currently experiencing higher than usual latency. This means issues in new Snyk Projects might not yet be visible in Jira as expected.

Feb 13, 13:26 UTC
Investigating - The Snyk Security in Jira Cloud Integration is currently experiencing higher than usual latency. This means issues in new Snyk Projects might not yet be visible in Jira as expected.
Feb 13, 09:50 UTC
Resolved - This incident has been resolved.
Feb 13, 15:14 UTC
Identified - Snyk Engineers have identified and deployed a fix to resolve the IaC+ issue data degradation. Monitoring is underway to validate the success of the fix.

Further updates to follow.

Feb 13, 14:12 UTC
Update - Snyk Engineers continue to investigate the issues causing the below impact.

Issue data for projects in IaC+ is not being updated correctly. This means issue data in new projects or changes in existing projects will not be reflected in the platform.

This does not affect the standard Snyk IaC offering.

Further updates to follow.

Feb 13, 13:00 UTC
Investigating - Issue data for projects in IaC+ is not being updated correctly. This means issue data in new projects or changes in existing projects will not be reflected in the platform.

This does not affect the standard Snyk IaC offering.

Feb 13, 11:19 UTC