- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Bitrise. 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 12h 44m it lasted.
Anything that failed between 2026-06-26 19:40 UTC and 2026-06-27 08:25 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 2
- identified
The issue has been identified, and we are working on a fix. In the meantime, adding a previous version of bitrise-step-activate-gradle-remote-cache pinned to version 2.20.13 functions as a workaround.
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-ec62c8861d
Is Bitrise still down?
No, this incident was resolved 2026-06-27 08:25 UTC. For Bitrise's live state, see https://down.guide/bitrise.
How long did it last?
12h 44m, from 2026-06-26 19:40 UTC to 2026-06-27 08:25 UTC, by the times Bitrise posted.
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.