Cloud Messaging Incident #19005
The Firebase Cloud Messaging service is experiencing an issue with Topic Messaging.
Incident began at 2019-05-15 13:52 and ended at 2019-05-27 23:22 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| May 27, 2019 | 23:22 | The issue with Firebase Cloud Messaging, where some topics became dissociated from their subscription base, has been resolved for all affected users as of Monday, 2019-05-27 23:18 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
|
| May 24, 2019 | 13:52 | The issue in which topics became dissociated from their subscription in Firebase Cloud Messaging has been resolved for some subscriptions. We expect a full resolution in the near future. We will provide another status update by Tuesday, 2019-05-28 14:00 US/Pacific with current details. |
|
| May 22, 2019 | 11:52 | Our Engineering Team is currently testing a recovery script to re-associate topics with their subscriber base. We will provide another status update by Friday, 2019-05-24 14:00 US/Pacific with current details. |
|
| May 15, 2019 | 14:07 | Firebase Cloud Messaging is experiencing an issue with Topic Messaging where approx. 5% of topics became dissociated from their subscription base. Messages sent through the Firebase console using segments may also be affected. The issue was mitigated on May 10th, and our Engineers are working to re-associate topics with their subscriber base and as of today have progressed into the testing phase. No customer data was lost, but remediation is expected to complete by Friday, 2019-05-24 . We will provide another status update by Friday, 2019-05-24 14:00 US/Pacific with current details. |
|
| May 15, 2019 | 13:52 | The Firebase Cloud Messaging service is experiencing an issue with Topic Messaging. |