Bitrise: Interrupted builds and longer queue times

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 44m it lasted.
Anything that failed between 2026-11-06 16:40 UTC and 2026-11-06 17:24 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.

investigatingNov 6, 2026, 4:40 PM UTC
We are currently investigating reports of interrupted builds and longer-than-usual build queue times for some users. Our infrastructure has since begun recovering, and we are monitoring the situation while we continue to investigate. We will provide a further update as soon as more information is available.
provider
monitoringNov 6, 2026, 5:11 PM UTC
A fix has been implemented and builds are recovering. We are monitoring the results. If you are still experiencing interrupted builds or longer queue times, please retry your build and contact support if the issue persists.
provider
resolvedNov 6, 2026, 5:24 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Bitrise still down?

No, this incident was resolved 2026-11-06 17:24 UTC. For Bitrise's live state, see https://down.guide/bitrise.

How long did it last?

44m, from 2026-11-06 16:40 UTC to 2026-11-06 17:24 UTC, by the times Bitrise posted.

What was affected?

Bitrise named ⚙️ Builds (CI).

What caused it?

Bitrise hasn't published a root cause. If it does, it shows here.

Where does this come from?

Bitrise's official status page, https://status.bitrise.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.