Cloud Messaging Incident #17005
FCM Send requests are returning 500
Incident began at 2017-05-16 05:30 and ended at 2017-05-16 16:10 (all times are US/Pacific).
|May 16, 2017||20:21||
The issue with FCM send requests returning 500 status code should have been resolved for all affected users as of 04:10 PM US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence.
|May 16, 2017||14:24||
This outage is affecting requests that use legacy server keys. We are investigating the issue and will post an update here soon. Meanwhile, users who are significantly impacted can update their request to use the new server key found in Firebase console, Project Settings > Cloud Messaging section.
|May 16, 2017||13:25||
We are experiencing an issue with Firebase Cloud Messaging where some of the send requests are returning a response with a 500 status code. For everyone who is affected, we apologize for any inconvenience you may be experiencing. We are investigating the root cause and will post an update by 02:00 PM PST