Service Health
Incident affecting Cloud Firestore
Users will not receive alerts on Firebase console.
Incident began at 2022-01-16 00:49 and ended at 2022-01-16 02:10 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 16 Jan 2022 | 02:10 PST | The issue with Firebase Console is believed to be affecting a very small number of customers and our Engineering Team is working on it. 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. We thank you for your patience while we're working on resolving the issue. |
| 16 Jan 2022 | 02:07 PST | Summary: Users will not receive alerts on Firebase console. Description: We believe the issue with Firebase Console is mitigated. Alerts may be delayed by up to 30 minutes but are still being processed. We do not have an ETA for full resolution at this point. We will provide an update by Sunday, 2022-01-16 04:00 US/Pacific with current details. Diagnosis: Users will not receive alerts on Firebase console. Workaround: None at this time. |
| 16 Jan 2022 | 01:27 PST | Summary: Users will not receive alerts on Firebase console. Description: We are experiencing an issue with Firebase Console.Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2022-01-16 04:30 US/Pacific with current details. Diagnosis: Users will not receive alerts on Firebase console. Workaround: None at this time. |
| 16 Jan 2022 | 01:26 PST | Summary: Users will not receive alerts on Firebase console. Description: We are experiencing an issue with Firebase Console.Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2022-01-16 04:30 US/Pacific with current details. Diagnosis: Users will not receive alerts on Firebase console. Workaround: None at this time. |
| 16 Jan 2022 | 00:49 PST | Summary: Users will not receive alerts on Firebase console. Description: We've received a report of an issue with Firebase Console as of Sunday, 2022-01-16 00:29 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2022-01-16 01:25 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: None at this time. Workaround: None at this time. |
- All times are US/Pacific