# Elevated error rates for Android builds

- Provider: [Bitrise](https://down.guide/bitrise)
- Level: confirmed
- Impact: Degraded
- lasted 9h 48m
- started 2026-04-29 10:36 UTC
- ⚙️ Builds (CI)
- us
- id: DWN-545d1b9c40
- Official page: https://stspg.io/kqg9702zt297

## Updates from Bitrise
### 2026-04-29 10:36 UTC: identified
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.

### 2026-04-29 14:03 UTC: monitoring
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 an update 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.

### 2026-04-29 16:50 UTC: monitoring
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.

### 2026-04-29 19:15 UTC: monitoring
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.

### 2026-04-29 20:24 UTC: resolved
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 support@bitrise.io.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).