Changes / Snyk / Snyk Open Source .NET Tests Failing
Snyk: Major incident: Snyk Open Source .NET Tests Failing
Summary
Snyk reported a major incident affecting all Snyk Open Source .NET project workflows, including import, retest, and pull request checks, across AU, EU, GOV, US-01 and US-02 components. It started at 2026-08-04 13:07 UTC and was resolved at 2026-08-04 14:29 UTC, lasting 1 h 21 min; engineers deployed a fix and confirmed recovery.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Snyk Open Source .NET Tests Failing
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-04 13:07 UTC
Before: not present
After: 2026-08-04 14:29 UTC
Before: not present
After: SNYK-AU-01 (app.au.snyk.io) - Snyk Open Source, SNYK-EU-01 (app.eu.snyk.io) - Snyk Open Source, SNYK-GOV-01 (app.snykgov.io) - Snyk Open Source, Snyk Open Source, SNYK-US-01 (app.snyk.io) - Snyk Open Source, SNYK-US-02 (app.us.snyk.io) - Snyk Open Source
Before: not present
After: We've identified an issue affecting all .NET project workflows, including import, retest, and pull request checks.
The Snyk Incident Response has been invoked, and our engineering team are investigating.
Before: not present
After: Our engineering team have identified the root cause and are working on deploying a fix.
We will keep you updated on our progress.
Before: not present
After: Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered.
The Snyk Incident Response has been stood down.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Snyk Open Source .NET Tests Failing (this change) Snyk reported a major incident affecting all Snyk Open Source .NET project workflows, including import, retest, and pull request checks, across AU, EU, GOV, US-01 and US-02 components. It started at 2026-08-04 13:07 UTC and was resolved at 2026-08-04 14:29 UTC, lasting 1 h 21 min; engineers deployed a fix and confirmed recovery. | Major incident |