Vendor reports: degradedResolved · vendor status “resolved”Official status API

503 error in Firebase Virtual Device Testing for Android step

Reported by Bitrise · Developer Tools & CI/CD · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Jun 25, 2026, 10:28 UTC
Vendor's clock
Resolved
Jun 26, 2026, 06:14 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
19 h 46 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Bitrise reports degraded: "503 error in Firebase Virtual Device Testing for Android step".[E1, E2]
  • The vendor marked it resolved at 2026-06-26 06:14 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-06-26 06:14 UTC · summary s1, evidence 67b032e6758994c4

Evidence (7)
  1. E1Bitrise reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "503 error in Firebase Virtual Device Testing for Android step". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-25 10:28 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-06-26 06:14 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Bitrise is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jun 25, 2026, 10:28 UTCVendor-reported startVendor time
  2. Jun 26, 2026, 06:14 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.