Major impactOngoingDevOps

Snyk outage: BitBucket Cloud Integrations Degraded

Snyk reported this major-impact incident on its official status page on Oct 29, 2026, 10:44 UTC. It has not been marked resolved yet.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Oct 29, 2026, 10:44 UTC
started
—
resolved
ongoing
duration
Major
impact

Affected components

  • Snyk API & Web
  • Snyk Code
  • Snyk Container
  • Snyk IaC
  • Snyk Open Source
  • Snyk Secrets
  1. monitoringOct 29, 2026, 12:25 UTC

    Our Engineers have implemented a fix, and we're observing improvements in success rates. We are now monitoring to ensure services remain stable.

  2. investigatingOct 29, 2026, 10:44 UTC

    We are investigating degradation affecting Bitbucket Cloud integrations across all Snyk environments. Customers may observe that their Bitbucket Cloud integrations are showing the error 'could not connect'. This will affect all Bitbucket Cloud actions, such as PR Checks, Importing and Recurring Tests, among others. The Snyk Incident Response has been invoked.

What APIStatus.watch saw

  • Oct 29, 2026, 10:49 UTCoperational → degraded
  • Oct 29, 2026, 12:29 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 25 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 15h 6m. See Snyk's uptime and incident history