Bitrise Outage History
Daily status observations, past incidents, and reported issue history for Bitrise.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 32% | 25 | 17 |
| July 2026 | 35.5% | 31 | 20 |
| June 2026 | 60% | 30 | 12 |
| May 2026 | 0% | 5 | 5 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Inreased queues on Linux machines
Started:
investigating
We are experiencing increased build queues on our Linux machines, we are currently investigating the issue.
July 2026
Public VNC access is temporarily disabled on remote access builds and RDE sessions
Started:
⚙️ Builds (CI)
identified
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 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.
Elevated error rates on Bitrise Website
Started:
monitoring
Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.
identified
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.
investigating
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.
ORD data center network outage
Started:
monitoring
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.
investigating
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.
Slow or hanging builds during clone and dependency resolution
Started:
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
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.
Degraded Build Cache in IAD datacenter
Started:
investigating
We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.
Elevated error rates for the Bitrise Workflow Editor
Started:
monitoring
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.
investigating
<b>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.</b>
<b>Services impacted:</b>
The Workflow Editor may return errors or fail to load.
<b>Scope:</b>
[All users]
<b>Severity:</b>
[SEV-1]
<b>What we’re doing?</b>
Our Engineering teams are actively investigating this incident, monitoring alerts, and tracing requests to identify the roo...
Elevated errors with Bitrise Build Pipeline
Started:
monitoring
<b>We mitigated this incident and are currently monitoring our systems.</b>
<b>Services:</b>
Build Pipelines
<b>Scope:</b>
[All users]
<b>Severity:</b>
[SEV-1]
<b>What we’re doing</b>
Our Engineering teams released a fix to mitigate this incident and are now actively monitoring our systems.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1 hour</b> from now.
investigating
<b>We are currently investigating an incident causing elevated errors in Pipelines</b>
<b>Services:</b>
Build Pipelines
<b>Scope:</b>
[All users]
<b>Severity:</b>
[SEV-1]
<b>What we’re doing?</b>
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.
<b>When will th...
Intermittent DNS failures
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
<b> A subset of Bitrise builds are experiencing intermittent DNS failures. </b>
<b>Scope:</b>
[A subset of users]
<b>Severity:</b>
[SEV-1]
<b>What we’re doing?</b>
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.
<b>When will the next update be available?<b>
You can expect a status update a...
Linux machines on hold
Started:
investigating
We are experiencing a delay in starting builds on Linux machines, we are investigating the issue.
June 2026
Potential issues withGradle init script compile
Started:
identified
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.
503 error in Firebase Virtual Device Testing for Android step
Started:
investigating
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.
Long waiting times on M4 Pro Machines
Started:
investigating
<b>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.</b>
<b>Services:</b>
Build start times and queue wait times; build execution itself remains normal once a worker is allocated.
<b>Scope:</b>
Builds on M4 Pro Stacks
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
Our Engineering teams are actively investigating causes, reviewing worker pool utilization...
Builds Failing
Started:
investigating
<b>Gradle builds in the ORD data center are experiencing failures with dependency resolution. Some users may experience build failures</b>
<b>Services:</b>
Gradle Repository Manager
<b>Scope:</b>
All builds in the ORD data center
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
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.
<b>When will th...
Issues with Data Center Connectivity
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
<b>We are currently investigating an incident causing to be unavailable.</b>
<b>Services:</b>
Data Center Connectivity
<b>Severity:</b>
SEV-1
<b>What we’re doing?</b>
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.
<b>When will the next update be available?</b...
May 2026
Artifact upload failures in Store Releases
Started:
investigating
We are continuing to investigate this issue.
investigating
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.
April 2026
Elevated error rate with Android builds
Started:
identified
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 <b><a href="https://discuss.bitrise.io/t/new-gradle-mirrors-on-bitrise-to-help-avoid-maven-central-rate-limits/25888">guide</a></b>.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1 hour</b> from now.
identified
<b>What we’re doing?</b>
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 w...
identified
For customers having dependency verification enabled for their Android builds, you will need to update your configuration based on our updated <b><a href="https://docs.google.com/document/d/1mrquZ-n7dNNmQo0o4ddzY73JTsY5xkYRgRKARoKNFvs/edit?tab=t.0#heading=h.hldkjykpbhvu
">guide</a></b>.
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...
identified
<b>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.</b>
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1 hour</b> from now.
identified
<b>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</b>
<b>Services impacted:</b>
Android builds
<b>Severity:</b>
SEV-2
<b>When will the next update be available?<b>
You can expect a status update approximat...
Elevated error rates for Android builds
Started:
monitoring
<b>We are still taking additional measures and are observing decreasing instances of rate limiting</b>
<b>Services:</b>
Android Builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing:</b>
Our Engineering teams released an update to mitigate this incident and are actively monitoring our systems.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>2 hours</b> from now.
monitoring
<b>We have taken additional measures and are observing decreasing instances of rate limiting</b>
<b>Services:</b>
Android Builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing:</b>
Our Engineering teams released a fix to mitigate this incident and are actively monitoring our systems.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>2 hours</b> from now.
monitoring
<b>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</b>
<b>Services:</b>
Android builds
<b>Scope:</b>
[All users / a subset of users]
<b>Severity:</b>
SEV-2
<b>What we’re doing</b>
Our Engineering teams released an update to mitigate this incident and now actively monitoring our ...
identified
<b>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</b>
<b>Services impacted:</b>
Android builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
We are actively making adjustments to help resolve issues with the failing builds
<b>When will the next update be available?<b>
You can expect a status update approxima...
Elevated error rates for Android builds
Started:
monitoring
<b>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</b>
<b>Services:</b>
Android builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing</b>
We are actively monitoring our systems.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1 hour</b> from now.
monitoring
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
monitoring
<b>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</b>
<b>Services:</b>
Builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>Steps to take</b>
Please add the following step to your workflows. You can reach out to the Bitrise support team if you have any questions. https://...
monitoring
<b>We mitigated this incident and are currently monitoring our systems to resolve </b>
<b>Services:</b>
Android Builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-1
<b>What we’re doing</b>
Our Engineering teams released a fix to mitigate this incident. We expect new builds to start, and we continue to monitor the situation.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1 hour</b> from now.
identified
We are working on redirections to mitigate the current issue.
<b>Services:</b>
Android Builds
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
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.
<b>When will the next update be available?</b>
You can expect a status update approximately <b>1...
investigating
<b>We are currently investigating elevated errors for Android builds.</b>
<b>Services impacted:</b>
Android builds are failing due to MavenCentral request throttling
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
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.
<b>When will the next update be avai...
Elevated error rates on build details page
Started:
monitoring
<b>We mitigated this incident and are currently monitoring our systems to resolve HTTP errors, intermittent page load failures, or timeouts when accessing the site.</b>
<b>Services:</b>
Build details pages on app.bitrise.io are failing to load.
<b>Scope:</b>
Subset of users
<b>Severity:</b>
SEV-1
<b>What we’re doing</b>
Our Engineering teams released a fix to mitigate this incident and are now actively monitoring our systems.
<b>When will the next update be available?</b>
You can exp...
Experiencing issues with billing cycle refreshing credits/builds for certain Bitrise plans
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
<b>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.</b>
<b>Services:</b>
Features related to managing account details, teams and team members, billing and payments.
<b>Scope:</b>
A subset of users
<b>Severity:</b>
SEV-2
<b>What we’re doing?</b>
Our Engineering teams are actively investigating this incident, monitoring al...
Elevated Queue Times on Linux Machines
Started:
investigating
<b>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.</b>
<b>Services:</b>
Build start times and queue wait times; build execution itself remains normal once a worker is allocated.
<b>Scope:</b>
Queues on standard, elite, and elite-xl machines
<b>Severity:</b>
[SEV-2]
<b>What we’re doing?</b>
Our Engineering teams are actively investigating causes, revie...
March 2026
Elevated Queue Times on Linux Machines
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.