Bitrise had 37 outages in the last 2 years totaling 69h 45m of downtime — averaging 1.5 incidents per month.
There were 37 Bitrise outages since June 11, 2025 totaling 69h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some accounts are incorrectly being disabled by automated fraud detection. We are re-enabling legitimate accounts and investigating the cause of these false positives to prevent future instances
This incident has been resolved.
Due to an update the build cache was unusable outside of the Bitrise DCs. We have resolved this issue.
We are experiencing elevated queues and error rate due to network issues on our upstream provider. We are working on a solution with the team.
This incident has been resolved.
app.bitrise.io is currently unavailable. The team is investigating.
We're seeing errors across multiple internal services.
We've identified that we have problems with certificates preventing access to multiple Bitrise services. We are working on the fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're wrongly displaying "No Cache Connection Detected" for Bazel builds, even though the cache is still being used correctly and build performance are not affected. This started around 13:30 UTC
This incident has been resolved.
Swift package resolution of official Apple Swift packages from https://developer.apple.com/swift/packages/collections/apple.json is failing. The certificate for this package collection has expired. Apple must publish a new certificate to unblock teams reliant on this package collection.
This incident has been resolved.
We are aware that Ubuntu's main mirror (archive.ubuntu.com) is having issues, which causes package installations on Linux-based stacks to fail. We are working on a workaround.
We have applied a workaround; newly created builds should not have the issue anymore. In the meantime, the upstream Ubuntu mirror is also starting to recover. We are monitoring the situation.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We’re seeing signs of recovery and our teams are closely monitoring the situation.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We're experiencing an elevated level of errors and are currently looking into the issue. This may cause builds not to start.
We have identified that the recent increase in error rates is directly related to an ongoing outage with Google's services. Our investigation confirms that the root cause of these elevated errors stems from disruptions within Google's cloud infrastructure. Our teams are closely monitoring the situation. We understand the impact this has on your operations and appreciate your patience as this issue is being addressed. We will provide further updates as more information becomes available or when service is fully restored. Thank you for your understanding.
Google engineers have identified the root cause and have applied appropriate mitigations. They are still working on resolving the issue, and our engineers are actively monitoring the situation.
We’re seeing signs of recovery across our services following the Google Cloud outage. Some functionality has been restored, but we are still observing intermittent errors. Our team is actively working to ensure a smooth and complete recovery. We’ll continue to provide updates as we make progress.
All systems are working again. The impact of the Google outage will be investigated and anything remaining will be mitigated by our team. Thank you for your patience!
We are currently investigating this issue.
We have identified that builds with Gradle cache or Gradle analytics enabled (either manually or via the Bitrise step) are affected. Any other Android/Gradle builds are not affected. Thank you for your continued patience!
Due to Sonatype/MavenCentral rate limiting, we temporarily disabled Bitrise Build Cache for Gradle plugins to prevent failing builds. We're working on a fix to avoid the rate-limiting issue.
We made a change in the Activate Bitrise Build Cache for Gradle step, and in the Bitrise Build Cache CLI, and re-enabled the Bitrise Build Cache for Gradle plugins. We're monitoring the system.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.