- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Git via SSH, Git via HTTPS
- Down Index
- 42of 100
What to do
Check whether you use Bitbucket Git via SSH, Git via HTTPS. 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 1h 6m it lasted.
Anything that failed between 2025-08-01 08:16 UTC and 2025-08-01 09:22 UTC may need a replay.Subscribe to Bitbucket's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=bitbucket works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bitbucket 2
- investigating
We are investigating reports of intermittent errors for some Atlassian Bitbucket Cloud customers. We will provide more details once we identify the root cause.
provider
- resolved
Between 08:00UTC to 09:00UTC, we experienced degraded performance with push and clone operations for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.
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-2aa52a25fb
Is Bitbucket still down?
No, this incident was resolved 2025-08-01 09:22 UTC. For Bitbucket's live state, see https://down.guide/bitbucket.
How long did it last?
1h 6m, from 2025-08-01 08:16 UTC to 2025-08-01 09:22 UTC, by the times Bitbucket posted.
What was affected?
Bitbucket named Git via SSH, Git via HTTPS.
What caused it?
Bitbucket hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bitbucket's official status page, https://bitbucket.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.