Cloud Functions Incident #18022
Investigating an issue with Cloud Functions for Firebase
Incident began at 2018-04-21 05:05 and ended at 2018-04-21 09:04 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| May 09, 2018 | 10:54 | SUMMARY: On Saturday, April 21, 2018, users of Cloud Functions for Firebase experienced delays in their functions executions. We understand the pain that this caused developers who rely on Cloud Functions for Firebase for their back end infrastructure, and apologize to everyone who was affected by the incident. DETAILED DESCRIPTION OF IMPACT: During the incident, which lasted seven hours, about 10% of all functions executions were significantly delayed (up to five hours). ROOT CAUSE: A release in upstream Google infrastructure caused a degradation in Cloud Functions for Firebase performance. REMEDIATION AND PREVENTION: Oncall engineers found and patched the issue with the upstream Google infrastructure. To improve response time if a similar issue occurs in the future, engineers have improved monitoring tools for earlier alerting. |
|
| Apr 21, 2018 | 09:04 | The issue with triggers for Cloud Functions for Firebase has been resolved for all affected users as of 09:04 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. |
|
| Apr 21, 2018 | 07:44 | We are investigating an issue related to triggers for Cloud Functions for Firebase. We will provide more information as soon as possible. |