- Level
- confirmed
- Worst impact
- Degraded
- Components
- Pipelines
- Down Index
- 30of 100
What to do
Check whether you use Bitbucket Pipelines. 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 50m it lasted.
Anything that failed between 2025-03-20 06:11 UTC and 2025-03-20 07:01 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 aware of an issue where users are receiving an error message when running a build. Although we believe builds are still running successfully our team is investigating with urgency and an update will be provided when available.
provider
- resolved
The issue where users running builds would receive an error message should now be resolved. This issue was impacting only those using self-hosted runners. It is expected that builds should have still run as expected despite this error message in the meantime.
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-9b10bfe43a
Is Bitbucket still down?
No, this incident was resolved 2025-03-20 07:01 UTC. For Bitbucket's live state, see https://down.guide/bitbucket.
How long did it last?
50m, from 2025-03-20 06:11 UTC to 2025-03-20 07:01 UTC, by the times Bitbucket posted.
What was affected?
Bitbucket named Pipelines.
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.