Bitrise Outage History
Bitrise degraded View live status →Pingoru has recorded 53 incidents for Bitrise: 46 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 36 of 720 (5%) |
| May 2026 | 1 | 103 of 744 (14%) |
| June 2026 | 6 | 93 of 720 (13%) |
| July 2026 | 11 | 85 of 744 (11%) |
| August 2026 | 2 | 304 of 744 (41%) |
| September 2026 | 2 | 3 of 720 (0%) |
| October 2026 | 1 | 2 of 521 (0%) |
Incidents, newest first
Major October 5, 2026 Issue with the Start Build dialog in the Website UI 2h 18m ⚙️ Builds (CI)
Started Oct 05, 2026, 08:36 AM UTC· resolved Oct 05, 2026, 10:55 AM UTC
- investigating Oct 05, 2026, 08:36 AM UTC
We have reports of users being unable to start new builds and being bet with a 500 error, we are investigating the issue.
- identified Oct 05, 2026, 08:36 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 05, 2026, 08:46 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 05, 2026, 10:55 AM UTC
This incident has been resolved.
Minor September 22, 2026 Long waiting times [on specific stacks / to start builds] 1h 6m ⚙️ Builds (CI)
Started Sep 22, 2026, 04:15 PM UTC· resolved Sep 22, 2026, 05:21 PM UTC
- investigating Sep 22, 2026, 04:15 PM UTC
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.
- resolved Sep 22, 2026, 05:21 PM UTC
This incident has been resolved.
Minor September 5, 2026 Key Value Dependency Cache Service 1h 49m Key Value Dependency Cache Service
Started Sep 05, 2026, 12:52 PM UTC· resolved Sep 05, 2026, 02:41 PM UTC
- monitoring Sep 05, 2026, 12:52 PM UTC
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.
- resolved Sep 05, 2026, 02:41 PM UTC
This incident has been resolved.
Major August 28, 2026 CI build list is not loading in multiple workspaces 32m ⚙️ Builds (CI)
Started Aug 28, 2026, 01:01 PM UTC· resolved Aug 28, 2026, 01:33 PM UTC
- investigating Aug 28, 2026, 01:01 PM UTC
We are currently investigating this issue.
- investigating Aug 28, 2026, 01:04 PM UTC
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.
- resolved Aug 28, 2026, 01:33 PM UTC
This incident has been resolved.
Minor August 7, 2026 Increased queues on Linux machines 57m ⚙️ Builds (CI)
Started Aug 07, 2026, 01:02 PM UTC· resolved Aug 07, 2026, 02:00 PM UTC
- investigating Aug 07, 2026, 01:02 PM UTC
We are experiencing increased build queues on our Linux machines, we are currently investigating the issue.
- resolved Aug 07, 2026, 02:00 PM UTC
This incident has been resolved.
Minor July 30, 2026 Public VNC access is temporarily disabled on remote access builds and RDE sessions 31d 21h ⚙️ Builds (CI)
Started Jul 30, 2026, 03:40 PM UTC· resolved Aug 31, 2026, 01:29 PM UTC
- identified Jul 30, 2026, 03:40 PM UTC
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.
- resolved Aug 31, 2026, 01:29 PM UTC
This incident has been resolved.
Minor July 16, 2026 Elevated error rates on Bitrise Website 1h 9m GitHub API Requests
Started Jul 16, 2026, 11:04 PM UTC· resolved Jul 17, 2026, 12:13 AM UTC
- investigating Jul 16, 2026, 11:04 PM UTC
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.
- identified Jul 16, 2026, 11:24 PM UTC
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.
- monitoring Jul 17, 2026, 12:04 AM UTC
Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.
- resolved Jul 17, 2026, 12:13 AM UTC
This incident has been resolved.
Minor July 16, 2026 Website high error rate due to database migration issue –
Started Jul 16, 2026, 02:51 PM UTC· resolved Jul 16, 2026, 02:51 PM UTC
- resolved Jul 16, 2026, 02:51 PM UTC
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.
Major July 14, 2026 ORD data center network outage 1d 1h ⚙️ Builds (CI)
Started Jul 14, 2026, 04:40 PM UTC· resolved Jul 15, 2026, 06:13 PM UTC
- investigating Jul 14, 2026, 04:40 PM UTC
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.
- monitoring Jul 14, 2026, 06:18 PM UTC
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.
- resolved Jul 15, 2026, 06:13 PM UTC
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.
Minor July 14, 2026 Slow or hanging builds during clone and dependency resolution 1d 2h ⚙️ Builds (CI), GitHub Git Operations
Started Jul 14, 2026, 03:35 PM UTC· resolved Jul 15, 2026, 06:10 PM UTC
- investigating Jul 14, 2026, 03:35 PM UTC
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.
- investigating Jul 14, 2026, 03:36 PM UTC
We are continuing to investigate this issue.
- investigating Jul 14, 2026, 04:30 PM UTC
We are continuing to investigate this issue.
- resolved Jul 15, 2026, 06:10 PM UTC
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.
Minor July 13, 2026 Degraded Build Cache in IAD datacenter 1h 41m Build Cache
Started Jul 13, 2026, 09:08 AM UTC· resolved Jul 13, 2026, 10:49 AM UTC
- investigating Jul 13, 2026, 09:08 AM UTC
We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.
- resolved Jul 13, 2026, 10:49 AM UTC
This incident has been resolved.
Major July 10, 2026 Elevated error rates for the Bitrise Workflow Editor 2h 1m ⚙️ Builds (CI)
Started Jul 10, 2026, 05:49 PM UTC· resolved Jul 10, 2026, 07:50 PM UTC
- investigating Jul 10, 2026, 05:49 PM UTC
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.
- monitoring Jul 10, 2026, 06:37 PM UTC
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.
- resolved Jul 10, 2026, 07:50 PM UTC
This incident has been resolved.
Minor July 9, 2026 Elevated errors with Bitrise Build Pipeline 3h 6m ⚙️ Builds (CI)
Started Jul 09, 2026, 09:05 AM UTC· resolved Jul 09, 2026, 12:12 PM UTC
- investigating Jul 09, 2026, 09:05 AM UTC
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.
- monitoring Jul 09, 2026, 09:29 AM UTC
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.
- resolved Jul 09, 2026, 12:12 PM UTC
This incident has been resolved.
Major July 8, 2026 Intermittent DNS failures 1h 10m ⚙️ Builds (CI)
Started Jul 08, 2026, 08:19 PM UTC· resolved Jul 08, 2026, 09:30 PM UTC
- investigating Jul 08, 2026, 08:19 PM UTC
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.
- investigating Jul 08, 2026, 08:21 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 08, 2026, 09:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 08, 2026, 09:30 PM UTC
This incident has been resolved.
Major July 8, 2026 Linux machines on hold 18h 2m ⚙️ Builds (CI)
Started Jul 08, 2026, 01:54 PM UTC· resolved Jul 09, 2026, 07:57 AM UTC
- investigating Jul 08, 2026, 01:54 PM UTC
We are experiencing a delay in starting builds on Linux machines, we are investigating the issue.
- resolved Jul 09, 2026, 07:57 AM UTC
This incident has been resolved.
Minor July 7, 2026 Experiencing networking connectivity issues in our IAD datacenter 3m
Started Jul 07, 2026, 03:06 PM UTC· resolved Jul 07, 2026, 03:09 PM UTC
- identified Jul 07, 2026, 03:06 PM UTC
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.
- resolved Jul 07, 2026, 03:09 PM UTC
This incident has been resolved.
Notice June 26, 2026 Potential issues withGradle init script compile 12h 44m
Started Jun 26, 2026, 07:40 PM UTC· resolved Jun 27, 2026, 08:25 AM UTC
- identified Jun 26, 2026, 07:40 PM UTC
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.
- resolved Jun 27, 2026, 08:25 AM UTC
This incident has been resolved.
Minor June 25, 2026 503 error in Firebase Virtual Device Testing for Android step 19h 46m ⚙️ Builds (CI)
Started Jun 25, 2026, 10:28 AM UTC· resolved Jun 26, 2026, 06:14 AM UTC
- investigating Jun 25, 2026, 10:28 AM UTC
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.
- resolved Jun 26, 2026, 06:14 AM UTC
We improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.
Notice June 23, 2026 Build logs containing malformed sections instead of the usual structured data –
Started Jun 23, 2026, 09:00 AM UTC· resolved Jun 23, 2026, 09:00 AM UTC
- resolved Jun 23, 2026, 11:12 AM UTC
We have observed some malformed data appearing in build logs, we have quickly issues a fix and this has been resolved.
Minor June 17, 2026 Long waiting times on M4 Pro Machines 55m ⚙️ Builds (CI)
Started Jun 17, 2026, 03:34 PM UTC· resolved Jun 17, 2026, 04:29 PM UTC
- investigating Jun 17, 2026, 03:34 PM UTC
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.
- resolved Jun 17, 2026, 04:29 PM UTC
This incident has been resolved.
Minor June 11, 2026 Builds Failing 12m ⚙️ Builds (CI)
Started Jun 11, 2026, 08:26 PM UTC· resolved Jun 11, 2026, 08:39 PM UTC
- investigating Jun 11, 2026, 08:26 PM UTC
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.
- monitoring Jun 11, 2026, 08:38 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 11, 2026, 08:39 PM UTC
This incident has been resolved.
Minor June 11, 2026 Issues with Data Center Connectivity 1h 56m ⚙️ Builds (CI)
Started Jun 11, 2026, 04:50 PM UTC· resolved Jun 11, 2026, 06:46 PM UTC
- investigating Jun 11, 2026, 04:50 PM UTC
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.
- monitoring Jun 11, 2026, 04:50 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 11, 2026, 06:46 PM UTC
This incident has been resolved.
Minor May 28, 2026 Artifact upload failures in Store Releases 5d 17h 📦 Release Management
Started May 28, 2026, 03:00 PM UTC· resolved Jun 03, 2026, 08:52 AM UTC
- investigating May 28, 2026, 03:00 PM UTC
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.
- investigating May 28, 2026, 03:01 PM UTC
We are continuing to investigate this issue.
- resolved Jun 03, 2026, 08:52 AM UTC
This incident has been resolved.
Minor April 30, 2026 Elevated error rate with Android builds 1d 10h ⚙️ Builds (CI)
Started Apr 30, 2026, 11:34 AM UTC· resolved May 01, 2026, 09:50 PM UTC
- identified Apr 30, 2026, 11:34 AM UTC
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.
- identified Apr 30, 2026, 01:04 PM UTC
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.
- identified Apr 30, 2026, 02:01 PM UTC
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.
- identified Apr 30, 2026, 03:32 PM UTC
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.
- identified Apr 30, 2026, 07:45 PM UTC
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.
- resolved May 01, 2026, 09:50 PM UTC
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/
Minor April 29, 2026 Elevated error rates for Android builds 9h 48m ⚙️ Builds (CI)
Started Apr 29, 2026, 10:36 AM UTC· resolved Apr 29, 2026, 08:24 PM UTC
- identified Apr 29, 2026, 10:36 AM UTC
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.
- monitoring Apr 29, 2026, 02:03 PM UTC
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.
- monitoring Apr 29, 2026, 04:50 PM UTC
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.
- monitoring Apr 29, 2026, 07:15 PM UTC
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.
- resolved Apr 29, 2026, 08:24 PM UTC
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].