Resolved -
This incident has been resolved.
Jul 17, 00:13 UTC
Monitoring -
Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.
Jul 17, 00:04 UTC
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.
Jul 16, 23:24 UTC
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.
Jul 16, 23:04 UTC
Resolved -
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.
Jul 15, 18:13 UTC
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.
Jul 14, 18:18 UTC
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.
Jul 14, 16:40 UTC
Resolved -
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.
Jul 15, 18:10 UTC
Update -
We are continuing to investigate this issue.
Jul 14, 16:30 UTC
Update -
We are continuing to investigate this issue.
Jul 14, 15:36 UTC
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.
Jul 14, 15:35 UTC
Resolved -
This incident has been resolved.
Jul 13, 10:49 UTC
Investigating -
We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.
Jul 13, 09:08 UTC
Completed -
The scheduled maintenance has been completed.
Jul 13, 04:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 21:45 UTC
Scheduled -
From 21:45 UTC Friday, 10 July, until 04:00 UTC Monday, 13 July, Bitrise will perform general maintenance on our infrastructure. This will reduce the M4 Pro, M2 Pro and Linux capacity, with a small chance of causing wait times during the weekend. We apologize for any inconvenience.
Jul 10, 13:27 UTC
Resolved -
This incident has been resolved.
Jul 10, 19:50 UTC
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.
Jul 10, 18:37 UTC
Investigating -
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.
Jul 10, 17:49 UTC
Completed -
The scheduled maintenance has been completed.
Jul 10, 05:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 04:00 UTC
Scheduled -
From 23:45 UTC Friday, 10 July, until 04:00 UTC Monday, 13 July, Bitrise will perform general maintenance on our infrastructure. This will reduce the M4 Pro, M2 Pro and Linux capacity, with a small chance of causing wait times during the weekend. We apologize for any inconvenience.
Jun 22, 09:26 UTC
Resolved -
This incident has been resolved.
Jul 9, 12:12 UTC
Monitoring -
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.
Jul 9, 09:29 UTC
Investigating -
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.
Jul 9, 09:05 UTC
Resolved -
This incident has been resolved.
Jul 8, 21:30 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 8, 21:01 UTC
Update -
We are continuing to investigate this issue.
Jul 8, 20:21 UTC
Investigating -
A subset of Bitrise builds are experiencing intermittent DNS failures.
Scope: [A subset of users]
Severity: [SEV-1]
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.
Jul 8, 20:19 UTC
Resolved -
This incident has been resolved.
Jul 7, 15:09 UTC
Identified -
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.
Jul 7, 15:06 UTC