Is Bitrise down?

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 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 mirrors) to cover a larger subset of artifacts to proxy Services impacted: Android builds Severity: SEV-2 When will the next update be available? You can expect a status update approximately 1 hour from now.

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 update be available? You can expect a status update approximately 1 hour from now.

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 builds as the mirrors are deployed inside the datacenters, so one URL in a build won't work in another. We strongly suggest that customers to not cache anything in ~/.gradle/init.d/, and if you do, clear these contents / re-add our steps that activate the mirror. When will the next update be available? You can expect a status update approximately 1 hour from now.

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 are working on a fix. We identified a gap in the mirroring logic for Roboelectric tests, exploring our options to help mitigate the issue. We are seeing larger latencies from Maven Central upstream, which we are investigating. When will the next update be available? You can expect a status update approximately 1 hour from now.

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 be available? You can expect a status update approximately 1 hour from now.

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 how to avoid a similar outage in the future. Thank you for your patience and understanding. If you encounter any issues, please reach out to our Support team: https://support.bitrise.io/en/

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 doing? We are actively making adjustments to help resolve issues with the failing builds When will the next update be available? You can expect a status update approximately 1 hour from now.

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 builds Scope: [All users / a subset of users] Severity: SEV-2 What we’re doing Our Engineering teams released a fix to mitigate this incident and now actively monitoring our systems. When will the next update be available? You can expect a status update approximately 1 hour from now.

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. When will the next update be available? You can expect a status update approximately 2 hours from now.

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 systems. When will the next update be available? You can expect a status update approximately 2 hours from now.

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 is working as intended, and the vast majority of dependency downloads over the previous 1.5 days have been served by Bitrise. There was, however, a subset of Bitrise CI jobs that were in the long tail and still experiencing 429 errors, even when following our recommended steps for using the mirror. Over the past several hours, we have evenly distributed traffic flow and have addressed the edge cases in customer Gradle configurations that bypassed the mirror. If you are still experiencing 429 rate-limiting errors when installing dependencies, and you have already followed the recommended steps for using the mirror, please reach out to us at [email protected].