- Level
- confirmed
- Worst impact
- Degraded
- Components
- ⚙️ Builds (CI), GitHub Git Operations
- Down Index
- 24of 100
What to do
Check whether you use Bitrise ⚙️ Builds (CI), GitHub Git Operations. 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 1d 2h it lasted.
Anything that failed between 2026-07-14 15:35 UTC and 2026-07-15 18:10 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 4
- investigating
We are currently investigating reports of slow or hanging builds. Affected builds may stall or take significantly longer than usual during early phases such as cloning repositories or resolving Swift Package Manager dependencies. We will provide a further update as soon as more information is available.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
This incident has been resolved. Some builds may still experience slower clone operations from GitHub due to performance degradation affecting Git operations in some of our datacenters. As a workaround, use Bitrise key-based caching for SPM dependencies so builds do not re-resolve them over the slow path. Add Restore SPM Cache (restore-spm-cache@3) before your dependency-resolution/build step and Save SPM Cache (save-spm-cache@1) after your dependency resolution and build steps — no extra configuration needed. Please note that Bitrise does not cache your source code; your repository must still be cloned to fetch the latest changes. If a build fails or hangs during code fetch, retry the build to attempt the clone operation again.
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-e6c69cd160
Is Bitrise still down?
No, this incident was resolved 2026-07-15 18:10 UTC. For Bitrise's live state, see https://down.guide/bitrise.
How long did it last?
1d 2h, from 2026-07-14 15:35 UTC to 2026-07-15 18:10 UTC, by the times Bitrise posted.
What was affected?
Bitrise named ⚙️ Builds (CI), GitHub Git Operations.
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.