Skip to content

Outage tracker / Firebase

Is Firebase down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Firebase from all 10 regions we check.

As of Oct 5, 2026, 8:13 PM UTC, Firebase answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Firebase (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:13 PM UTC
US-East273 msOperational
US-West379 msOperational
Europe241 msOperational
Asia-Pacific244 msOperational
US-Central267 msOperational
Canada327 msOperational
UK64 msOperational
Southeast Asia820 msOperational
Australia667 msOperational
South America922 msOperational
their status pagetheir claim, not our reading

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

from Firebase's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and Firebase's own status page agree: both show Firebase as reachable 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
520msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 347ms2026-09-07 UTC: p95 343ms2026-09-08 UTC: p95 360ms2026-09-09 UTC: p95 375ms2026-09-10 UTC: p95 356ms2026-09-11 UTC: p95 896ms2026-09-12 UTC: p95 758ms2026-09-13 UTC: p95 799ms2026-09-14 UTC: p95 750ms2026-09-15 UTC: p95 698ms2026-09-16 UTC: p95 756ms2026-09-17 UTC: p95 232ms2026-09-18 UTC: p95 310ms2026-09-19 UTC: p95 255ms2026-09-20 UTC: p95 464ms2026-09-21 UTC: p95 454ms2026-09-22 UTC: p95 539ms2026-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 520ms
Sep 6Sep 20Oct 5
US-West
529msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 272ms2026-09-07 UTC: p95 299ms2026-09-08 UTC: p95 286ms2026-09-09 UTC: p95 443ms2026-09-10 UTC: p95 418ms2026-09-11 UTC: p95 392ms2026-09-12 UTC: p95 417ms2026-09-13 UTC: p95 328ms2026-09-14 UTC: p95 277ms2026-09-15 UTC: p95 302ms2026-09-16 UTC: p95 595ms2026-09-17 UTC: p95 201ms2026-09-18 UTC: p95 229ms2026-09-19 UTC: p95 215ms2026-09-20 UTC: p95 263ms2026-09-21 UTC: p95 559ms2026-09-22 UTC: p95 890ms2026-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 529ms
Sep 6Sep 20Oct 5
Europe
298msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 283ms2026-09-07 UTC: p95 115ms2026-09-08 UTC: p95 106ms2026-09-09 UTC: p95 357ms2026-09-10 UTC: p95 404ms2026-09-11 UTC: p95 358ms2026-09-12 UTC: p95 297ms2026-09-13 UTC: p95 394ms2026-09-14 UTC: p95 203ms2026-09-15 UTC: p95 188ms2026-09-16 UTC: p95 283ms2026-09-17 UTC: p95 329ms2026-09-18 UTC: p95 328ms2026-09-19 UTC: p95 316ms2026-09-20 UTC: p95 299ms2026-09-21 UTC: p95 331ms2026-09-22 UTC: p95 684ms2026-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 298ms
Sep 6Sep 20Oct 5
Asia-Pacific
574msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 472ms2026-09-07 UTC: p95 572ms2026-09-08 UTC: p95 433ms2026-09-09 UTC: p95 474ms2026-09-10 UTC: p95 422ms2026-09-11 UTC: p95 666ms2026-09-12 UTC: p95 569ms2026-09-13 UTC: p95 534ms2026-09-14 UTC: p95 587ms2026-09-15 UTC: p95 577ms2026-09-16 UTC: p95 577ms2026-09-17 UTC: p95 617ms2026-09-18 UTC: p95 593ms2026-09-19 UTC: p95 608ms2026-09-20 UTC: p95 684ms2026-09-21 UTC: p95 607ms2026-09-22 UTC: p95 162ms2026-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 574ms
Sep 6Sep 20Oct 5
US-Central
527msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 493ms2026-09-07 UTC: p95 584ms2026-09-08 UTC: p95 490ms2026-09-09 UTC: p95 442ms2026-09-10 UTC: p95 347ms2026-09-11 UTC: p95 345ms2026-09-12 UTC: p95 362ms2026-09-13 UTC: p95 369ms2026-09-14 UTC: p95 344ms2026-09-15 UTC: p95 362ms2026-09-16 UTC: p95 265ms2026-09-17 UTC: p95 229ms2026-09-18 UTC: p95 241ms2026-09-19 UTC: p95 229ms2026-09-20 UTC: p95 190ms2026-09-21 UTC: p95 251ms2026-09-22 UTC: p95 340ms2026-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 527ms
Sep 6Sep 20Oct 5
Canada
422msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 497ms2026-09-07 UTC: p95 596ms2026-09-08 UTC: p95 495ms2026-09-09 UTC: p95 529ms2026-09-10 UTC: p95 714ms2026-09-11 UTC: p95 788ms2026-09-12 UTC: p95 326ms2026-09-13 UTC: p95 395ms2026-09-14 UTC: p95 451ms2026-09-15 UTC: p95 501ms2026-09-16 UTC: p95 449ms2026-09-17 UTC: p95 241ms2026-09-18 UTC: p95 253ms2026-09-19 UTC: p95 240ms2026-09-20 UTC: p95 236ms2026-09-21 UTC: p95 826ms2026-09-22 UTC: p95 851ms2026-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 422ms
Sep 6Sep 20Oct 5
UK
201msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 249ms2026-09-07 UTC: p95 347ms2026-09-08 UTC: p95 494ms2026-09-09 UTC: p95 687ms2026-09-10 UTC: p95 676ms2026-09-11 UTC: p95 658ms2026-09-12 UTC: p95 182ms2026-09-13 UTC: p95 148ms2026-09-14 UTC: p95 679ms2026-09-15 UTC: p95 178ms2026-09-16 UTC: p95 694ms2026-09-17 UTC: p95 471ms2026-09-18 UTC: p95 404ms2026-09-19 UTC: p95 352ms2026-09-20 UTC: p95 330ms2026-09-21 UTC: p95 535ms2026-09-22 UTC: p95 595ms2026-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 201ms
Sep 6Sep 20Oct 5
Southeast Asia
969msp95 · 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-06 UTC: p95 824ms2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 945ms2026-09-09 UTC: p95 891ms2026-09-10 UTC: p95 817ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 745ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 720ms2026-09-15 UTC: p95 775ms2026-09-16 UTC: p95 608ms2026-09-17 UTC: p95 937ms2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.7s2026-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 969ms
Sep 6Sep 20Oct 5
Australia
981msp95 · 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-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 2.1s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 938ms2026-09-18 UTC: p95 966ms2026-09-19 UTC: p95 896ms2026-09-20 UTC: p95 710ms2026-09-21 UTC: p95 947ms2026-09-22 UTC: p95 842ms2026-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 981ms
Sep 6Sep 20Oct 5
South America
974msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 928ms2026-09-10 UTC: p95 658ms2026-09-11 UTC: p95 863ms2026-09-12 UTC: p95 798ms2026-09-13 UTC: p95 762ms2026-09-14 UTC: p95 733ms2026-09-15 UTC: p95 740ms2026-09-16 UTC: p95 685ms2026-09-17 UTC: p95 343ms2026-09-18 UTC: p95 342ms2026-09-19 UTC: p95 353ms2026-09-20 UTC: p95 351ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-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 974ms
Sep 6Sep 20Oct 5

Is it Firebase, or is it you?

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.

Get an email when we see Firebase go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Firebase, and again when they can reach it again. That is our own measurement from ten regions, not Firebase's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 273msstatus code: 401checked: Oct 5, 2026, 8:10 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
      Operationallatency: 379msstatus code: 401checked: Oct 5, 2026, 8:13 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
      Operationallatency: 267msstatus code: 401checked: Oct 5, 2026, 8:07 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
      Operationallatency: 327msstatus code: 401checked: Oct 5, 2026, 8:07 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
    Operationallatency: 922msstatus code: 401checked: Oct 5, 2026, 8:12 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 241msstatus code: 401checked: Oct 5, 2026, 8:06 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
      Operationallatency: 64msstatus code: 401checked: Oct 5, 2026, 8:02 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 244msstatus code: 401checked: Oct 5, 2026, 8:08 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
      Operationallatency: 820msstatus code: 401checked: Oct 5, 2026, 7:55 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
      Operationallatency: 667msstatus code: 401checked: Oct 5, 2026, 8:00 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 outages

No outages on record yet for Firebase.

measured 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 measurements and Firebase's own claim at the time, side by side.

Full availability history for Firebase: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Firebase uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Firebase's SLA implies, from our measurement

At or above your target

We measured none of downtime for Firebase over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Firebase's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://firebase.googleapis.com/v1beta1/availableProjects
secondary
https://status.firebase.google.com/
RealUptime is not affiliated with Firebase; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.