Live

Snyk EVO Login Issues

0

Following further investigation, we have confirmed that the issue also affects logging in to the Snyk Evo UI within our app.au.snyk.io environment. Snyk Evo services are otherwise operating normally. Our engineers are working on a fix, and we will share a further update shortly.

The latest update from Snyk.

State

Identified

Started

Ongoing for

55 min

Worst impact

Degraded

Timeline

2 updates
15:0015:1415:2815:4115:55
DegradedUpdate postedTimes in UTC

Identified

55 min 100%

Updates

Times in UTC

As posted by Snyk

Identified

Following further investigation, we have confirmed that the issue also affects logging in to the Snyk Evo UI within our app.au.snyk.io environment. Snyk Evo services are otherwise operating normally. Our engineers are working on a fix, and we will share a further update shortly.

Identified

We have identified an issue preventing customers from logging in to the Snyk Evo UI within our SNYK-US-01 environment. Snyk Evo services are otherwise operating normally. Our engineers are working on a fix, and we will share a further update shortly. The Snyk Incident Response has been invoked.

Affected components

3
Evo by SnykSNYK-US-01 (app.snyk.io) - Evo by SnykSNYK-AU-01 (app.au.snyk.io) - Evo by Snyk

Snyk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

40

Median duration

14 h 16 min

This incident

94% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days
median 14 h 16 min
90 days agoToday

Other Snyk incidents

All incidents

Snyk·Snyk Open Source Degraded

Our engineers are investigating degraded performance affecting Snyk Open Source for customers within our app.au.snyk.io environment. Customers may experience slower response times or errors when running tests and importing projects. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

Degraded

Snyk·Snyk Open Source and Container Degradation

Between 13:20 and 13:35 UTC, customers within our app.snyk.io environment may have experienced errors when importing projects, monitoring projects and viewing issues in Snyk Open Source and Snyk Container. Services have since returned to normal. Recurring tests will retry automatically. Any imports or monitor runs that failed during this time should complete as normal when re-run.

Resolved

Snyk·Snyk Apps - Degraded Functionality for App Management

Snyk App management functions had degraded functionality. Existing Snyk Apps continued to work. Snyk reports that the incident is resolved. It lasted about 2 hours and 43 minutes.

Resolved

Snyk·Snyk Services Degraded

Snyk Code, Snyk Container, and Snyk Open Source are degraded in the SNYK-US-01 (app.snyk.io) environment. Snyk reports that the incident is resolved. The outage lasted 19 minutes.

Resolved

Snyk·Intermittent failures for Go-based projects

Snyk Open Source and SNYK-US-01 (app.snyk.io) had intermittent failures for Go-based projects on all flows except the CLI flow. Snyk reports that this incident is resolved. It lasted 14 hours and 16 minutes.

Resolved

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.live/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.live/feed.xml?providers=snyk
Slack
/feed subscribe https://outages.live/feed.xml?providers=snyk

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane