Bitrise

Affected: ⚙️ Builds (CI)

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 08:36 UTC

   Users may be unable to open or use the Start Build dialog in the UI. This does not impact the underlying build trigger functionality., we are investigating the issue.

2. identified 2026-10-05 08:36 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-05 08:46 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-05 10:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-22 16:15 UTC

   We are currently investigating elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up. Services: Build start times and queue wait times; build execution itself remains normal once a...

2. resolved 2026-09-22 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: Key Value Dependency Cache Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-05 12:52 UTC

   We identified that the Key Value Dependency Cache Service was down between 9:21 and 10:03 CET. Bitrise customers using Key-value-caching may have experienced slower-running builds. The issue is now resolved.

2. resolved 2026-09-05 14:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-28 13:01 UTC

   We are currently investigating this issue.

2. investigating 2026-08-28 13:04 UTC

   We are currently investigating an issue where the Builds List page is not loading for some workspaces. We will provide an update as soon as we have more information.

3. resolved 2026-08-28 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 13:02 UTC

   We are experiencing increased build queues on our Linux machines, we are currently investigating the issue.

2. resolved 2026-08-07 14:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-30 15:40 UTC

   A macOS Screen Sharing (VNC) vulnerability, CVE-2026-43760, has been announced. To protect your machines, we’ve disabled internet-facing access to VNC. SSH is unaffected and remains fully available. We have no evidence that any customer machine was accessed as a result of this...

2. resolved 2026-08-31 13:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: GitHub API Requests

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-16 23:04 UTC

   We are currently investigating reports of an elevated error rate on the Bitrise website. We will provide a further update as soon as more information is available.

2. identified 2026-07-16 23:24 UTC

   We're experiencing elevated error rates across the Bitrise website. This is caused by an ongoing GitHub incident that is disrupting a critical part of our platform: https://www.githubstatus.com/incidents/gxycch3076xk We're actively working to restore service stability.

3. monitoring 2026-07-17 00:04 UTC

   Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.

4. resolved 2026-07-17 00:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-16 14:51 UTC

   We experienced a brief period of high error rates on our website. The issue was resolved after a rollback.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 16:40 UTC

   We are currently investigating a network outage affecting our ORD data center. Builds running in this data center may have failed or been delayed during the outage. Our team identified an issue with Proxmox storage in the affected data center and is working on a fix. We will...

2. monitoring 2026-07-14 18:18 UTC

   The network outage affecting our ORD data center has been mitigated. Builds running in this data center may have failed or been delayed during the outage window. Our team identified and addressed an issue with Proxmox storage in the affected data center, and job scheduling has...

3. resolved 2026-07-15 18:13 UTC

   This incident has been resolved. We experienced a network outage in our ORD data center caused by dropped packets between nodes, which led to failed health checks and a cluster-wide disruption. The outage was mitigated on July 14, and we've since applied network configuration...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI), GitHub Git Operations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-14 15:35 UTC

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

2. investigating 2026-07-14 15:36 UTC

   We are continuing to investigate this issue.

3. investigating 2026-07-14 16:30 UTC

   We are continuing to investigate this issue.

4. resolved 2026-07-15 18:10 UTC

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

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: Build Cache

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 09:08 UTC

   We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.

2. resolved 2026-07-13 10:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-10 17:49 UTC

   We are currently investigating elevated errors observed for the Bitrise Workflow Editor. Users may experience increased HTTP errors, intermittent page load failures, or timeouts when accessing the site. Services impacted: The Workflow Editor may return errors or fail to load....

2. monitoring 2026-07-10 18:37 UTC

   The issue has been identified. We've deployed a workaround, and the Workflow Editor is now loading normally for all customers. This issue was caused by the ongoing LaunchDarkly incident affecting flag delivery evaluations. We're continuing to monitor and will provide updates as...

3. resolved 2026-07-10 19:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-09 09:05 UTC

   We are currently investigating an incident causing elevated errors in Pipelines Services: Build Pipelines Scope: [All users] Severity: [SEV-1] What we’re doing? Our Engineering teams are actively investigating this issue. We’re checking recent deploys, logs, CDN, DNS health, and...

2. monitoring 2026-07-09 09:29 UTC

   We mitigated this incident and are currently monitoring our systems. Services: Build Pipelines Scope: [All users] Severity: [SEV-1] What we’re doing Our Engineering teams released a fix to mitigate this incident and are now actively monitoring our systems. When will the next...

