Bitrise Outage History

52 incidents recorded over the last 365 days, 45 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bitrise status99.82% uptime history

Every Recorded Bitrise Incident

Bitrise incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Elevated errors on Bitrise pages in SafariThis incident has been resolved.1h 17mResolved
Oct 26, 2026Long waiting times (queue) on buildsThis incident has been resolved.31 minResolved
Oct 10, 2026Network infrastructure maintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Oct 5, 2026Issue with the Start Build dialog in the Website UIThis incident has been resolved.2h 18mResolved
Sep 22, 2026Long waiting times [on specific stacks / to start builds]This incident has been resolved.1h 6mResolved
Sep 20, 2026Scheduled Network Maintenance on BitriseThe scheduled maintenance has been completed.3h 0mScheduled
Sep 5, 2026Key Value Dependency Cache ServiceThis incident has been resolved.1h 49mResolved
Aug 28, 2026CI build list is not loading in multiple workspacesThis incident has been resolved.32 minResolved
Aug 7, 2026Increased queues on Linux machinesThis incident has been resolved.57 minResolved
Jul 30, 2026Public VNC access is temporarily disabled on remote access builds and RDE sessionsThis incident has been resolved.765h 48mResolved
Jul 16, 2026Elevated error rates on Bitrise WebsiteThis incident has been resolved.1h 9mResolved
Jul 16, 2026Website high error rate due to database migration issueWe experienced a brief period of high error rates on our website. The issue was resolved after a rollback.0 minResolved
Jul 14, 2026ORD data center network outageThis 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…25h 33mResolved
Jul 14, 2026Slow or hanging builds during clone and dependency resolutionThis 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…26h 35mResolved
Jul 13, 2026Degraded Build Cache in IAD datacenterThis incident has been resolved.1h 41mResolved
Jul 10, 2026Scheduled maintenance on M4 Pro, M2 Pro and Linux infrastructureThe scheduled maintenance has been completed.54h 15mScheduled
Jul 10, 2026Elevated error rates for the Bitrise Workflow EditorThis incident has been resolved.2h 1mResolved
Jul 10, 2026Scheduled maintenance on M4Pro, M2 Pro and Linux infrastructureThe scheduled maintenance has been completed.1h 0mScheduled
Jul 9, 2026Elevated errors with Bitrise Build PipelineThis incident has been resolved.3h 6mResolved
Jul 8, 2026Intermittent DNS failuresThis incident has been resolved.1h 10mResolved
Jul 8, 2026Linux machines on holdThis incident has been resolved.18h 2mResolved
Jul 7, 2026Experiencing networking connectivity issues in our IAD datacenterThis incident has been resolved.3 minResolved
Jun 26, 2026Potential issues withGradle init script compileThis incident has been resolved.12h 44mResolved
Jun 25, 2026503 error in Firebase Virtual Device Testing for Android stepWe improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.19h 46mResolved
Jun 23, 2026Build logs containing malformed sections instead of the usual structured dataWe have observed some malformed data appearing in build logs, we have quickly issues a fix and this has been resolved.-132 minResolved
Jun 17, 2026Long waiting times on M4 Pro MachinesThis incident has been resolved.55 minResolved
Jun 11, 2026Builds FailingThis incident has been resolved.12 minResolved
Jun 11, 2026Issues with Data Center ConnectivityThis incident has been resolved.1h 56mResolved
May 28, 2026Artifact upload failures in Store ReleasesThis incident has been resolved.137h 52mResolved
Apr 30, 2026Elevated error rate with Android builds<b>This incident is now resolved, and impacted services are now operating.</b> Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll…34h 16mResolved
Apr 29, 2026Elevated error rates for Android buildsOn 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…9h 48mResolved
Apr 28, 2026Elevated error rates for Android builds<b>This incident is now resolved and impacted services are now operating without issues.</b> Our teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is…8h 36mResolved
Apr 28, 2026Elevated error rates on build details pageThis incident has been resolved.4h 58mResolved
Apr 20, 2026Experiencing issues with billing cycle refreshing credits/builds for certain Bitrise plansThis incident has been resolved.3h 8mResolved
Apr 15, 2026Elevated Queue Times on Linux Machines<b>This incident is now resolved, and impacted services are now operating without issues.</b> Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation…31 minResolved
Mar 21, 2026Scheduled maintenance on BitriseThe scheduled maintenance has been completed.8h 0mScheduled
Mar 19, 2026Elevated Queue Times on Linux MachinesThis incident has been resolved.5h 50mResolved
Mar 9, 2026Build IssuesThis incident has been resolved.3h 20mResolved
Mar 5, 2026Deploy to Bitrise step failing due to network issuesThis incident has been resolved.30 minResolved
Mar 2, 2026Increase build queues on all StacksThis incident has been resolved.1h 33mResolved
Mar 2, 2026Increase build queues on all StacksThis incident has been resolved.2h 29mResolved
Mar 2, 2026Increased error rates in build triggering.This incident has been resolved.8 minResolved
Feb 11, 2026Issues with Pipelines API EndpointThis incident has been resolved.2h 48mResolved
Dec 5, 2025www.bitrise.io downWe observed high error rates affecting our static site (bitrise.io) due to Cloudflare’s incident between 8:56 - 9:12 UTC app.bitrise.io was unaffected-361 minResolved
Dec 5, 2025Scheduled maintenance on M1 Mac mini infrastructureThe scheduled maintenance has been completed.1h 0mScheduled
Dec 3, 2025Issues with passing values to environment variables<b>This incident is now resolved and impacted services are now operating without issues.</b> Our teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is…41 minResolved
Dec 3, 2025Scheduled maintenance on M1 Mac mini infrastructureThe scheduled maintenance has been completed.4h 0mScheduled
Nov 26, 2025Users might experience issues with Android builds hangingThis incident has been resolved.22h 18mResolved
Nov 25, 2025Slower response times on Bitrise web app and REST APIThis incident has been resolved.24 minResolved
Nov 18, 2025Long waiting times on M4 Pro machine (queue) buildsWait times have now dropped to approximately 30 seconds across most queues. This incident has been resolved.3h 18mResolved
Nov 18, 2025Bitrise web application (app.bitrise.io) unavailableThis incident has been resolved.8h 43mResolved
Nov 10, 2025Long waiting times on Mac stacks due to degraded VM startupThis incident has been resolved.3 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Bitrise incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Bitrise Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bitrise acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Bitrise outage in this window ran 31d 21h, against a mean recovery of 1d. If you depend on Bitrise in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.