Crashlytics Incident #19005
We've received a report of an issue with Firebase Crashlytics
Incident began at 2019-07-18 10:09 and ended at 2019-07-18 15:50 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jul 18, 2019 | 15:50 | The latency issue with Firebase Crashlytics has been resolved for all affected users as of Thursday, 2019-07-18 15:50 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. |
|
| Jul 18, 2019 | 14:48 | The latency for these crashes is decreasing and is further down to 30 minutes. We will provide another status update by Thursday, 2019-07-18 17:30 US/Pacific with current details. |
|
| Jul 18, 2019 | 13:40 | Mitigation work is still under way by our Engineering team and the latency of these crashes is down to 1.5 hours. We expect the latency to gradually reduce over the next few hours. We will provide another status update by Thursday, 2019-07-18 17:30 US/Pacific with current details. |
|
| Jul 18, 2019 | 12:21 | Our previous actions did not resolve the issue. We are pursuing alternative solutions. Affected customers may see a delay of up to 1.75 hours in seeing crashes. We will provide another status update by Thursday, 2019-07-18 13:30 US/Pacific with current details. |
|
| Jul 18, 2019 | 11:22 | Mitigation work is still underway by our Engineering Team and the delays are starting to recover. We will provide another status update by Thursday, 2019-07-18 12:30 US/Pacific with current details. |
|
| Jul 18, 2019 | 11:00 | The latency in crashes showing up in Firebase Crashlytics is reducing. We will provide another status update by Thursday, 2019-07-18 11:30 US/Pacific with current details. |
|
| Jul 18, 2019 | 10:22 | We are investigating latency with Firebase Crashlytics. Our Engineering Team is investigating possible causes. We will provide another status update by Thursday, 2019-07-18 11:00 US/Pacific with current details. |