Skip to content
PulseWatchOUTAGE.INTEL
Firebase logo

Cloud Infrastructure

Is Firebase down right now?

NormalOfficial status last polled Oct 5, 2026 13:58 UTCfirebase.google.comOfficial status page

Google Firebase backend services

Are you on the Firebase team and see something inaccurate? Report it to us. We respond within one business day.

Is Firebase down right now?

No. Firebase has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 5, 2026 15:14 UTC

Normal

Firebase is operating normally

As of Oct 5, 2026 15:14 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 23, 2026 00:23 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Firebase.

4

Incident days

26

No recorded incident

15h 8m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Firebase. Hover a day for detail.

Sep 6Sep 11Sep 16Sep 21Sep 26Oct 101234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

4

Days with incidents

3 incidents

Busiest day

15h 8m

Recorded duration

Report volume

0 reports in last 24H

03:00 PM06:30 PM10:00 PM01:30 AM05:00 AM08:30 AM12:00 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Firebase: vendor-reported incident on September 22 (tracked 7h 28m)

Sep 22, 04:54 PM → Sep 23, 12:23 AM · 7h 28m · medium

Firebase reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 7h 28m, from Tue, 22 Sep 2026 16:54:56 GMT to Wed, 23 Sep 2026 00:23:31 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
7h 28m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 22, 04:54 PM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Sep 22, 04:54 PM

    Status updated: possible issue

  3. Sep 23, 12:23 AM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 04:54 PM

    Firebase reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

97.9%

90-day uptime

41.4%

Calculated from Firebase's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/22/2026, 4:54:56 PM · 7h 28m

04:54 PM12:23 AM
Detection9/22/2026, 4:54:56 PM · 12d ago

Detected — medium severity

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/22/2026, 4:50:46 AM · 1h 27m

04:50 AM06:18 AM
Detection9/22/2026, 4:50:46 AM · 13d ago

Detected — medium severity

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 7:50:35 PM · 4h 37m

07:50 PM12:28 AM
Detection9/21/2026, 7:50:35 PM · 13d ago

Detected — medium severity

Firebase: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Firebase: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/16/2026, 7:45:48 PM · 1h 32m

07:45 PM09:18 PM
Detection9/16/2026, 7:45:48 PM · 18d ago

Detected — medium severity

Firebase: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

Firebase incident correlated across 1 signal group: official/vendor.

8/29/2026, 5:15:11 AM · 3d 23h

05:15 AM04:58 AM
Detection8/29/2026, 5:15:11 AM · 1mo ago

Detected — medium severity

Firebase incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Firebase enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Official status page polled; no gradeable history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

firebase.google.com