Minor impactResolvedDevOps

Snyk incident: Reporting PDF Degraded

Snyk reported this minor-impact incident on its official status page on May 13, 2026, 14:49 UTC. It was resolved after 4h 13m.

Right now Snyk is degraded. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
May 13, 2026, 14:49 UTC
started
May 13, 2026, 19:01 UTC
resolved
4h 13m
duration
Minor
impact

Affected components

  • Snyk AppRisk
  • Snyk Code
  • Snyk Container
  • Snyk IaC
  • Snyk Open Source
  1. resolvedMay 13, 2026, 19:01 UTC

    Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.

  2. investigatingMay 13, 2026, 14:49 UTC

    Snyk engineers are investigating degraded performance with the Reporting PDF in the Snyk-US-01 multi-tenant environment. Customers may observe longer generation times or failures to generate reports.

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

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

Snyk incident on May 13, 2026: Reporting PDF Degraded · APIStatus.watch