Snyk Status

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Resolved: Our Engineers have confirmed that services have remained stable.

The Snyk Incident Response has been stood down.

Monitoring: Our Engineers confirm no further issues have been observed. However, to ensure stability, we will continue to monitor services throughout today and through the weekend.

We will provide a further update on Monday, 21st April.

Monitoring: Snyk Engineers have implemented a fix and, after a period of monitoring, are no longer observing delays. We will continue to monitor to ensure stability.

Monitoring: Our Engineers have implemented a fix to mitigate the load on the environment, and the initial signs are positive.

Some customers will continue observing latency of around 2 hours, which we expect to clear in the evening hours(EMEA).

Identified: Snyk Engineers continue to observe delays affecting IaC+ scans. Remediation efforts remain underway. We will keep you updated on our progress.

Identified: Our Engineers are continuing to work on a fix to mitigate the delays affecting IaC+ scans.

We will keep you updated on our progress.

Identified: Snyk Engineers have identified an issue affecting IaC+ scan results in the SNYK-US-01 (app.snyk.io) environment. The Snyk Incident response has been enacted. Customers will observe a delay with the IaC+ scans displayed in the UI. Our Engineers are aware of the issue and are working to mitigate the delays.

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

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.

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

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.

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.

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.

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Resolved: Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.

Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.

Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Identified: Our internal testing remains ongoing. However, it is almost complete.

During our testing and investigations, we have identified that all our environments will experience this issue.

Further updates will be shared once internal testing is completed.

Identified: Our internal testing remains ongoing, and preliminary indications suggest we are nearing a point where we can effectively mitigate the impact.

Considering the complexity of the solution and the potential risk to other services, we would like to continue with our internal testing until we are completely confident before deploying the fix.

Identified: Our root cause investigation has led us to what we believe is a configuration issue, which causes intermittent behaviours with Azure Repos.

We're currently testing a fix internally to ensure it mitigates the issue.

Investigating: Our Engineers have determined that this issue only affects a small percentage of Azure Repos PR Checks, as we have successfully reproduced this internally.

We are now capturing additional logs for analysis to help us identify and understand the root cause of the issue.

Investigating: Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.

We will keep you updated on the progress of our investigation.

Investigating: Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.

Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.

Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.

The Snyk Incident Response has been invoked, and initial investigations are ongoing.