Skip to content

Outage tracker / Firebase

Is Firebase down?

I'm having a problem

Vendor reports no incidentWhat Firebase reports

Firebase reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:24 UTC.

Firebase's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Firebase pass from all 10 regions we check.

As of Nov 5, 2026, 2:33 PM UTC, RealUptime's checks of Firebase passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:33 PM UTC
US-East1458 msChecks passing
US-West548 msChecks passing
Europe744 msChecks passing
Asia-Pacific1220 msChecks passing
US-Central610 msChecks passing
Canada623 msChecks passing
UK1014 msChecks passing
Southeast Asia1399 msChecks passing
Australia1861 msChecks passing
South America1553 msChecks passing
their status pagetheir claim, not our reading

Firebase reports: All systems operational (“No open incidents reported”)

from Firebase's own status page, checked Nov 5, 2026, 1:56 PM UTC
Firebase's own status page shows no incident, and our checks of Firebase pass right now.

This is Firebase's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Firebase response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 635ms2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 479ms2026-10-10 UTC: p95 439ms2026-10-11 UTC: p95 466ms2026-10-12 UTC: p95 457ms2026-10-13 UTC: p95 503ms2026-10-14 UTC: p95 345ms2026-10-15 UTC: p95 391ms2026-10-16 UTC: p95 627ms2026-10-17 UTC: p95 824ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 755ms2026-10-24 UTC: p95 738ms2026-10-25 UTC: p95 634ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.3sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 390ms2026-10-08 UTC: p95 387ms2026-10-09 UTC: p95 448ms2026-10-10 UTC: p95 372ms2026-10-11 UTC: p95 199ms2026-10-12 UTC: p95 431ms2026-10-13 UTC: p95 572ms2026-10-14 UTC: p95 441ms2026-10-15 UTC: p95 390ms2026-10-16 UTC: p95 411ms2026-10-17 UTC: p95 134ms2026-10-18 UTC: p95 125ms2026-10-19 UTC: p95 443ms2026-10-20 UTC: p95 503ms2026-10-21 UTC: p95 798ms2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 195ms2026-10-24 UTC: p95 857ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Europe
916msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 365ms2026-10-08 UTC: p95 304ms2026-10-09 UTC: p95 165ms2026-10-10 UTC: p95 269ms2026-10-11 UTC: p95 352ms2026-10-12 UTC: p95 311ms2026-10-13 UTC: p95 246ms2026-10-14 UTC: p95 233ms2026-10-15 UTC: p95 199ms2026-10-16 UTC: p95 216ms2026-10-17 UTC: p95 161ms2026-10-18 UTC: p95 789ms2026-10-19 UTC: p95 998ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 918ms2026-10-22 UTC: p95 877ms2026-10-23 UTC: p95 684ms2026-10-24 UTC: p95 802ms2026-10-25 UTC: p95 660ms2026-10-26 UTC: p95 680ms2026-10-27 UTC: p95 687ms2026-10-28 UTC: p95 760ms2026-10-29 UTC: p95 811ms2026-10-30 UTC: p95 599ms2026-10-31 UTC: p95 635ms2026-11-01 UTC: p95 608ms2026-11-02 UTC: p95 937ms2026-11-03 UTC: p95 754ms2026-11-04 UTC: p95 565ms2026-11-05 UTC: p95 916ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.4sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 531ms2026-10-08 UTC: p95 476ms2026-10-09 UTC: p95 459ms2026-10-10 UTC: p95 462ms2026-10-11 UTC: p95 431ms2026-10-12 UTC: p95 456ms2026-10-13 UTC: p95 396ms2026-10-14 UTC: p95 211ms2026-10-15 UTC: p95 394ms2026-10-16 UTC: p95 679ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 171ms2026-10-26 UTC: p95 257ms2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 738ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 953ms2026-11-01 UTC: p95 948ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 520ms2026-10-08 UTC: p95 556ms2026-10-09 UTC: p95 502ms2026-10-10 UTC: p95 512ms2026-10-11 UTC: p95 480ms2026-10-12 UTC: p95 512ms2026-10-13 UTC: p95 526ms2026-10-14 UTC: p95 217ms2026-10-15 UTC: p95 452ms2026-10-16 UTC: p95 880ms2026-10-17 UTC: p95 942ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 405ms2026-10-23 UTC: p95 604ms2026-10-24 UTC: p95 608ms2026-10-25 UTC: p95 436ms2026-10-26 UTC: p95 404ms2026-10-27 UTC: p95 471ms2026-10-28 UTC: p95 767ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Canada
1.3sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 488ms2026-10-08 UTC: p95 479ms2026-10-09 UTC: p95 543ms2026-10-10 UTC: p95 503ms2026-10-11 UTC: p95 591ms2026-10-12 UTC: p95 588ms2026-10-13 UTC: p95 525ms2026-10-14 UTC: p95 272ms2026-10-15 UTC: p95 275ms2026-10-16 UTC: p95 762ms2026-10-17 UTC: p95 901ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 540ms2026-10-23 UTC: p95 839ms2026-10-24 UTC: p95 996ms2026-10-25 UTC: p95 970ms2026-10-26 UTC: p95 904ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 771ms2026-10-30 UTC: p95 971ms2026-10-31 UTC: p95 938ms2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
UK
630msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 204ms2026-10-08 UTC: p95 276ms2026-10-09 UTC: p95 251ms2026-10-10 UTC: p95 288ms2026-10-11 UTC: p95 261ms2026-10-12 UTC: p95 385ms2026-10-13 UTC: p95 392ms2026-10-14 UTC: p95 343ms2026-10-15 UTC: p95 269ms2026-10-16 UTC: p95 254ms2026-10-17 UTC: p95 855ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 284ms2026-10-24 UTC: p95 279ms2026-10-25 UTC: p95 297ms2026-10-26 UTC: p95 291ms2026-10-27 UTC: p95 502ms2026-10-28 UTC: p95 615ms2026-10-29 UTC: p95 567ms2026-10-30 UTC: p95 533ms2026-10-31 UTC: p95 404ms2026-11-01 UTC: p95 540ms2026-11-02 UTC: p95 613ms2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 630ms
Oct 7Oct 21Nov 5
Southeast Asia
2.7sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 712ms2026-10-10 UTC: p95 688ms2026-10-11 UTC: p95 700ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 963ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 781ms2026-10-25 UTC: p95 779ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 855ms2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
Australia
1.8sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 922ms2026-10-08 UTC: p95 956ms2026-10-09 UTC: p95 743ms2026-10-10 UTC: p95 889ms2026-10-11 UTC: p95 846ms2026-10-12 UTC: p95 568ms2026-10-13 UTC: p95 644ms2026-10-14 UTC: p95 679ms2026-10-15 UTC: p95 687ms2026-10-16 UTC: p95 878ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 822ms2026-10-23 UTC: p95 864ms2026-10-24 UTC: p95 937ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
South America
2.1sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 946ms2026-10-09 UTC: p95 648ms2026-10-10 UTC: p95 872ms2026-10-11 UTC: p95 747ms2026-10-12 UTC: p95 656ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 895ms2026-10-16 UTC: p95 591ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 762ms2026-10-23 UTC: p95 7.7s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 949ms2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Firebase

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Firebase. It cannot diagnose Firebase's own systems.

