- Level
- confirmed
- Worst impact
- Degraded
- Components
- Git via SSH, Git via HTTPS
- Down Index
- 36of 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 7h 46m it lasted.
Anything that failed between 2025-08-20 07:30 UTC and 2025-08-20 15:16 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 3
- investigating
- Bitbucket Cloud is investigating an incident affecting Git clone reliability. - The team is investigating the root cause and will update as soon as possible.
provider
- monitoring
A root cause has been identified and a mitigation has been implemented; we're monitoring the situation.
provider
- resolved
This incident has been resolved.
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-19dd04900a
Is Bitbucket still down?
No, this incident was resolved 2025-08-20 15:16 UTC. For Bitbucket's live state, see https://down.guide/bitbucket.
How long did it last?
7h 46m, from 2025-08-20 07:30 UTC to 2025-08-20 15:16 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.