Bitrise outage, 13 November 2026
Security Incident
- Started
- Status
- Ongoing: Investigating
- Impact
- Critical
- Affected
- ⚙️ Builds (CI), Key Value Dependency Cache Service, 📊 Insights, Build Cache, 📦 Release Management, Bazel Remote Execution, 📲 CodePush, 👥 Account Management
Is this still happening?
Yes. Bitrise still lists it as investigating; last update 13 Nov 2026, 20:44 UTC.
Right now: Bitrise reports a major outage. (as of 13 Nov, 20:59 UTC) Live Bitrise status
At a glance
- Bitrise rated this a critical incident (major outage).
- Half of the 27 resolved Bitrise incidents we recorded were fixed within 1 h 56 min.
- Bitrise had 4 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 8 Nov 2026.
Our summary from the Bitrise incidents we have recorded since 29 Apr 2026 - how we count.
Last update from Bitrise
<b>We are responding to a security incident affecting some of Bitrise’s internal secrets, detected within the last hour. As a precaution we have temporarily taken Bitrise offline. We have no confirmation that any customer data or source code was accessed and are investigating urgently. Out of an abundance of caution, we recommend rotating any Git and source-code access credentials connected to Bitrise. We will share updates as soon as we know more.</b> <b>Scope:</b> All Users <b>Severity:</b> SEV 1 <b>When will the next update be available?</b> You can expect a status update approximately <b>1 hour<b> from now.
Similar Bitrise incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h 56 min
-
, resolved after 44 min
-
, resolved after 1 h 17 min
-
, resolved after 31 min
Long waiting times (queue) on buildsPostmortem
-
, resolved after 2 h 18 min
Other recent Bitrise incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.