Firebase Status Dashboard

This page provides status information on the services that are part of Firebase. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://firebase.google.com/.

NOTE

For incidents related to Cloud Functions, Cloud Firestore and Cloud Storage, please see Cloud Status Dashboard. And for incidents related to Google Analytics, please see Ads Status Dashboard.


Incident affecting Console

Issues with enabling Cloud Firestore via Firebase console on new projects

Incident began at 2020-02-05 14:14 and ended at 2020-02-05 15:56 (all times are US/Pacific).

Date Time Description
5 Feb 2020 15:56 PST

The issue with Firebase Console has been resolved for all affected users as of Wednesday, 2020-02-05 15:56 US/Pacific.

We thank you for your patience while we've worked on resolving the issue.

5 Feb 2020 14:34 PST

Description: We are experiencing an issue with enabling Cloud Firestore via Firebase Console, beginning at Wednesday, 2020-02-05 10:21 US/Pacific.

Our Engineering team is working on deploying a fix. The current ETA to deploy the fix is ~ 2 hours.

We will provide an update by Wednesday, 2020-02-05 16:30 US/Pacific with current details.

Diagnosis: Affected customers may see a 'host not found' error when attempting to enable Clould Firestore using the Firebase Console. This affects customers trying to enable Cloud Firestore for new projects. Existing projects are unaffected.

Workaround: Customers may use Cloud Console as a workaround.

5 Feb 2020 14:22 PST

Description: We are experiencing an issue with enabling Cloud Firestore via Firestore Console, beginning at Wednesday, 2020-02-05 12:56 US/Pacific.

Our engineering team has identified the root cause and is working to mitigate.

We will provide an update by Wednesday, 2020-02-05 15:26 US/Pacific with current details.

We apologize to all who are affected by the disruption.