Cloud Firestore Incident #18008
Cloud Firestore web clients experiencing internal errors
Incident began at 2018-10-30 12:11 and ended at 2018-10-30 18:12 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Oct 30, 2018 | 19:46 | The rollback has been completed. The issue should have been resolved for affected users as of 18:12 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
|
| Oct 30, 2018 | 17:47 | The rollback is still in progress and affected users may still encounter the issue. We will provide an update as soon as it is completed. |
|
| Oct 30, 2018 | 16:24 | The rollback is still in progress and affected users may still encounter the issue. We apologize for the confusion. We will provide another status update by Tuesday, 2018-10-30 17:30 US/Pacific with current details |
|
| Oct 30, 2018 | 14:49 | The issue with Cloud Firestore web clients experiencing internal errors has been resolved for all affected users. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
|
| Oct 30, 2018 | 13:24 | We are investigating an issue with Cloud Firestore. Affected customers may see INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set when performing get(), set() or update() operations on their applications. Our engineering team has identified an issue with the backend and is currently rolling back changes to mitigate the issue. We will provide another status update by Tuesday, 2018-10-30 15:00 US/Pacific with current details. |