3. resolved 2026-07-09 12:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-08 20:19 UTC

   A subset of Bitrise builds are experiencing intermittent DNS failures. Scope: [A subset of users] Severity: [SEV-1] What we’re doing? Our Engineering teams are actively investigating this incident to identify the root cause. We’re checking recent deploys, logs, CDN, DNS health,...

2. investigating 2026-07-08 20:21 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-08 21:01 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-08 21:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 13:54 UTC

   We are experiencing a delay in starting builds on Linux machines, we are investigating the issue.

2. resolved 2026-07-09 07:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-07 15:06 UTC

   In our IAD datacenter, we are experiencing networking connectivity issues. Services: [IAD datacenter] Scope: [some users] Severity: [SEV-2] What we’re doing? Our Engineering teams are working on immediate actions to remediate this issue. We will perform validated mitigations as...

2. resolved 2026-07-07 15:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-26 19:40 UTC

   The issue has been identified, and we are working on a fix. In the meantime, adding a previous version of bitrise-step-activate-gradle-remote-cache pinned to version 2.20.13 functions as a workaround.

2. resolved 2026-06-27 08:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-25 10:28 UTC

   We are seeing elevated error rates in Virtual Device Testing steps, resulting from the Google Cloud Tool Results API being intermittently unavailable. We are monitoring the situation.

2. resolved 2026-06-26 06:14 UTC

   We improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-23 09:00 UTC

   We have observed some malformed data appearing in build logs, we have quickly issues a fix and this has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 15:34 UTC

   We are currently investigating elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up. Services: Build start times and queue wait times; build execution itself remains normal once a...

2. resolved 2026-06-17 16:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 20:26 UTC

   Gradle builds in the ORD data center are experiencing failures with dependency resolution. Some users may experience build failures Services: Gradle Repository Manager Scope: All builds in the ORD data center Severity: SEV-2 What we’re doing? Our Engineering teams are actively...

2. monitoring 2026-06-11 20:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-11 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 16:50 UTC

   We are currently investigating an incident causing to be unavailable. Services: Data Center Connectivity Severity: SEV-1 What we’re doing? Our Engineering teams are actively investigating this issue. We’re checking recent deploys, logs, CDN, DNS health, and server availability....

2. monitoring 2026-06-11 16:50 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-11 18:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: 📦 Release Management

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-28 15:00 UTC

   We are currently investigating an issue affecting artifact uploads in Release Management Store Releases. Most uploads are failing because valid requests to the Google Play AndroidPublisher API are incorrectly being marked as expired.

2. investigating 2026-05-28 15:01 UTC

   We are continuing to investigate this issue.

