Firebase Hosting served elevated 502 errors on requests for dynamic content for 2 hours and 6 minutes on 12 November 2026. The fault sat on Google's side of Hosting, not in your own code.
Started
16:43 UTC
Duration
Lasted 2h 6m
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: Hosting
What happened?
Firebase's status page logged one incident on this day, starting at 16:43 UTC and lasting 2h 6m. The title Google published is specific: "Firebase Hosting is experiencing slightly elevated 502 errors on requests for dynamic content". That wording points at dynamic content specifically, meaning server-rendered or function-backed responses through Hosting, rather than static file delivery. No updates were posted against this incident, so there is no record of when Google identified the cause, whether it escalated, or what fixed it. No user reports were filed during the window in the data available here. Firebase's own description uses the word "slightly", which is Google's grading of its own incident, not a measure of what you experienced if your product depends on Hosting for dynamic requests. Over the past 90 days Firebase has logged 15 incidents with a median duration of 5 hours 28 minutes, so this one ran shorter than typical. Across all time Firebase averages 5.6 incidents a month over 289 total. One component, Hosting, is listed as affected. No post-mortem has been published, and Google's status page gives no further detail beyond the single incident title and duration.
Learning
When a platform like Firebase Hosting returns elevated 502s on dynamic requests, the failure sits between your function or backend and the edge that serves it, a layer you don't control and can't patch from your own side. If you only monitor your own endpoints, you'd see requests fail or slow down without any way to tell whether your code broke or Google's routing did. That's the gap this kind of incident exposes: your health checks confirm your service is up, but they can't see the provider's internal path to the public internet. Over UptimeRobot's own 30 day window, Firebase logged 7 incidents, all resolved, with a median duration of 5h 28m, roughly matching the 90 day pattern, so short dips like this one are part of a recurring rhythm rather than a one off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.