Bitrise change history

Bitrise reported a major Builds (CI) incident: users may have been unable to open or use the Website UI’s Start Build dialog, while underlying build triggers were unaffected. It started at 2026-10-05 08:36 UTC and was resolved at 2026-10-05 10:55 UTC, lasting 2 h 18 min. A fix was implemented at 08:46 UTC.

Bitrise reported a major incident affecting Builds (CI): the Builds List page failed to load in multiple workspaces. It started at 2026-08-28 13:01 UTC and was resolved at 2026-08-28 13:33 UTC, lasting 32 min; no cause or fix was stated.

Bitrise reported a major ORD data center outage affecting Builds (CI), with possible failures or delays, starting 2026-07-14 16:40 UTC and resolved after 25 h 33 min. Dropped packets between nodes caused failed health checks and cluster-wide disruption; mitigation restored job scheduling, and network configuration changes were applied across all data centers.

Bitrise’s Workflow Editor experienced elevated HTTP errors, page-load failures and timeouts affecting all users in a major (SEV-1) incident from 2026-07-10 17:49 UTC to 2026-07-10 19:50 UTC, lasting 2 h 1 min. Bitrise attributed it to an ongoing LaunchDarkly incident affecting flag delivery evaluations; a workaround restored normal loading before resolution.

A subset of Bitrise Builds (CI) experienced intermittent DNS failures in a major (SEV-1) incident starting 2026-07-08 20:19 UTC. Bitrise implemented a fix and began monitoring at 2026-07-08 21:01 UTC, then resolved the incident at 2026-07-08 21:30 UTC; the reported duration was 1 h 10 min.

Bitrise reported a major Builds (CI) incident that delayed builds from starting on Linux machines. It started at 2026-07-08 13:54 UTC and was resolved at 2026-07-09 07:57 UTC, lasting 18 h 2 min; no cause or specific fix was stated.

Bitrise reported a major Builds (CI) degradation affecting M4 Pro build queues from 2025-11-18 17:20 UTC to 2025-11-18 20:38 UTC, lasting 3 h 18 min. Bitrise attributed longer build-start waits to increased build volume following an earlier Cloudflare outage; execution remained normal. The incident was resolved with waits around 30 seconds across most queues.

Bitrise’s web application (app.bitrise.io) was unavailable in a major incident affecting Builds (CI), from 2025-11-18 11:53 UTC to 2025-11-18 20:36 UTC (8 h 43 min). Bitrise attributed the errors to a Cloudflare Global Network outage, stopped routing traffic through Cloudflare, and re-enabled Cloudflare services before resolution.

Bitrise reported major (SEV-1) degradation of Builds (CI), with long Mac stack queue waits and build start delays due to degraded VM startup. It started at 2025-11-10 11:10 UTC and resolved at 2025-11-10 11:14 UTC; the reported duration was 3 min. Engineering released a mitigating fix and monitored systems before resolution.

Bitrise reported a major (SEV-2) degradation affecting build queues on M4 Pro machines, with longer waits for builds to start; execution remained normal once a worker was allocated. It started at 2025-10-30 16:18 UTC and was resolved at 2025-10-30 17:55 UTC, lasting 1 h 37 min.

Bitrise reported a major Builds (CI) degradation: capacity issues on M4 Pro machines could delay build launches. It started at 2025-10-28 16:21 UTC and was resolved at 2025-10-28 19:04 UTC, lasting 2 h 42 min; no specific fix was stated.

Bitrise reported a major outage of billing and subscription management because its billing service provider was down due to an AWS outage; builds ran without issues. The incident started at 2025-10-20 10:10 UTC and was resolved at 2025-10-20 14:24 UTC, lasting 4 h 13 min.