Firebase Outage History

Firebase partial outage View live status →

There were 13 Firebase outages since February 26, 2026 totaling 1383h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.firebase.google.com

Major April 28, 2026

ARM devices delayed

Detected by Pingoru
Apr 28, 2026, 08:27 PM UTC
Resolved
Apr 30, 2026, 06:59 AM UTC
Duration
1d 10h
Affected: Test LabTest Lab (global)
Timeline · 2 updates
  1. investigating Apr 28, 2026, 08:29 PM UTC

    Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.

  2. resolved Apr 29, 2026, 07:53 AM UTC

    The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Critical April 9, 2026

Physical device tests are delayed and stuck pending

Detected by Pingoru
Apr 09, 2026, 04:59 PM UTC
Resolved
Apr 09, 2026, 09:00 PM UTC
Duration
4h 1m
Affected: Test LabTest Lab (global)
Timeline · 3 updates
  1. investigating Apr 09, 2026, 05:00 PM UTC

    We're investigating the issue and determining the cause

  2. investigating Apr 09, 2026, 05:12 PM UTC

    We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests

  3. resolved Apr 09, 2026, 08:57 PM UTC

    We believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue

Read the full incident report →

Major April 9, 2026

Incident affecting Firebase AI Logic

Detected by Pingoru
Apr 09, 2026, 12:01 PM UTC
Resolved
Apr 09, 2026, 10:00 PM UTC
Duration
9h 59m
Affected: Firebase AI LogicFirebase AI Logic (global)
Timeline · 2 updates
  1. investigating Apr 09, 2026, 06:09 PM UTC

    No updates so far

  2. resolved Apr 10, 2026, 12:09 AM UTC

    Problem appears to be mitigated and the error rates are back to normal level.

Read the full incident report →

Major March 31, 2026

Delays and elevated inconclusive rates in Test Lab ARM devices

Detected by Pingoru
Mar 31, 2026, 07:00 PM UTC
Resolved
Apr 01, 2026, 06:00 AM UTC
Duration
11h
Affected: Test LabTest Lab (global)
Timeline · 2 updates
  1. investigating Apr 01, 2026, 04:21 AM UTC

    Test Lab ARM devices are experiencing elevated failures rates and delays to test results.

  2. resolved Apr 01, 2026, 06:09 AM UTC

    This issue appears to be resolved now. Error rates are back to normal.

Read the full incident report →

Major March 23, 2026

Firebase Hosting is missing metrics and logs in Cloud Logging.

Detected by Pingoru
Mar 23, 2026, 09:46 PM UTC
Resolved
Mar 31, 2026, 11:30 AM UTC
Duration
7d 13h
Affected: HostingHosting (global)
Timeline · 3 updates
  1. investigating Mar 31, 2026, 01:34 AM UTC

    Firebase Hosting is aware of missing metrics and logs from Cloud Logging.

  2. investigating Mar 31, 2026, 01:35 AM UTC

    Firebase Hosting engineers are working on backfilling missing Cloud Logging entries from 2026-03-23 21:46 UTC to 2026-03-30 16:04 UTC. The ETA is about 11:30 UTC March 31 for that process to complete.

  3. resolved Mar 31, 2026, 03:32 PM UTC

    The logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.

Read the full incident report →

Major March 17, 2026

404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash

Detected by Pingoru
Mar 17, 2026, 07:00 AM UTC
Resolved
Mar 17, 2026, 02:10 PM UTC
Duration
7h 10m
Affected: Cloud MessagingCloud Messaging (global)
Timeline · 2 updates
  1. investigating Mar 20, 2026, 01:05 PM UTC

    A recent change is causing 404 errors for clients who send messages to a URL which includes a trailing slash (/v1/projects/my-project/messages:send/ vs /v1/projects/my-project/messages:send). We are in the process of rolling back this change. For clients that are impacted, removing the trailing slash from the send URL will immediately resolve the problem.

  2. resolved Mar 20, 2026, 02:40 PM UTC

    The rollback is complete - service is fully restored.

Read the full incident report →

Major March 10, 2026

Firebase Studio App Hosting deployment disruption

