Firebase's Realtime Database saw degraded performance for users in the us-central1 region for 24 hours and 19 minutes on 21 October 2026. The fault sat with Firebase's infrastructure, not with anything in your own app.
Started
14:39 UTC
Duration
Lasted 1d 0h
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: Realtime Database
What happened?
Firebase logged one incident on this day, titled "Partial performance degradation for RTDB users in us-central1", starting at 14:39 UTC and lasting 24h 19m. The affected component is listed as Realtime Database, and only that one component shows any impact for the day. Firebase's status page carries no updates for this incident beyond the initial filing, so there is no timeline of escalation, mitigation or recovery to report. No user reports were filed during this window on record, which is unusual for an incident lasting a full day but is what the record shows. Firebase calls this "partial" degradation rather than a full outage, but that is Firebase's own grading, not a measure of what it cost you if your RTDB traffic routes through us-central1. With zero updates published, there is no explanation on record for what caused the degradation or what fixed it. Over the past 90 days Firebase has logged 16 incidents with a median duration of 9 hours 27 minutes, so a 24h 19m incident sits well above that median. Across its full history Firebase has recorded 287 incidents, averaging 5.5 per month, which gives useful context for how often this provider's status page gets an entry at all. For this specific day, one incident, one affected component, and a single filing with no follow-up is the whole record.
Learning
A regional database performance issue like this one often shows up as slower reads and writes or intermittent timeouts rather than a hard outage, which is exactly the kind of fault that a simple uptime check on your own endpoint can miss entirely. Your monitoring watches whether your product responds, but the Realtime Database itself is a layer underneath that, running on Firebase's infrastructure in a specific region. If your health check doesn't exercise RTDB reads and writes against us-central1 specifically, it can stay green while your actual data layer is degraded for your users. That is consistent with this incident drawing no user reports in the window even though it ran for over a day. Over UptimeRobot's own last 30 days of watching Firebase, there were 6 incidents with 5 resolved and a median duration of 9h 27m, a very similar figure to Firebase's own 90-day median, which suggests this kind of regional RTDB slowdown is a recurring pattern 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.