Bitrise had 45 outages in the last 2 years totaling 1074h 10m of downtime — averaging 1.8 incidents per month.
There were 45 Bitrise outages since October 2, 2025 totaling 1074h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been resolved.
We are experiencing increased build queues on our Linux machines, we are currently investigating the issue.
This incident has been resolved.
A macOS Screen Sharing (VNC) vulnerability, CVE-2026-43760, is currently being exploited. 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 vulnerability. This is a proactive measure to reduce exposure. You can connect to the VNC server by tunnelling it over SSH: ssh -L 5900:localhost:5900 $SSH_ADDRESS Then connect to `localhost:5900` with a VNC client.
This incident has been resolved.
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.
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.
Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.
This incident has been resolved.
We experienced a brief period of high error rates on our website. The issue was caused by a database migration timing issue and was resolved after a rollback.
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 provide a further update as soon as more information is available.
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 resumed. We are continuing to monitor stability as we investigate the underlying root cause. We will provide a further update as soon as more information is available.
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 changes across all our data centers to address the underlying cause and prevent recurrence. We apologize for the disruption it caused.
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 information is available.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
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 to attempt the clone operation again.
We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.
This incident has been resolved.
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. Scope: [All users] Severity: [SEV-1] What we’re doing? Our Engineering teams are actively investigating this incident, monitoring alerts, and tracing requests to identify the root cause. We’re checking recent deploys, logs, CDN, DNS health, and server availability. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
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 needed.
This incident has been resolved.
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 server availability. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
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 update be available? You can expect a status update approximately 1 hour from now.
This incident has been resolved.
A subset of Bitrise builds are experiencing intermittent DNS failures. Scope: [A subset of users] Severity: [SEV-2] 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, and server availability. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing a delay in starting builds on Linux machines, we are investigating the issue.
This incident has been resolved.
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 soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
This incident has been resolved.
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.
This incident has been resolved.
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.
We improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.
We have observed some malformed data appearing in build logs, we have quickly issues a fix and this has been resolved.
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 worker is allocated. Scope: Builds on M4 Pro Stacks Severity: SEV-2 What we’re doing? Our Engineering teams are actively investigating causes, reviewing worker pool utilization, autoscaling events, recent deploys, and any upstream provider issues. We are analyzing metrics and logs to identify bottlenecks like unusually high build volume, throttling from third-party providers, etc. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
This incident has been resolved.
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 investigating root cause. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 15 minutes from now.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are continuing to investigate this issue.
This incident has been resolved.
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 we’re doing Our Engineering teams released a fix to mitigate this incident and are now actively monitoring our systems. When will the next update be available? You can expect a status update approximately 1 hour from now.
This incident has been resolved.
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 and team members, billing and payments. Scope: A subset of users Severity: SEV-2 What we’re doing? Our Engineering teams are actively investigating this incident, monitoring alerts, and tracing requests to identify the root cause. We’re checking recent deploys, logs, CDN, DNS health, and server availability. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.
The issue has been identified and a fix is being implemented.
This incident has been resolved.