3. resolved 2026-06-03 08:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-30 11:34 UTC

   We are tackling edge cases where the Maven Central mirror cannot be applied. We are working on a fix to make the Maven Central mirror compatible with dependency verification. We have released new versions of the affected steps (Install Android SDK components and Activate Gradle...

2. identified 2026-04-30 13:04 UTC

   We are seeing some timeouts when connecting to the Maven Central proxy in one of our datacenters and are investigating. Dependency verification support is still in progress. We are exploring options to auto-enable the Gradle mirrors for our Bitrise customers. When will the next...

3. identified 2026-04-30 14:01 UTC

   For customers having dependency verification enabled for their Android builds, you will need to update your configuration based on our updated guide . We have identified cases where customers have cached the init scripts performing the mirror redirection. This can break the...

4. identified 2026-04-30 15:32 UTC

   What we’re doing? We have rolled out a change so that all builds have the redirection enabled by default; there is no need to add the specific steps for this, except for dependency verification (which requires a specific step version pin). We identified upstream 401 errors and...

5. identified 2026-04-30 19:45 UTC

   We are continuing to fine-tune our mirror for reduced latency. Customers using our mirror are no longer experiencing rate limiting. We are continuing to monitor for edge cases and help customers migrate to using the mirror by using the following guide . When will the next update...

6. resolved 2026-05-01 21:50 UTC

   This incident is now resolved, and impacted services are now operating. Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-04-29 10:36 UTC

   We are still seeing some Android build failures. We are creating a dedicated step just for enabling the proxy, so customers won't need to add the "install missing Android SDK components" step Services impacted: Android builds Scope: A subset of users Severity: SEV-2 What we’re...

2. monitoring 2026-04-29 14:03 UTC

   We have released the step "activate-gradle-mirrors" so that our customers can enable the proxy without having to add the "install Android missing SDK components" step to their workflows. Please reach out to the Bitrise support team if you have any questions Services: Android...

3. monitoring 2026-04-29 16:50 UTC

   We have taken additional measures and are observing decreasing instances of rate limiting Services: Android Builds Scope: A subset of users Severity: SEV-2 What we’re doing: Our Engineering teams released a fix to mitigate this incident and are actively monitoring our systems....

4. monitoring 2026-04-29 19:15 UTC

   We are still taking additional measures and are observing decreasing instances of rate limiting Services: Android Builds Scope: A subset of users Severity: SEV-2 What we’re doing: Our Engineering teams released an update to mitigate this incident and are actively monitoring our...

5. resolved 2026-04-29 20:24 UTC

   On April 28, 2026, rate limiting by Maven Central began causing 429 errors for Bitrise-hosted CI jobs attempting to download dependencies. We responded by enabling a proxy layer to mirror Maven packages within Bitrise in order to reduce load on Maven Central. The proxy service...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 13:38 UTC

   We are currently investigating elevated errors for Android builds. Services impacted: Android builds are failing due to MavenCentral request throttling Scope: A subset of users Severity: SEV-2 What we’re doing? Our Engineering teams are actively investigating this incident,...

2. identified 2026-04-28 16:38 UTC

   We are working on redirections to mitigate the current issue. Services: Android Builds Scope: A subset of users Severity: SEV-2 What we’re doing? Our Engineering teams identified the root cause and are now actively working on mitigations to restore stability across all affected...

3. monitoring 2026-04-28 17:25 UTC

   We mitigated this incident and are currently monitoring our systems to resolve Services: Android Builds Scope: A subset of users Severity: SEV-1 What we’re doing Our Engineering teams released a fix to mitigate this incident. We expect new builds to start, and we continue to...

4. monitoring 2026-04-28 18:01 UTC

   We're seeing build failures for customers who do not have the "Install missing Android SDK components" step added. We strongly suggest adding this step for mitigation to your workflow. https://bitrise.io/integrations/steps/install-missing-android-tools Services: Builds Scope: A...

5. monitoring 2026-04-28 18:52 UTC

   We have identified an issue with plugins on the Gradle plugin portal not being found in the Install missing Android SDK components step. We're releasing a fix

6. monitoring 2026-04-28 19:29 UTC

   we have released a fix for the Gradle plugin portal not being found in the "Install missing Android SDK components" step, and will continue monitoring Services: Android builds Scope: A subset of users Severity: SEV-2 What we’re doing We are actively monitoring our systems. When...

7. resolved 2026-04-28 22:14 UTC

   This incident is now resolved and impacted services are now operating without issues. Our teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-28 12:29 UTC

   We mitigated this incident and are currently monitoring our systems to resolve HTTP errors, intermittent page load failures, or timeouts when accessing the site. Services: Build details pages on app.bitrise.io are failing to load. Scope: Subset of users Severity: SEV-1 What...

2. resolved 2026-04-28 17:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: 👥 Account Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 16:37 UTC

   We are currently investigating a service disruption affecting account, team, and billing features on the Bitrise website. Users may observe their credits/build not being refreshed at the start of their billing cycle. Services: Features related to managing account details, teams...

2. identified 2026-04-20 16:37 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-04-20 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 20:23 UTC

   We are currently investigating elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up. Services: Build start times and queue wait times; build execution itself remains normal once a...

2. identified 2026-04-15 20:43 UTC

   We identified the root cause of elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up. Services: Build start times and queue wait times; build execution itself remains normal once...

3. resolved 2026-04-15 20:54 UTC

   This incident is now resolved, and impacted services are now operating without issues. Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-19 16:52 UTC

   We are currently investigating this issue.

2. identified 2026-03-19 18:37 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-19 22:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-09 12:21 UTC

   We have noticed build related issues with our web UI, starting new builds, incoming webhooks, and accessing build artifacts of running builds. We are currently investigating.

2. identified 2026-03-09 12:27 UTC

   We managed to attribute the high error rate to an incident affecting Google Kubernetes Engine.

3. monitoring 2026-03-09 12:31 UTC

   Google has applied a workaround, and error rates are decreasing. Operations are returning to normal.

4. resolved 2026-03-09 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-05 11:43 UTC

   We are currently investigating this issue.

2. identified 2026-03-05 12:03 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-03-05 12:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-03-05 12:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-02 15:59 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-03-02 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 13:27 UTC

   We have noticed increased build queues on all stacks, both on Linux and macOS. We are investigating the issue.

2. identified 2026-03-02 13:48 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-02 15:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 11:37 UTC

   We have noticed an increased error rate when triggering builds, we are investigating the issue.

2. resolved 2026-03-02 11:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-11 14:59 UTC

   We are currently investigating an incident causing the Pipelines API endpoint to be unavailable Services: Bitrise API Scope: some users Severity: SEV-2 What we’re doing? Our Engineering teams are actively investigating this issue. We’re checking recent deploys, logs, CDN, DNS...

2. identified 2026-02-11 16:05 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-02-11 17:11 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-02-11 17:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. resolved 2025-12-05 09:00 UTC

   We observed high error rates affecting our static site (bitrise.io) due to Cloudflare’s incident between 8:56 - 9:12 UTC app.bitrise.io was unaffected

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-03 10:18 UTC

   We are currently investigating an incident that is causing issues with passing values to environment variables. The team is working on a fix. Services: Environment Variables Scope: All users Severity: SEV-2 What we’re doing? Our Engineering teams are actively investigating this...

2. resolved 2025-12-03 10:59 UTC

   This incident is now resolved and impacted services are now operating without issues. Our teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what...

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-26 16:09 UTC

   We are currently investigating an incident causing Android builds to hang/fail. Services: Android builds seem to be affected on macOS only. Scope: Some users might experience issues. Severity: SEV-1 What we’re doing? Our Engineering teams are actively investigating this issue....

2. identified 2025-11-26 19:01 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-11-27 13:18 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-27 14:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-25 16:55 UTC

   We are currently investigating slower response times on the Bitrise website at app.bitrise.io. Users may experience increased HTTP errors, intermittent page load failures, or timeouts when accessing the site. Services impacted: Website pages on app.bitrise.io, including sign-up...

2. resolved 2025-11-25 17:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 17:20 UTC

   We identified the root cause of elevated build queues on M4 Pro. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up due to the Cloudflare outage experienced earlier today, which has resulted in a larger number...

2. identified 2025-11-18 18:18 UTC

   We’re continuing to address the elevated build queue times, but wait times have now dropped to approximately 6-7 minutes across most queues. Our engineering team is monitoring the queues closely and is working on full remediation. We’ll keep you posted with further updates....

3. resolved 2025-11-18 20:38 UTC

   Wait times have now dropped to approximately 30 seconds across most queues. This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 11:53 UTC

   We are currently investigating the web application being unavailable

2. identified 2025-11-18 11:58 UTC

   We are aware that the web app error is due to a current Cloudflare Global Network outage

3. monitoring 2025-11-18 15:17 UTC

   We have stopped routing traffic through Cloudflare, and most of our services are now functioning normally. Our team is monitoring performance and completing final checks.

4. monitoring 2025-11-18 20:35 UTC

   We are no longer observing errors in increased latency related to the Cloudflare outage. We have re-enabled our Cloudflare services that were temporarily disabled.

5. resolved 2025-11-18 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-10 11:10 UTC

   We mitigated this incident and are currently monitoring our systems to resolve the elevated build queue times on Mac stacks. Services: Build start times and Mac stack queue wait times Scope: Builds on Mac stacks Severity: SEV-1 What we’re doing Our Engineering teams released a...

2. resolved 2025-11-10 11:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-30 16:18 UTC

   We are currently investigating elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up. What’s happening? Services: Build start times and queue wait times; build execution itself...

2. resolved 2025-10-30 17:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: ⚙️ Builds (CI)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-28 16:21 UTC

   We are currently experiencing capacity issues on M4 Pro machines. Launching builds might be delayed.

2. resolved 2025-10-28 19:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: GitHub Git Operations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-24 09:48 UTC

   Github is currently experiencing issues, which could also affect Bitrise builds using Github ssh: https://www.githubstatus.com/incidents/n7hf73qtpz2l

2. resolved 2025-10-24 12:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: Bitrise Support Center

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 16:27 UTC

   Our customer communication platform, Intercom, is currently experiencing disruptions due to a widespread AWS outage affecting multiple services globally. As a result, some users may encounter issues reaching our Support team through the in-app chat (Messenger). We are closely...

2. identified 2025-10-20 17:04 UTC

   While Intercom is unavailable, if you have a pressing or time-sensitive issue, please reach out to us at support@bitrise.io so we can assist you as quickly as possible. For non-urgent inquiries, we kindly ask that you wait until Intercom services are restored and contact us via...

3. resolved 2025-10-20 23:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 10:10 UTC

   Due to an AWS outage, our 4rd party billing service provider is down. Biling and subscription management is not available. Builds are running without issues.

2. resolved 2025-10-20 14:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-14 16:52 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2025-10-14 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.

Affected: Build Cache

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-02 12:31 UTC

   Bitrise users may experience a loading issue with the Build Cache webpage. We are investigating the cause of the issue. The Build Cache functionality itself is not affected

2. resolved 2025-10-02 12:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitrise's status page.