Cloud Messaging Incident #17006
Issue with sending notifications using the Firebase Notifications console
Incident began at 2017-07-18 08:25 and ended at 2017-07-24 08:22 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jul 24, 2017 | 08:22 | The issue has been resolved for all affected users as of 08:22 AM US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
|
| Jul 24, 2017 | 07:20 | We are still investigating the issue with the Firebase Notifications console. We will provide another status update by 08:00 US/Pacific with current details. |
|
| Jul 24, 2017 | 05:08 | We are experiencing an issue with sending notifications using the Firebase Notifications console beginning at Tuesday, 2017-07-18 08:25 US/Pacific. Users can check whether their messages are affected by saving a message as draft and re-opening it before sending. The problem is associated with saving data from the console. If the desired filter conditions have been saved then the correct messages should be sent out. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We will provide an update by 05:25 US/Pacific with current details. |