Minor impactResolvedDevOps

Snyk incident: Snyk PR Degradation

Snyk reported this minor-impact incident on its official status page on May 18, 2026, 11:19 UTC. It was resolved after 1h 34m.

Right now Snyk is degraded. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
May 18, 2026, 11:19 UTC
started
May 18, 2026, 12:53 UTC
resolved
1h 34m
duration
Minor
impact

Affected components

  • Snyk Code
  • Snyk Open Source
  1. resolvedMay 18, 2026, 12:53 UTC

    Following our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution details, please follow: <a href="https://status.snyk.io/incidents/h8w8rtczn430">Service Degradation on US-01 (app.snyk.io)</a>.

  2. investigatingMay 18, 2026, 11:19 UTC

    We're currently investigating intermittent degradation affecting PR events. This is affecting GitHub, GitLab, Bitbucket Cloud and Bitbucket Server integrations. The Snyk Incident Response has been invoked.

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 18, 2026: Snyk PR Degradation · APIStatus.watch