Live / Bitrise / Incident
Bitrise: Security Incident
Bitrise · bitrise.ioCritical outagemonitoring2026-11-16 01:03 UTC
Public — what happened
Summary
Bitrise said it is dealing with a critical security incident that involves some of its internal secrets, first spotted shortly before 20:44 UTC on 2026-11-13. As a precaution the company took its service offline, which it says affects all users and all services. Bitrise said it has no confirmation that customer data or source code was accessed, and it suggested customers change any Git and source-code access credentials linked to Bitrise. As of its latest update at 23:01 UTC the investigation was still going and the incident was not resolved.
Affected
⚙️ Builds (CI), Key Value Dependency Cache Service, 📊 Insights, Build Cache, 📦 Release Management, Bazel Remote Execution, 📲 CodePush, 👥 Account Management
Timeline
- Started — 2026-11-13 20:44 UTC
- Investigating — 2026-11-13 20:44 UTC (41 updates)
- Monitoring — 2026-11-15 23:18 UTC (3 updates)
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Bitrise against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Bitrise: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Bitrise report →
More from Bitrise
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.