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
SNYK-GOV-01 (app.snykgov.io) Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Support (support.snyk.io) Operational
Support Portal Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Planned Maintenance Scheduled for 11th of April 2026 Apr 11, 2026 14:00-17:00 UTC

Maintenance is scheduled to take place between the following times:
Saturday 11th April 2026 from 2:00PM UTC to 5:00PM UTC
07:00 PDT / 10:00 EDT / 15:00 BST / 16:00 CEST / 00:00 AEST (+1)

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

We continue with our established maintenance schedule, happening every 3 months on the second Saturday of the month.

Upcoming maintenance windows:
11th April 2026
9th May 2026
8th August 2026
14th November 2026

We will confirm each of these events nearer the time and wherever possible we will provide you with at least 30 days’ advance notice.

We have a support page summarizing 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 status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team.

We appreciate your understanding as we work to improve your experience as a valued customer.
Posted on Mar 11, 2026 - 13:13 UTC
Apr 5, 2026

No incidents reported today.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

Apr 1, 2026
Snyk Recurring Tests Degraded
Resolved - We are no longer experiencing delays affecting recurring tests.

The Snyk Incident Response has now been stood down.
Apr 1, 12:57 UTC
Investigating - We are investigating degradation affecting Snyk Recurring Tests.

Some Customers may notice that their daily recurring tests are delayed.

The Snyk Incident Response has been invoked.
Mar 31, 11:30 UTC
Mar 31, 2026
Snyk GitHub Cloud App Integrations Degraded
Resolved - No further issues have been observed during our monitoring period.

The Snyk Incident Response has been stood down.
Mar 31, 13:02 UTC
Monitoring - We are no longer observing degradation. However, we are monitoring the services to ensure they remain stable.
Mar 31, 11:29 UTC
Investigating - We are currently investigating a service degradation affecting customers using our GitHub Cloud App integration.

Customers may experience delays or failures affecting their Snyk scans.

The Snyk Incident Response has been invoked.
Mar 31, 09:46 UTC
Mar 30, 2026
Snyk Recurring Tests Degraded
Resolved - Services remain stable during the monitoring period. The Snyk Incident Response has been stood down.
Mar 30, 15:39 UTC
Monitoring - Our mitigation steps have been successful, and we're no longer observing delays affecting recurring tests.

We will continue to monitor to ensure services remain stable.
Mar 27, 15:57 UTC
Identified - To resolve the issues causing test delays and ensure system stability, we are temporarily reverting our recent Reachability engine updates for Java and JavaScript.

As a direct result of this rollback, customers may observe the following temporary effects:

Fluctuations in the Reachability status for Java and JavaScript vulnerabilities.
Changes to the corresponding Risk and Priority Scores.
Mar 26, 15:50 UTC
Update - Our Engineers have identified the likely root cause of the delays and are working to deploy a fix.

In the meantime, a small percentage of daily recurring tests may still be affected.
Mar 26, 14:01 UTC
Update - We're still observing delays affecting recurring tests, and our troubleshooting efforts remain ongoing.

We will provide a further update tomorrow.
Mar 25, 15:16 UTC
Update - Our Engineers are continuing their mitigation efforts. However, a small percentage of customers may continue to observe delays affecting daily recurring tests.

We will continue to keep you updated with our progress.
Mar 24, 15:54 UTC
Update - Delays are still affecting a small portion of our weekly and daily recurring tests.

We will continue to keep you updated on any progress.
Mar 23, 16:00 UTC
Update - We continue to observe delays affecting a small portion of daily and weekly recurring tests.

Our investigations remain ongoing, and we will have a further update to share after 16:00 UTC.
Mar 23, 14:43 UTC
Update - We're continuing to observe delays affecting a small portion of daily recurring tests.

We expect any missed tests from yesterday to be picked up during today's run.

Our investigations remain ongoing, and we will continue to keep you updated with our progress.
Mar 20, 13:28 UTC
Update - A small portion of daily recurring tests are still experiencing delays.

We will continue to keep you updated as we progress.
Mar 19, 15:04 UTC
Investigating - Our Engineers are investigating the degradation affecting Snyk Recurring Tests.

Some Customers may notice that their daily recurring tests have not executed as expected.

The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Mar 18, 13:30 UTC
Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026
Mar 26, 2026
Mar 25, 2026
Degradation of Bitbucket Cloud integration services
Resolved - We have observed no further issues during our monitoring period.

The Snyk Incident Response has now been stood down.
Mar 25, 09:00 UTC
Monitoring - The mitigation is now live. Our team will remain in a monitoring phase through 6 PM UTC to ensure continued stability
Mar 24, 16:37 UTC
Update - We have deployed a fix that enables a workaround for project imports using the BitBucket Connect App. As this rolls out, you may experience temporary failures with these imports for up to 30 minutes. If you experience an issue, we recommend waiting a few minutes before trying again.
Mar 23, 14:05 UTC
Identified - During our monitoring phase, we have become aware that customers using Bitbucket Connect App integrations may be unable to import new repositories.

We are investigating this and will keep you updated on our progress.
Mar 23, 12:18 UTC
Monitoring - A fix has been implemented, and we are now monitoring to ensure services fully recover.
Mar 23, 08:26 UTC
Identified - Customers using the Bitbucket Cloud integrations may see degradation in service affecting any use of the Bitbucket Cloud integrations, including:

Creating/Editing Bitbucket Integration,
Listing repos for import,
Import (via UI or API)
Tests, Recurring Tests, PR Checks
Fix PRs


We have identified the cause of the issue and are working towards remediation.
Mar 23, 00:45 UTC
Mar 24, 2026
Free Users Unable to Sign up for Snyk
Resolved - Our Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform.

The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Mar 24, 17:45 UTC
Identified - Our Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform.

The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Mar 24, 17:21 UTC
Mar 23, 2026
Mar 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage