Skip to content
OutageDeck

Incident detail

Security Incident

Active incidentCritical3 affected services

Timeline window

Started

Get alerted the next time Bitrise breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Bitrise alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

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

  2. Investigating

    <b>We are continuing to investigate the security incident causing Bitrise to be unavailable.</b>

    <b>Services:</b>

    All Services

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

  3. Investigating

    <b>We are continuing to investigate the security incident causing Bitrise to be unavailable.</b>

    <b>Services:</b>

    All Services

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

  4. Investigating

    <b>We are continuing to investigate the security incident causing Bitrise to be unavailable.

    If you need to reach out to us please e-mail us at support@bitrise.io</b>

    <b>Services:</b>

    All Services

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

  5. Investigating

    <b>What happened?</b>

    On November 13, 2026 at 11:32 EST (16:32 UTC), we detected suspicious activity in one of our internal cloud environments. Our initial investigation confirmed unauthorized access to an internal system. This system does not store or process customer data.

    Following our incident response procedures, we immediately took all of our services offline as a precaution while we investigated.

    At this stage, we have found no evidence that customer data, secrets, or source code were exposed. We are working all hands on the deck to determine the full scope and to restore our services as soon as possible.

    <b>What we recommend</b>

    As a precaution, once our services are restored, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.

    <b>What’s next</b>

    Our teams are working on completing the investigation and to restore all services safely.

    We understand the impact this has on your work and appreciate your patience.

    <b>Services:</b>

    All Services

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

  6. Investigating

    <b></b>

    After ongoing investigations we have still found no evidence that customer data, secrets, or source code were exposed. We are now beginning to restore services in a controlled, phased manner. We do not yet have an estimated time for full restoration.

    <b>What we recommend</b>

    As a precaution, once our services are restored, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.

    <b>Services:</b>

    All Services

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

  7. Investigating

    <b></b>

    We are making progress restoring the service, we expect the logins to app.bitrise.io to be restored by 01:00 EST (06:00 UTC), we are still working on a timeline for full restoration.

    <b>What we recommend</b>

    As a precaution, once you are able to sign in, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.

    <b>Services:</b>

    All Services

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

  8. Investigating

    <b></b>

    We are still making progress restoring the service, we expect the logins to app.bitrise.io to be restored soon, we are still working on a timeline for full restoration.

    <b>What we recommend</b>

    As a precaution, once you are able to sign in, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.

    <b>Services:</b>

    All Services

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

Keep exploring

More from Bitrise

Neighboring incidents on Bitrise's timeline and the rest of their record on OutageDeck.

← Older incident

Builds failing while downloading tools from GitHub

All Bitrise incidentsBitrise live status