New Multi-region uptime checks and custom-domain status pages

Bitrise Outage History

Daily provider-status observations and published incident history for Bitrise.

Operational

Bitrise is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Bitrise for future changes.

70.4% of 54 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 80% 30 6

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.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Issue with the Start Build dialog in the Website UI
major Observed active window 2h 23m

View incident details and source

Started:

⚙️ Builds (CI)
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Users may be unable to open or use the Start Build dialog in the UI. This does not impact the underlying build trigger functionality., we are investigating the issue.
September 2026
Long waiting times [on specific stacks / to start builds]
minor Observed active window 1h 9m

View incident details and source

Started:

⚙️ Builds (CI)
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, 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. <b>When will the next update be available?</b> You can expect a status update approximately <b>1 hour</b> from now.
Key Value Dependency Cache Service
minor Observed active window 1h 52m

View incident details and source

Started:

Key Value Dependency Cache Service
monitoring
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.
August 2026
CI build list is not loading in multiple workspaces
major Observed active window 33m

View incident details and source

Started:

⚙️ Builds (CI)
investigating
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.
investigating
We are currently investigating this issue.
July 2026
Public VNC access is temporarily disabled on remote access builds and RDE sessions
minor Observed active window 765h 49m

View incident details and source

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.

Legacy Incident Archive

22 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Inreased queues on Linux machines
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are experiencing increased build queues on our Linux machines, we are currently investigating the issue.
July 2026
Elevated error rates on Bitrise Website
minor Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
minor Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
major Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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.