Skip to main content
Snyk

BitBucket Cloud Integrations Degraded

Partial outage Lasted 3h 32m · started · Snyk's page

Level
confirmed
Worst impact
Partial outage
Components
Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk API & Web, Snyk Secrets
Down Index
39of 100

What to do

  • Check whether you use Snyk Snyk Code, Snyk Code, Snyk Code, Snyk Code and 14 more. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 32m it lasted.

    Anything that failed between 2026-10-29 10:44 UTC and 2026-10-29 14:16 UTC may need a replay.
  • Subscribe to Snyk's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 3

  1. investigating

    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.

    provider

  2. monitoring

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

    provider

  3. resolved

    Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-eb58e97796

Is Snyk still down?

No, this incident was resolved 2026-10-29 14:16 UTC. For Snyk's live state, see https://down.guide/snyk.

How long did it last?

3h 32m, from 2026-10-29 10:44 UTC to 2026-10-29 14:16 UTC, by the times Snyk posted.

What was affected?

Snyk named Snyk Code, Snyk Code, Snyk Code, Snyk Code and 14 more.

What caused it?

Snyk hasn't published a root cause. If it does, it shows here.

Where does this come from?

Snyk's official status page, https://status.snyk.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.