Detected by Pingoru
Mar 10, 2026, 05:51 PM UTC
Resolved
Mar 31, 2026, 07:00 AM UTC
Duration
20d 13h
Affected: Firebase StudioFirebase Studio (global)
Timeline · 2 updates
  1. investigating Mar 11, 2026, 05:59 PM UTC

    Investigating: We are aware of a service disruption affecting App Hosting deployments from Firebase Studio. Impact: Users are currently unable to publish apps with App Hosting from Firebase Studio. Action: Our engineers are currently working to identify the root cause and restore deployment functionality as quickly as possible. We will provide an update as soon as we can. Workaround: In the meantime, you can publish using the Firebase App Hosting console or the Firebase CLI. Learn more at https://firebase.google.com/docs/app-hosting/get-started .

  2. resolved Apr 02, 2026, 06:49 PM UTC

    This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.

Read the full incident report →

Critical March 10, 2026

We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

Detected by Pingoru
Mar 10, 2026, 02:51 PM UTC
Resolved
Mar 10, 2026, 04:43 PM UTC
Duration
1h 52m
Affected: CrashlyticsPerformance MonitoringCrashlytics (global)Performance Monitoring (global)
Timeline · 1 update
  1. resolved Mar 10, 2026, 03:59 PM UTC

    We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

Read the full incident report →

Major March 10, 2026

Firebase Crashlytics is currently experiencing delays exporting BigQuery

Detected by Pingoru
Mar 10, 2026, 01:52 PM UTC
Resolved
Mar 14, 2026, 10:46 AM UTC
Duration
3d 20h
Affected: CrashlyticsCrashlytics (global)
Timeline · 2 updates
  1. investigating Mar 13, 2026, 01:55 PM UTC

    Firebase Crashlytics is currently experiencing delays exporting data to BigQuery. Data from 03/09 and onwards have not been exported. We are currently investigating ways to expedite the export.

  2. resolved Mar 14, 2026, 10:47 AM UTC

    All BigQuery export jobs for Firebase Crashlytics have caught up.

Read the full incident report →

Major March 8, 2026

Minor Intermittent Latency Increases for Some Firebase Cloud Messaging Services

Detected by Pingoru
Mar 08, 2026, 06:05 PM UTC
Resolved
Mar 31, 2026, 07:00 AM UTC
Duration
22d 12h
Affected: Cloud MessagingCloud Messaging (global)
Timeline · 6 updates
  1. investigating Mar 13, 2026, 06:14 PM UTC

    We're aware of a problem with FCM affecting some users. We will provide an update by 13:00 PDT detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.

  2. investigating Mar 13, 2026, 07:56 PM UTC

    We are continuing to investigate this issue. We will provide an update by 18:00 PDT detailing when we expect to resolve the problem.

  3. investigating Mar 14, 2026, 02:58 AM UTC

    We are continuing to investigate this issue. We will provide updates in the next few days, but we believe the issue is quite minor and should not be a problem for most customers. Thank you for your patience.

  4. investigating Mar 16, 2026, 11:15 PM UTC

    We have pinpointed the issue and are actively working on a resolution; only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.

  5. investigating Mar 30, 2026, 02:14 PM UTC

    We are actively working on a resolution. Only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.

  6. resolved Apr 01, 2026, 05:23 PM UTC

    The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.

Read the full incident report →

Major March 5, 2026

Deploys from GitHub are failing in us-east5

Detected by Pingoru
Mar 05, 2026, 04:50 PM UTC
Resolved
Mar 05, 2026, 07:30 PM UTC
Duration
2h 40m
Affected: App HostingApp Hosting (global)
Timeline · 2 updates
  1. investigating Mar 05, 2026, 06:32 PM UTC

    We are investigating increased errors when connecting to GitHub in us-east5. This is believed to affect automatic and manual deploys from GitHub as well as updating commit statuses with GitHub checks. As a workaround, you may deploy from local source using the Firebase command line tools.

  2. resolved Mar 05, 2026, 08:23 PM UTC

    The issue has been resolved.

Read the full incident report →

Major February 26, 2026

Elevated errors and latency in europe-west4

Detected by Pingoru
Feb 26, 2026, 02:11 PM UTC
Resolved
Feb 26, 2026, 03:11 PM UTC
Duration
1h
Affected: App HostingApp Hosting (global)
Timeline · 1 update
  1. resolved Mar 02, 2026, 10:17 PM UTC

    For approximately 1 hour starting at 06:11 PST on February 26, 2026, Firebase App Hosting backends in europe-west4 were seeing elevated errors on un-cached content due to increased network congestion and elevated requests. The issue was resolved for all affected projects as of 07:10 PST. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

Read the full incident report →

Looking to track Firebase downtime and outages?

Pingoru polls Firebase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Firebase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Firebase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Firebase for free

5 free monitors · No credit card required