Email me when Firebase reports an incident on its status page, and again when it reports it resolved.

Get an email when Firebase reports an incident

Email me when Firebase reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Firebase's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1458msstatus code: 401checked: Nov 5, 2026, 2:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Firebase normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 548msstatus code: 401checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Firebase normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 610msstatus code: 401checked: Nov 5, 2026, 2:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Firebase normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 623msstatus code: 401checked: Nov 5, 2026, 2:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Firebase normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1553msstatus code: 401checked: Nov 5, 2026, 2:17 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Firebase normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 744msstatus code: 401checked: Nov 5, 2026, 2:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Firebase normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1014msstatus code: 401checked: Nov 5, 2026, 2:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Firebase normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1220msstatus code: 401checked: Nov 5, 2026, 2:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Firebase normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1399msstatus code: 401checked: Nov 5, 2026, 2:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Firebase normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1861msstatus code: 401checked: Nov 5, 2026, 2:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Firebase normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Firebase, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Firebase yet, which is not evidence that nothing is wrong.

Recent probe events

We are tracking a networking issue that may affect a significant part of the fleet. Devices may be unable to connect to backends that support IPv4 only (IPv6 and dual support are not affected)., 33h 6mdeclared on their status page2026-10-22
Partial performance degradation for RTDB users in us-central1 from 6 AM to 8:30 PM PT., 14h 25mdeclared on their status page2026-10-21
Reduced overall capacity for Android, iOS and Arm Emulator devices from 5 PM to 10 PM PT., 8hdeclared on their status page2026-10-17
Reduced overall capacity for Android, iOS and Arm Emulator devices from 2 PM to 8 PM PT., 5h 20mdeclared on their status page2026-10-15
Drop in ARM emulator capacity due to network disruption to datacenter, 2h 17mdeclared on their status page2026-10-13
Firebase Hosting projects presenting intermittent "Bandwidth Quota Exceeded" errors or failing deployments with quota errors., 33h 36mdeclared on their status page2026-10-07
Firebase Test Lab is experiencing availability issues with ARM emulator devices., 13h 30mdeclared on their status page2026-09-22
Firebase App Hosting experiencing issues actuating Cloud Run, 2h 6mdeclared on their status page2026-09-22

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Firebase since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Firebase covering any window you pick, with our check readings and Firebase's own claim at the time, side by side.

Full check history for Firebase: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Firebase uptime by RealUptime's checksLive, from this page's own readings.
[![Firebase uptime by RealUptime's checks](https://realuptime.io/outages/firebase/badge.svg?days=30)](https://realuptime.io/outages/firebase)
<a href="https://realuptime.io/outages/firebase"><img src="https://realuptime.io/outages/firebase/badge.svg?days=30" alt="Firebase uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Firebase down?", https://realuptime.io/outages/firebase. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://firebase.googleapis.com/v1beta1/availableProjects
secondary
https://status.firebase.google.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: firebase.googleapis.com

RealUptime is not affiliated with Firebase; the name identifies what we checked, and nothing here speaks for Firebase's own team. We send a single web request to Firebase from 10 regions on our own schedule and time the response. We do not see inside Firebase's systems, do not use an account or real transaction, and are not the same signal Firebase's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Firebase is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.