- Level
- confirmed
- Worst impact
- Degraded
- Components
- 📦 Release Management
- Down Index
- 24of 100
What to do
Check whether you use Bitrise 📦 Release Management. 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 5d 17h it lasted.
Anything that failed between 2026-05-28 15:00 UTC and 2026-06-03 08:52 UTC may need a replay.Subscribe to Bitrise's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=bitrise works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bitrise 3
- investigating
We are currently investigating an issue affecting artifact uploads in Release Management Store Releases. Most uploads are failing because valid requests to the Google Play AndroidPublisher API are incorrectly being marked as expired.
provider
- investigating
We are continuing to investigate this issue.
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-71718c1559
Is Bitrise still down?
No, this incident was resolved 2026-06-03 08:52 UTC. For Bitrise's live state, see https://down.guide/bitrise.
How long did it last?
5d 17h, from 2026-05-28 15:00 UTC to 2026-06-03 08:52 UTC, by the times Bitrise posted.
What was affected?
Bitrise named 📦 Release Management.
What caused it?
Bitrise hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bitrise's official status page, https://status.bitrise.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.