Snyk incident

Snyk Go Scans Degraded

Minor Resolved View vendor source →
Started
Mar 17, 2026, 10:54 AM UTC
Resolved
Mar 17, 2026, 02:16 PM UTC
Duration
3h 21m
Detected by Pingoru
Mar 17, 2026, 10:54 AM UTC

Affected components

Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source

Update timeline

  1. investigating Mar 17, 2026, 10:54 AM UTC

    Our engineers are currently investigating a degradation affecting customers who have opted in to Full Source Code Analysis. A small subset of affected customers may observe issues with importing, PR Checks, manual tests, and recurring tests for their Go projects. The Snyk Incident Response has been invoked, and our investigations are underway.

  2. monitoring Mar 17, 2026, 12:00 PM UTC

    We have implemented a fix, and initial signs suggest this has been successful. We will continue to monitor to ensure services have fully recovered.

  3. monitoring Mar 17, 2026, 02:15 PM UTC

    No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.

  4. resolved Mar 17, 2026, 02:16 PM UTC

    No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.

Looking to track Snyk downtime and outages?

Pingoru polls Snyk's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Snyk reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Snyk alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Snyk for free

5 free monitors · No credit card required