Firebase favicon

Firebase outage on 2026-10-16

google.com
October 2026 16 Minor incident

Firebase's Test Lab ran at reduced capacity for 9h 27m on 16 October 2026, cutting into Android, iOS and Arm Emulator device availability. This was a fault on Firebase's side, not in your test setup.

Started

23:23 UTC

Duration

Lasted 9h 27m

Source

IsDown

Next time

Firebase is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Test Lab

What happened?

Firebase logged one incident on this day, affecting the Test Lab component. The incident title states reduced overall capacity for Android, iOS and Arm Emulator devices from 5 PM to 10 PM PT, which converts to the 23:23 UTC start recorded here and a total span of 9h 27m. Firebase published no updates on this incident, so there is no record of when capacity started degrading within that window, how severe the reduction got, or what fixed it. No user reports were filed during the window, which is plausible given that Test Lab capacity issues show up as slower or queued test runs rather than hard failures, something a developer might not think to report. One filing from Firebase, with zero follow-up updates, is all there is to go on here. Over the past 90 days Firebase has logged 16 incidents with a median duration of 10 hours 15 minutes, so this one sits close to the usual length for a Test Lab or similar capacity event. Across all time, Firebase averages 5.5 incidents a month, putting this in line with a service that has frequent, usually contained incidents rather than this being an anomaly. No post-mortem has been published explaining the root cause of the capacity reduction, and Firebase's status page does not say why capacity dropped on this occasion. The component list names only Test Lab, so other Firebase services were not flagged as affected in this record.

Learning

Test Lab capacity problems are a provider-side resourcing issue, not something you can see from inside your own app or CI pipeline, because your build and test scripts will simply report slower runs or timeouts without any indication that the cause sits upstream at Firebase. An external check against your own endpoints would stay green throughout an incident like this, since your app isn't down, it's the testing infrastructure behind it that's constrained. Over the last 30 days UptimeRobot's own monitoring recorded 7 incidents on Firebase, all resolved, with a median duration of 5h 28m, shorter than Firebase's own 90 day median, which tells you these capacity dips vary a lot in how long they run. The lesson is that device test queue slowdowns deserve the same suspicion as any other latency spike: check the vendor's status page before assuming your own test configuration broke. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.