Bitrise outage, 14 July 2026

Slow or hanging builds during clone and dependency resolution

Started
Resolved
15 Jul 2026, 18:10 UTC (after 26 h 35 min)
Impact
Minor
Affected
⚙️ Builds (CI), GitHub Git Operations

Last update from Bitrise

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...

15 Jul 2026, 18:10 UTC

Read the full incident on the official Bitrise status page

Is Bitrise down now?

This page is the record of one past incident. For the live status, see Is Bitrise down right now? - it reads the official status page every 2 minutes.

Other Bitrise incidents

  1. Issue with the Start Build dialog in the Website UI

  2. Long waiting times [on specific stacks / to start builds]

  3. Key Value Dependency Cache Service

  4. CI build list is not loading in multiple workspaces

  5. Increased queues on Linux machines

  6. Public VNC access is temporarily disabled on remote access builds and RDE sessions

  7. Elevated error rates on Bitrise Website

  8. Website high error rate due to database migration issue

All recorded Bitrise incidents