Snyk reported this minor-impact incident on its official status page on Jun 16, 2026, 04:52 UTC. It was resolved after 6d 5h.
Right now Snyk is operational. Live Snyk status →
Both the Issues API data freshness and reporting data freshness have been fully restored and are operating normally. Our investigation is now complete, and the Snyk Incident Response has been stood down. We apologise for any inconvenience this may have caused and thank you for your patience throughout.
We are no longer observing delays affecting our reporting data freshness. However, the Issues API data freshness remains delayed, and our investigation into this is ongoing. We will provide a further update as soon as we have more information.
Snyk Engineering has identified a data freshness delay within Issues Reporting. Our teams are actively investigating the root cause, and we will provide further updates as the situation progresses.
Engineering have detected a delay in data affecting Issue API results on the app.snyk.io environment. Project data, UI based Reporting, and Export API are not affected. We are investigating and will report back here with any updates.
Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history