Skip to main content
Bitrise

503 error in Firebase Virtual Device Testing for Android step

Degraded Lasted 19h 46m · started · Bitrise's page

Level
confirmed
Worst impact
Degraded
Components
⚙️ Builds (CI)
Down Index
24of 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 19h 46m it lasted.

    Anything that failed between 2026-06-25 10:28 UTC and 2026-06-26 06:14 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 2

  1. investigating

    We are seeing elevated error rates in Virtual Device Testing steps, resulting from the Google Cloud Tool Results API being intermittently unavailable. We are monitoring the situation.

    provider

  2. resolved

    We improved the handling of transient Firebase errors, Virtual Device Steps are back to normal.

    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-982836283a

Is Bitrise still down?

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

How long did it last?

19h 46m, from 2026-06-25 10:28 UTC to 2026-06-26 06:14 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.