Skip to main content
Bitrise

Elevated Queue Times on Linux Machines

Degraded Lasted 5h 51m · started · Bitrise's page

Level
confirmed
Worst impact
Degraded
Components
⚙️ Builds (CI)
Down Index
22of 100

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 5h 51m it lasted.

    Anything that failed between 2026-03-19 16:52 UTC and 2026-03-19 22:43 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. investigating

    We are currently investigating this issue.

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-997802001f

Is Bitrise still down?

No, this incident was resolved 2026-03-19 22:43 UTC. For Bitrise's live state, see https://down.guide/bitrise.

How long did it last?

5h 51m, from 2026-03-19 16:52 UTC to 2026-03-19 22:43 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.