# Bitrise: Major incident: Queues on M4 Pro

**Summary:** 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, sol)_
- Kind: Major incident · Label: degradation (model (Jev))
- Changed: 2025-10-30 16:18 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/zwfp9lzty0pm](https://stspg.io/zwfp9lzty0pm)
- [Company: Bitrise](https://rewindex.com/company/bitrise.md)
- Versions: before (none: first archived) → after incident\_version:177/71q36pd3hm0s@9548f0595bf1
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Queues on M4 Pro
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2025-10-30 16:18 UTC
```

**5. Added: Resolved time**

```diff
+ 2025-10-30 17:55 UTC
```

**6. Added: Affected components**

```diff
+ ⚙️ Builds (CI)
```

**7. Added: Update** (investigating) · 2025-10-30 16:18 UTC

```diff
+ <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.
```

**8. Added: Update** (resolved) · 2025-10-30 17:55 UTC

```diff
+ This incident has been resolved.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2025-10-30 16:18 UTC | Major incident: Queues on M4 Pro (this change) | degradation |

All Bitrise changes: [timeline](https://rewindex.com/company/bitrise/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/id274a2f5a25c48 · Markdown: https://rewindex.com/change/id274a2f5a25c48.md · JSON: https://rewindex.com/api/v1/changes/id274a2f5a25c48 · Generated 2026-10-18T03:31:49.114Z