- Level
- confirmed
- Worst impact
- Degraded
- Components
- ⚙️ Builds (CI)
- Down Index
- 21of 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 3h 20m it lasted.
Anything that failed between 2026-03-09 12:21 UTC and 2026-03-09 15:41 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 4
- investigating
We have noticed build related issues with our web UI, starting new builds, incoming webhooks, and accessing build artifacts of running builds. We are currently investigating.
provider
- identified
We managed to attribute the high error rate to an incident affecting Google Kubernetes Engine.
provider
- monitoring
Google has applied a workaround, and error rates are decreasing. Operations are returning to normal.
provider
- 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-5dbd0dc331
Is Bitrise still down?
No, this incident was resolved 2026-03-09 15:41 UTC. For Bitrise's live state, see https://down.guide/bitrise.
How long did it last?
3h 20m, from 2026-03-09 12:21 UTC to 2026-03-09 15:41 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.