There were 13 Firebase outages since February 26, 2026 totaling 1383h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.
The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're investigating the issue and determining the cause
We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests
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
No updates so far
Problem appears to be mitigated and the error rates are back to normal level.
Test Lab ARM devices are experiencing elevated failures rates and delays to test results.
This issue appears to be resolved now. Error rates are back to normal.
Services are functioning normally as of 2026-03-30 09:00 PDT
Firebase Hosting is aware of missing metrics and logs from Cloud Logging.
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.
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.
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.
The rollback is complete - service is fully restored.
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 .
This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.
We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.
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.
All BigQuery export jobs for Firebase Crashlytics have caught up.
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.
We are continuing to investigate this issue. We will provide an update by 18:00 PDT detailing when we expect to resolve the problem.
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.
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.
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.
The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.
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.
The issue has been resolved.
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.
Pingoru polls Firebase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required