Firebase's Test Lab component ran into delays for 19 minutes on 11 November 2026. The fault sat on Google's side of Firebase, not in your test configuration.
Started
18:22 UTC
Duration
Lasted 19m
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's own status page logged one incident on this day, titled "Test Lab experiencing delays", starting at 18:22 UTC and lasting 19 minutes. Test Lab was the only component listed as affected. Firebase published no updates during this incident, zero in total, so there is no first-hand account of what the delay looked like from Google's side or how it was resolved. No user reports were filed during this window, which for a 19 minute delay on a single component is not surprising, since many teams would not notice a short lag in test runs at all. The incident carries no severity label worth repeating here, because Firebase grades its own incidents and that grade is not the same as the impact on your builds. Over the past 90 days Firebase has logged 15 incidents with a median duration of 6 hours 52 minutes, which makes this 19 minute delay short by Firebase's own recent standards. Across its full history, Firebase averages 5.5 incidents a month over 287 recorded incidents, so this kind of brief disruption is a regular feature of running on Firebase rather than an outlier. There is no post-mortem published for this incident. If you were running automated test suites through Test Lab around 18:22 UTC on 11 November, a short delay in queued or completed runs is the most likely symptom, consistent with the title Firebase gave the incident.
Learning
This incident did not come with an our_probes entry on this page, which means the signal here is Firebase's own status page rather than an external check of Test Lab's behaviour. Test Lab is a build and test execution layer, not a simple endpoint you can ping, so a delay in test runs is the kind of fault that would not show up in a standard uptime check pointed at your own application. Your own monitoring watches whether your product responds to requests, which is a different question from whether Google's test infrastructure is processing jobs on schedule. A 19 minute delay with no updates and no user reports is easy to miss entirely if you are only watching your own side. The pattern to recognise is simple: when build or test pipelines stall without any corresponding drop in your application's own uptime, the fault is more likely sitting with the dependency than with you. Firebase's history of 15 incidents in 90 days means this is not a one-off, so it is worth knowing which side of the pipeline failed rather than assuming your own configuration is at fault. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.