Elevated Queue Times on Linux Machines

What to do

• Check whether you use Bitrise ⚙️ Builds (CI). Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 31m it lasted.

  Anything that failed between 2026-04-15 20:23 UTC and 2026-04-15 20:54 UTC may need a replay.

• Subscribe to Bitrise's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=bitrise works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bitrise 3

1. investigatingApr 15, 2026, 8:23 PM UTC

   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. Services: Build start times and queue wait times; build execution itself remains normal once a worker is allocated. Scope: Queues on standard, elite, and elite-xl machines Severity: [SEV-2] What we’re doing? 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. When will the next update be available? You can expect a status update approximately 1 hour from now.

   provider

2. identifiedApr 15, 2026, 8:43 PM UTC

   We identified the root cause of 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. Services: Build start times and queue wait times; build execution itself remains normal once a worker is allocated. Scope: Queues on standard, elite, and elite-xl machines Severity: SEV-2 What we’re doing? Our Engineering teams identified the root cause and are now actively working on mitigations to restore stability across all affected services. We will perform validated mitigations as soon as they are determined safe. When will the next update be available? You can expect a status update approximately 1 hour from now.

   provider

3. resolvedApr 15, 2026, 8:54 PM UTC

   This incident is now resolved, and impacted services are now operating without issues. Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future. Thank you for your patience and understanding. If you encounter any issues, please reach out to our Support team: https://support.bitrise.io/en/

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.