outages.live
Live

Snyk

Snyk is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

27

Days with an incident

41

Median duration

7 h 1 min

Longest incident

5 days

Components

38

SNYK-US-01 (app.snyk.io)

Snyk AppRisk Operational
90 days ago8 days with an incidentToday
Snyk Code Operational
90 days ago27 days with an incidentToday
Snyk Container Operational
90 days ago21 days with an incidentToday
Snyk IaC Operational
90 days ago21 days with an incidentToday
Snyk Open Source Operational
90 days ago29 days with an incidentToday
Snyk Learn Operational
90 days agoNo incidentsToday
Evo by Snyk Operational
90 days agoNo incidentsToday
Snyk API & Web Operational
90 days ago5 days with an incidentToday
Snyk Secrets Operational
90 days ago6 days with an incidentToday

SNYK-US-02 (app.us.snyk.io)

Snyk AppRisk Operational
90 days ago1 day with an incidentToday
Snyk Code Operational
90 days ago7 days with an incidentToday
Snyk Container Operational
90 days ago3 days with an incidentToday
Snyk IaC Operational
90 days ago3 days with an incidentToday
Snyk Open Source Operational
90 days ago8 days with an incidentToday
Snyk Learn Operational
90 days agoNo incidentsToday
Evo by Snyk Operational
90 days agoNo incidentsToday
Snyk API & Web Operational
90 days ago2 days with an incidentToday

SNYK-EU-01 (app.eu.snyk.io)

Snyk AppRisk Operational
90 days ago5 days with an incidentToday
Snyk Code Operational
90 days ago11 days with an incidentToday
Snyk Container Operational
90 days ago11 days with an incidentToday
Snyk IaC Operational
90 days ago7 days with an incidentToday
Snyk Open Source Operational
90 days ago16 days with an incidentToday
Snyk Learn Operational
90 days agoNo incidentsToday
Evo by Snyk Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration3 h 32 min10:44 to 14:16BitBucket Cloud Integrations DegradedPartial outage

Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.

Oct 23, 2026

Duration3 days14:10 to 09:41Snyk Test Down in SNYK-US-01Partial outage

Services have remained stable throughout the weekend, and we do not expect any further impact. The Snyk Incident Response has been stood down.

Duration6 h 5 min03:56 to 10:02Snyk Support portal degradationDegraded

There have been no further interruptions to our service, declaring the incident as resolved.

Oct 22, 2026

Duration3 days21:53 to 07:44Snyk Container Degradation in SNYK-US-01Partial outage

Services have recovered, and Snyk Container is operating normally in SNYK-US-01 . Services have remained stable throughout our monitoring period. The Snyk Incident Response has been stood down.

Oct 20, 2026

Duration2 h 58 min16:33 to 19:31PR Check Invalid Credential ErrorDegraded

Post-mitigation monitoring confirms that all Snyk services are operating normally and remain stable. The incident response team has stood down, and this incident is now resolved.

Oct 17, 2026

Duration3 days01:43 to 22:02Snyk Code Performance Degraded in SNYK-US-02Degraded

All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.

Oct 15, 2026

Duration1 h 7 min20:39 to 21:47PR Checks and Imports Degraded in SNYK-US-01Degraded

All services remain operational during the monitoring period. The Snyk Incident response has been stood down.

Oct 13, 2026

Duration25 h 21 min07:32 to 08:53GitLab Cloud Integration DegradedDegraded

GitLab are still monitoring their services, but we have seen no further impact on Snyk integrations in the last 24 hours. This incident has been resolved, and the Snyk Incident Response has been stood down.

Oct 8, 2026

Duration21 h 5 min10:03 to 07:08Snyk Open Source and Container DegradationDegraded

Services have remained stable throughout our monitoring period, and the Snyk Incident Response has been stood down.

Oct 7, 2026

Duration26 h 38 min15:04 to 17:42Snyk CLI Tests - 504 Gateway TimeoutsDegraded

We have observed no further impact during our monitoring period. The Snyk Incident Response has been stood down.

Oct 6, 2026

Duration1 h 5 min22:53 to 23:58Snyk CLI SCA Scans Degraded due to Enrichment of Test FailureDegraded

We monitored the system and confirmed stable recovery. No further impact has been observed following the mitigation, the CLI SCA tests are completing normally. The Snyk Incident Response has been stood down.

Duration21 h 57 min14:37 to 12:34Snyk CLI Tests - 504 Gateway TimeoutsDegraded

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Oct 3, 2026

Duration5 days19:49 to 12:56Issues API V3 Service - DegradedDegraded

We're no longer observing delays affecting the Issues API V3 service. The Snyk Incident Response has been stood down.

Sep 28, 2026

Duration3 days14:26 to 12:33Snyk CLI Scans DegradedDegraded

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Duration4 h 24 min07:51 to 12:15Snyk CLI Scans DegradedDegraded

No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

Maintenance

Planned Maintenance Scheduled for 14th of November 2026

As a valued Snyk customer, we are informing you about upcoming planned maintenance that will temporarily impact the availability of your SaaS services while we upgrade our cloud infrastructure. Maintenance is scheduled to take place between the following times: Saturday 14th of November from 3:00PM UTC to 6:00PM UTC 07:00 PST / 10:00 EST / 15:00 GMT / 16:00 CET / 02:00 AEDT (+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: 14th November 2026 13th February 2027 15th May 2027 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 down

Maintenancestarts in 13 d

Follow Snyk

Your coding agent knows when Snyk is down, and tells you when a failure is theirs, not yours. You can also get Snyk incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "snyk" and tell me if Snyk has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=snyk
Slack
/feed subscribe https://outages.cc/feed.xml?providers=snyk

Go from tracking outages to fixing production issues with Polylane.

Try Polylane