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 Realtime Database

Users may be unable to access their Firebase Realtime Database dashboard in the Console when using Reliance Jio networks.

Incident began at 2020-09-03 06:30 and ended at 2020-09-04 09:21 (all times are US/Pacific).

Date Time Description
4 Sep 2020 09:21 PDT

The issue with Firebase Realtime Database is believed to be affecting a very small number of customers and our Engineering Team is working on it. We have reached out to the affected ISP's which are now in progress of resolving the issue.

If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.

No further updates will be provided here.

We thank you for your patience while we're working on resolving the issue.

3 Sep 2020 14:43 PDT

Description: We are experiencing an intermittent issue with Firebase Realtime Database beginning on Thursday, 2020-09-03 at 10:30 US/Pacific.

It appears there is a network problem at one or more ISPs that prevents users on those networks for accessing the Firebase Realtime Database. The databases itself and users on other networks are not affected. At the moment this problem is confirmed for users on Reliance Jio networks.

We are seeing fewer reports of this issue and our engineering team is continuing to monitor the issue.

Symptoms: Users may be unable to access their database or see it in the Console.

A current workaround for the issue is by using another network/provider, or switching to a public DNS provider.

We will provide an update by Friday, 2020-09-04 13:00 US/Pacific with current details.

Diagnosis: Firebase Realtime Database Dashboard was not showing any data, rules nor usage information.

Workaround: A current workaround for the issue is by using another network/provider. Another workaround is to configure RTDB clients to use a public DNS resolver.

3 Sep 2020 11:57 PDT

Description: We are experiencing an intermittent issue with Firebase Realtime Database beginning on Thursday, 2020-09-03 at 10:30 US/Pacific.

It appears there is a network problem at one or more ISPs that prevents users on those networks for accessing the Firebase Realtime Database. The databases itself and users on other networks are not affected. At the moment this problem is confirmed for users on Reliance Jio networks.

Our engineering team continues to investigate the issue.

Symptoms: Users may be unable to access their database or see it in the Console.

A current workaround for the issue is by using another network/provider, or switching to a public DNS provider.

We will provide an update by Thursday, 2020-09-03 15:00 US/Pacific with current details.

Diagnosis: Firebase Realtime Database Dashboard was not showing any data, rules nor usage information.

Workaround: A current workaround for the issue is by using another network/provider. Another workaround is to configure RTDB clients to use a public DNS resolver.

3 Sep 2020 08:52 PDT

Description: We are experiencing an intermittent issue with Firebase Realtime Database beginning at Thursday, 2020-09-03 10:30 US/Pacific.

It appears there is a network problem at one or more ISPs that prevents users on those networks for accessing the Firebase Realtime Database. The databases itself and users on other networks are not affected. At the moment this problem is confirmed for users on Reliance Jio networks.

Our engineering team continues to investigate the issue.

Symptoms: Users may be unable to access their database or see it in the Console.

A current workaround for the issue is by using another network/provider, or switching to a public DNS provider.

We will provide an update by Thursday, 2020-09-03 12:00 US/Pacific with current details.

Diagnosis: Firebase Realtime Database Dashboard was not showing any data, rules nor usage information.

Workaround: A current workaround for the issue is by using another network/provider. Another workaround is to configure RTDB clients to use a public DNS resolver.

3 Sep 2020 07:13 PDT

Description: We are experiencing an intermittent issue with Firebase Realtime Database beginning at Thursday, 2020-09-03 10:30 US/Pacific.

It appears there is a network problem at one or more ISPs that prevents users on those networks for accessing the Firebase Realtime Database. The databases itself and users on other networks are not affected. At the moment this problem is confirmed for users on Reliance Jio networks.

Our engineering team continues to investigate the issue.

Symptoms: Users may be unable to access their database or see it in the Console.

A current workaround for the issue is by using another network/provider, or switching to a public DNS provider.

We will provide an update by Thursday, 2020-09-03 09:00 US/Pacific with current details.

Diagnosis: Firebase Realtime Database Dashboard was not showing any data, rules nor usage information.

Workaround: A current workaround for the issue is by using another network/provider. Another workaround is to configure RTDB clients to use a public DNS resolver.

3 Sep 2020 07:13 PDT

Description: We are experiencing an intermittent issue with Firebase Realtime Database beginning at Thursday, 2020-09-03 10:30 US/Pacific.

Symptoms: User unable to access their database or see it in the Console with Reliance Jio ISP

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2020-09-03 08:39 US/Pacific with current details.

Diagnosis: Firebase Realtime Database Dashboard was not showing any data, rules nor usage information.

Workaround: As a walk around customer can switch client to use a public DNS resolver, or by using another network provider.