Bitrise Status

Update - 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.
Apr 30, 2026 - 19:45 UTC

Update - 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.
Apr 30, 2026 - 15:32 UTC

Update - 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.
Apr 30, 2026 - 14:01 UTC

Update - 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.
Apr 30, 2026 - 13:04 UTC

Identified - 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.
Apr 30, 2026 - 11:34 UTC

×
Subscribe to Incident

Subscribe to updates for Elevated error rate with Android builds via email and/or text message. You'll receive email notifications when incidents are updated, and text message notifications whenever Bitrise creates or resolves an incident.

VIA EMAIL:

VIA SMS:

Enter mobile number

Edit number Send OTP

Enter the OTP sent
Resend OTP in 30 seconds

To receive SMS updates, please verify your number. To proceed with just email click ‘Subscribe’

Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Uptime over the past 90 days. View historical uptime.

⚙️ Builds (CI) Degraded Performance

90 days ago

100.0 % uptime

Today

📊 Insights Operational

90 days ago

100.0 % uptime

Today

📦 Release Management Operational

90 days ago

100.0 % uptime

Today

👥 Account Management Operational

90 days ago

100.0 % uptime

Today

🥫 Cache Operational

90 days ago

100.0 % uptime

Today

Key Value Dependency Cache Service Operational

90 days ago

100.0 % uptime

Today

Build Cache Operational

90 days ago

100.0 % uptime

Today

Bazel Remote Execution Operational

90 days ago

100.0 % uptime

Today

🛟 Bitrise Support Operational

90 days ago

100.0 % uptime

Today

Bitrise Community Operational

90 days ago

100.0 % uptime

Today

Bitrise Support Center Operational

90 days ago

100.0 % uptime

Today

🤝 3rd Party Integrations Operational

DigitalOcean Operational

DNSimple Name Servers Operational

Atlassian Bitbucket API Operational

Atlassian Bitbucket Git via HTTPS Operational

Atlassian Bitbucket SSH Operational

Atlassian Bitbucket Webhooks Operational

Atlassian Bitbucket Website Operational

AWS s3-us-standard Operational

AWS s3-us-west-1 Operational

AWS s3-us-west-2 Operational

Bintray REST API Operational

Cocoapods Operational

GitHub API Requests Operational

GitHub Gists Operational

GitHub Notifications Operational

GitHub Git Operations Operational

GitHub Webhooks Operational

GitHub Pull Requests Operational

GitHub Actions Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Major outage

Partial outage

No downtime recorded on this day.

No data exists for this day.

had a major outage.

had a partial outage.

Related

No incidents or maintenance related to this downtime.

Past Incidents

May 1, 2026

No incidents reported today.

Apr 30, 2026

Unresolved incident: Elevated error rate with Android builds.

Apr 29, 2026

Elevated error rates for Android builds

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.
Apr 29, 20:24 UTC

Update - 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.
Apr 29, 19:15 UTC

Update - 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.
Apr 29, 16:50 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.
Apr 29, 14:03 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.
Apr 29, 10:36 UTC

Apr 28, 2026

Elevated error rates for Android builds

Resolved - 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 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/
Apr 28, 22:14 UTC

Update - 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 will the next update be available?

You can expect a status update approximately 1 hour from now.
Apr 28, 19:29 UTC

Update - 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
Apr 28, 18:52 UTC

Update - 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 subset of users

Severity:
SEV-2

Steps to take

Please add the following step to your workflows. You can reach out to the Bitrise support team if you have any questions. https://bitrise.io/integrations/steps/install-missing-android-tools

When will the next update be available?

You can expect a status update approximately 1 hour from now.
Apr 28, 18:01 UTC

Monitoring - 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 monitor the situation.

When will the next update be available?

You can expect a status update approximately 1 hour from now.
Apr 28, 17:25 UTC

Identified - 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 services. 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.
Apr 28, 16:38 UTC

Investigating - 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, monitoring alerts, and tracing requests to identify the root cause. 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.
Apr 28, 13:38 UTC

Elevated error rates on build details page

Resolved - This incident has been resolved.
Apr 28, 17:27 UTC

Monitoring - 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.
Apr 28, 12:29 UTC

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

Apr 23, 2026

No incidents reported.

Apr 22, 2026

No incidents reported.

Apr 21, 2026

No incidents reported.

Apr 20, 2026

Experiencing issues with billing cycle refreshing credits/builds for certain Bitrise plans

Resolved - This incident has been resolved.
Apr 20, 19:45 UTC

Identified - The issue has been identified and a fix is being implemented.
Apr 20, 16:37 UTC

Investigating - 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.
Apr 20, 16:37 UTC

Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage