Companies / Bitrise / incidents
Bitrise: Queues on M4 Pro
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.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: ⚙️ Builds (CI)
Timeline of updates
- 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>What’s happening?</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 machines <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.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Queues on M4 Pro 2025-10-30 16:18 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Bitrise profile · Recent Bitrise incidents · Markdown · JSON