Snyk: Golang Scan Failures
Azure outage, Oct 29, 2025 · 23 vendors, 23 incidents
Snyk’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +1 min vs the first vendor naming Azure)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 4 blamed Azure<br/>Devin (Cognition), Smartsheet, Sigma Computing, Elastic Cloud"]:::blames
root --> h1
later["Later<br/>1 vendor, 1 blamed Azure<br/>Speechmatics"]:::blames
root --> later
me["Snyk (this incident)<br/>posted +1 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Snyk Engineers have deployed a fix. All services have returned to normal operations, and the Snyk incident response has been stood down.
From Snyk’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.snyk.io (opens in new tab).