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-10-22 20:50 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.

Partially degradedchecked 1 minute ago

Firebase is answering our probes, but running at least 7x its 7-day median from US-West. The rest of the regions we check answered at their usual speed.

As of Oct 22, 2026, 8:54 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 Oct 22, 2026, 8:54 PM UTC
US-East740 msChecks passing
US-West796 msDegraded
Europe562 msChecks passing
Asia-Pacific608 msChecks passing
US-Central175 msChecks passing
Canada137 msChecks passing
UK567 msChecks passing
Southeast Asia512 msChecks passing
Australia567 msChecks passing
South America278 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 Oct 22, 2026, 8:33 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-09-23 UTC: p95 451ms2026-09-24 UTC: p95 463ms2026-09-25 UTC: p95 422ms2026-09-26 UTC: p95 439ms2026-09-27 UTC: p95 474ms2026-09-28 UTC: p95 420ms2026-09-29 UTC: p95 492ms2026-09-30 UTC: p95 501ms2026-10-01 UTC: p95 500ms2026-10-02 UTC: p95 472ms2026-10-03 UTC: p95 457ms2026-10-04 UTC: p95 445ms2026-10-05 UTC: p95 532ms2026-10-06 UTC: p95 678ms2026-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.1s
Sep 23Oct 7Oct 22
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-09-23 UTC: p95 745ms2026-09-24 UTC: p95 668ms2026-09-25 UTC: p95 668ms2026-09-26 UTC: p95 530ms2026-09-27 UTC: p95 548ms2026-09-28 UTC: p95 539ms2026-09-29 UTC: p95 342ms2026-09-30 UTC: p95 341ms2026-10-01 UTC: p95 393ms2026-10-02 UTC: p95 355ms2026-10-03 UTC: p95 335ms2026-10-04 UTC: p95 354ms2026-10-05 UTC: p95 527ms2026-10-06 UTC: p95 522ms2026-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.3s
Sep 23Oct 7Oct 22
Europe
902msp95 · 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-09-23 UTC: p95 706ms2026-09-24 UTC: p95 719ms2026-09-25 UTC: p95 458ms2026-09-26 UTC: p95 312ms2026-09-27 UTC: p95 365ms2026-09-28 UTC: p95 338ms2026-09-29 UTC: p95 285ms2026-09-30 UTC: p95 313ms2026-10-01 UTC: p95 296ms2026-10-02 UTC: p95 272ms2026-10-03 UTC: p95 323ms2026-10-04 UTC: p95 286ms2026-10-05 UTC: p95 286ms2026-10-06 UTC: p95 327ms2026-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 902ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.3sp95 · 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-09-23 UTC: p95 729ms2026-09-24 UTC: p95 675ms2026-09-25 UTC: p95 773ms2026-09-26 UTC: p95 712ms2026-09-27 UTC: p95 784ms2026-09-28 UTC: p95 678ms2026-09-29 UTC: p95 847ms2026-09-30 UTC: p95 829ms2026-10-01 UTC: p95 573ms2026-10-02 UTC: p95 495ms2026-10-03 UTC: p95 591ms2026-10-04 UTC: p95 529ms2026-10-05 UTC: p95 572ms2026-10-06 UTC: p95 566ms2026-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.3s
Sep 23Oct 7Oct 22
US-Central
410msp95 · 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-09-23 UTC: p95 434ms2026-09-24 UTC: p95 453ms2026-09-25 UTC: p95 388ms2026-09-26 UTC: p95 345ms2026-09-27 UTC: p95 370ms2026-09-28 UTC: p95 329ms2026-09-29 UTC: p95 419ms2026-09-30 UTC: p95 417ms2026-10-01 UTC: p95 374ms2026-10-02 UTC: p95 304ms2026-10-03 UTC: p95 381ms2026-10-04 UTC: p95 380ms2026-10-05 UTC: p95 477ms2026-10-06 UTC: p95 502ms2026-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 410ms
Sep 23Oct 7Oct 22
Canada
561msp95 · 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-09-23 UTC: p95 376ms2026-09-24 UTC: p95 421ms2026-09-25 UTC: p95 355ms2026-09-26 UTC: p95 414ms2026-09-27 UTC: p95 232ms2026-09-28 UTC: p95 237ms2026-09-29 UTC: p95 509ms2026-09-30 UTC: p95 577ms2026-10-01 UTC: p95 526ms2026-10-02 UTC: p95 428ms2026-10-03 UTC: p95 470ms2026-10-04 UTC: p95 420ms2026-10-05 UTC: p95 434ms2026-10-06 UTC: p95 333ms2026-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 561ms
Sep 23Oct 7Oct 22
UK
1.2sp95 · 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-09-23 UTC: p95 430ms2026-09-24 UTC: p95 503ms2026-09-25 UTC: p95 484ms2026-09-26 UTC: p95 467ms2026-09-27 UTC: p95 237ms2026-09-28 UTC: p95 258ms2026-09-29 UTC: p95 262ms2026-09-30 UTC: p95 721ms2026-10-01 UTC: p95 434ms2026-10-02 UTC: p95 426ms2026-10-03 UTC: p95 382ms2026-10-04 UTC: p95 360ms2026-10-05 UTC: p95 195ms2026-10-06 UTC: p95 240ms2026-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.2s
Sep 23Oct 7Oct 22
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 965ms2026-10-05 UTC: p95 927ms2026-10-06 UTC: p95 1.2s2026-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.2s
Sep 23Oct 7Oct 22
Australia
817msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 983ms2026-09-24 UTC: p95 982ms2026-09-25 UTC: p95 910ms2026-09-26 UTC: p95 925ms2026-09-27 UTC: p95 852ms2026-09-28 UTC: p95 839ms2026-09-29 UTC: p95 858ms2026-09-30 UTC: p95 833ms2026-10-01 UTC: p95 893ms2026-10-02 UTC: p95 935ms2026-10-03 UTC: p95 954ms2026-10-04 UTC: p95 875ms2026-10-05 UTC: p95 962ms2026-10-06 UTC: p95 928ms2026-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 817ms
Sep 23Oct 7Oct 22
South America
772msp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 729ms2026-09-24 UTC: p95 866ms2026-09-25 UTC: p95 718ms2026-09-26 UTC: p95 552ms2026-09-27 UTC: p95 640ms2026-09-28 UTC: p95 559ms2026-09-29 UTC: p95 570ms2026-09-30 UTC: p95 561ms2026-10-01 UTC: p95 545ms2026-10-02 UTC: p95 533ms2026-10-03 UTC: p95 739ms2026-10-04 UTC: p95 801ms2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.1s2026-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 772ms
Sep 23Oct 7Oct 22

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
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 740msstatus code: 401checked: Oct 22, 2026, 8:54 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
      Degradedlatency: 796msstatus code: 401checked: Oct 22, 2026, 8:47 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: 175msstatus code: 401checked: Oct 22, 2026, 8:46 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: 137msstatus code: 401checked: Oct 22, 2026, 8:46 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: 278msstatus code: 401checked: Oct 22, 2026, 8:47 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: 562msstatus code: 401checked: Oct 22, 2026, 8:47 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: 567msstatus code: 401checked: Oct 22, 2026, 8:47 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: 608msstatus code: 401checked: Oct 22, 2026, 8:54 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: 512msstatus code: 401checked: Oct 22, 2026, 8:46 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: 567msstatus code: 401checked: Oct 22, 2026, 8:46 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

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
Firebase Hosting dataplane connectivity is in some regions., 17h 27mdeclared on their status page2026-09-21

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

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>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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.