outages.live
Live
SnykIncident ·

Intermittent failures for Go-based projects

DegradedOfficial update
0

Go-based projects fail intermittently in Snyk Open Source and in SNYK-US-01 (app.snyk.io). All flows fail except the CLI flow. Snyk engineers are investigating the issue and the Snyk Incident response has been enacted.

State

Investigating

Started

Ongoing for

17 min

Worst impact

Degraded

Timeline

1 update
20:3420:3820:4320:4720:51
DegradedUpdate postedTimes in UTC

Investigating

17 min 100%

Updates

Times in UTC

As posted by Snyk

Investigating

Snyk engineers are investigating an issue with intermittent failures for Go-based projects for all flows except the CLI flow. The Snyk Incident response has been enacted.

Affected components

2
Snyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk Open Source

Snyk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

25

Days with an incident

39

Median duration

11 h 55 min

This incident

98% shorter than the median

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

5 days
median 11 h 55 min
90 days agoToday

Other Snyk incidents

All incidents

Snyk·Issue Resolving Entitlements

Snyk reported failures resolving entitlements. The issue affected Snyk Code, Snyk Container, Snyk IaC, and Snyk Open Source in the SNYK-US-02, SNYK-EU-01, and SNYK-AU-01 regions. Snyk has resolved the issue. It lasted about 17 hours and 45 minutes.

Resolved

Snyk·BitBucket Cloud Integrations Degraded

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.

Resolved

Snyk·Snyk Test Down in SNYK-US-01

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

Resolved

Snyk·Snyk Support portal degradation

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

Resolved

Snyk·Snyk Container Degradation in SNYK-US-01

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.

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