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

Planned Maintenance Scheduled for May 10th 2025 May 10, 2025 14:00-17:00 UTC

We are informing you about upcoming planned maintenance that will temporarily impact the availability of Snyk services while we upgrade our cloud infrastructure. Maintenance is scheduled to take place between the following times:

Saturday May 10 2025 from 2:00 pm UTC to 5:00 pm UTC
07:00 PDT / 10:00 EDT / 15:00 BST / 00:00 AEDT (start of Sunday 11th in Australia)

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 so we have planned our maintenance activity to minimize disruption.

This will be the second of our 2025 planned maintenance events. As a reminder, we intend to give you a predictable schedule by limiting planned maintenance to the second Saturday of every 3rd month from February 8 2025:

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

We will confirm each event nearer the time with at least 30 days’ advance notice wherever possible.

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 (https://support.snyk.io/).

We appreciate your understanding as we work to improve your experience as a valued customer.
Posted on Apr 03, 2025 - 16:13 UTC
Apr 26, 2025

No incidents reported today.

Apr 25, 2025

No incidents reported.

Apr 24, 2025
Snyk PR Checks for Azure Repositories are Degraded
Resolved - Following continued monitoring, we have not identified any further issues and have been unable to reproduce the problem. We are confident that the issue is resolved.

The Snyk Incident Response has now been stood down.
Apr 24, 08:29 UTC
Monitoring - The fix has now been deployed to our app.snyk.io environment. The fix has now been applied to all multi-tenant environments. Our engineers are monitoring at this time.
Apr 23, 16:22 UTC
Update - The fix has now been deployed to our app.eu.snyk.io and app.au.snyk.io environments.

We will share another update when the rollout has concluded.
Apr 23, 10:00 UTC
Update - The environment on which the fix was initially rolled out was app.us.snyk.io and not app.snyk.io as reported earlier.

Once the rollout to our remaining environments is complete, we will provide a further update.
Apr 23, 08:58 UTC
Update - The fix implemented to our app.snyk.io environment has been successful in mitigating the issue. Our Engineers will proceed with deploying the fix across our remaining environments.

We will provide a further update once the rollout is complete.
Apr 23, 08:22 UTC
Update - Our Engineers have rolled out a fix to our app.snyk.io environment due to the higher volume of expected traffic in this environment. This is to ensure that the issue is mitigated and that services respond well to the changes made.

We will continue to monitor throughout the evening and roll out the fix to all other environments once we have full confidence that the issue is resolved.
Apr 22, 15:56 UTC
Update - Our internal testing remains ongoing. However, it is almost complete.

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

Further updates will be shared once internal testing is completed.
Apr 22, 09:10 UTC
Update - 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.
Apr 17, 15:59 UTC
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.
Apr 17, 12:59 UTC
Update - 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.
Apr 16, 15:22 UTC
Update - 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.
Apr 16, 12:20 UTC
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.
Apr 16, 11:34 UTC
Apr 23, 2025
Apr 22, 2025
IaC+ Issues Degraded
Resolved - Our Engineers have confirmed that services have remained stable.

The Snyk Incident Response has been stood down.
Apr 22, 06:58 UTC
Update - 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.
Apr 17, 09:12 UTC
Update - 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.
Apr 16, 17:49 UTC
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).
Apr 16, 15:57 UTC
Update - Snyk Engineers continue to observe delays affecting IaC+ scans. Remediation efforts remain underway. We will keep you updated on our progress.
Apr 15, 20:58 UTC
Update - Our Engineers are continuing to work on a fix to mitigate the delays affecting IaC+ scans.

We will keep you updated on our progress.
Apr 15, 08:23 UTC
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.
Apr 14, 16:56 UTC
Apr 21, 2025

No incidents reported.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025
Apr 16, 2025
Apr 15, 2025
Google SCC, Amazon EventBridge and AWS Security Hub Integrations Degraded
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.
Apr 15, 11:37 UTC
Apr 14, 2025
Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage