Crashlytics Incident #20004
Firebase Crashlytics is experiencing crash ingestion delay.
Incident began at 2020-07-10 04:43 and ended at 2020-07-13 09:08 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jul 13, 2020 | 09:08 | The issue with Firebase Crashlytics delays has been resolved for all affected users as of Monday, 2020-07-13 08:55:21 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|
| Jul 13, 2020 | 07:40 | Description: We believe the issue with Firebase Crashlytics delays is resolved. Android and iOS crashes are being processed again without delays, as a result of mitigation efforts. We will provide an update by Monday, 2020-07-13 09:30 US/Pacific with current details. Diagnosis: Affected customers may experience delayed crash reports ingestion. Workaround: None at this time. |
|
| Jul 11, 2020 | 07:40 | Description: We believe the issue with Firebase Crashlytics delays is partially resolved, but delays are still higher than normal, and iOS crashes are being sampled in order to minimize delays while mitigation efforts continue. We do not have an ETA for full resolution at this point. We will provide an update by Monday, 2020-07-13 08:00 US/Pacific with current details. Diagnosis: Affected customers may experience delayed crash reports ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 18:38 | Description: We believe the issue with Firebase Crashlytics delays is partially resolved, but delays are still higher than normal while mitigation efforts continue. We do not have an ETA for full resolution at this point. We will provide an update by Saturday, 2020-07-11 09:00 US/Pacific with current details. Diagnosis: Affected customers may experience delayed crash reports ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 17:58 | Description: We believe the issue with Firebase Crashlytics delays is partially resolved, but delays are still higher than normal while mitigation efforts continue. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2020-07-10 21:00 US/Pacific with current details. Diagnosis: Affected customers may experience delayed crash reports ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 14:59 | Description: We believe the issue with Firebase Crashlytics delays is partially resolved, but delays are still higher then normal while mitigation efforts continue. We do not have an ETA for full resolution at this point. We will provide an update by Friday, 2020-07-10 18:00 US/Pacific with current details. Diagnosis: Affected customers may experience delayed crash reports ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 12:55 | Description: Mitigation work is still underway by our engineering team. We will provide more information by Friday, 2020-07-10 15:00 US/Pacific. Diagnosis: Affected customers may experience delayed crash ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 10:15 | Description: Mitigation work is still underway by our engineering team. We will provide more information by Friday, 2020-07-10 12:45 US/Pacific. Diagnosis: Affected customers may experience delayed crash ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 07:28 | Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2020-07-10 10:30 US/Pacific. Diagnosis: Affected customers may experience delayed crash ingestion. Workaround: None at this time. |
|
| Jul 10, 2020 | 06:09 | Description: We are experiencing an issue with Firebase Crashlytics beginning at Friday, 2020-07-10 04:43:01 US/Pacific. Crashlytics is experiencing high crash volumes due to an issue with a popular iOS SDK. Crash processing is slower than usual on Android and iOS. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2020-07-10 07:30 US/Pacific with current details. We apologize to all who are affected by the disruption. |