Crashlytics Incident #20003
Firebase Crashlytics experienced an issue with crashes processing.
Incident began at 2020-05-06 16:55 and ended at 2020-05-08 12:14 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| May 08, 2020 | 12:14 | The issue with Firebase Crashlytics has been resolved for all affected users, and all crashes are now being processed without significant delay as of Friday, 2020-05-08 12:04 US/Pacific. We thank you for your patience while we're working on resolving the issue. |
|
| May 08, 2020 | 11:30 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashltyics is now processing 100% of crashes on all platforms. Crash processing is slightly slower than normal. We are in the process of fully restoring iOS traffic processing to normal. We will provide another update by Friday, 2020-05-08 13:15 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 08, 2020 | 11:29 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashltyics is now processing 100% of crashes on all platforms. Crash processing is slightly slower than normal. We are in the process of fully restoring iOS traffic processing to normal. We will provide another update by Friday, 2020-05-08 13:00 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 08, 2020 | 08:42 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashltyics is now processing 100% of crashes on all platforms. Crash processing is slightly slower than normal. We are in the process of fully restoring iOS traffic processing to normal. We will provide another update by Friday, 2020-05-08 11:30 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 08, 2020 | 08:25 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashlytics is now processing 50% of iOS Crashes due to an ongoing incident. We are in the process of fully restoring iOS traffic processing to normal. We will provide another update by Friday, 2020-05-08 09:30 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 08, 2020 | 06:51 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashlytics is now processing 50% of iOS Crashes due to an ongoing incident. We are in the process of fully restoring iOS traffic processing to normal. We will provide another update by Friday, 2020-05-08 08:30 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 07, 2020 | 15:11 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashlytics is now processing 40% of iOS Crashes due to an ongoing incident. We won't increase the percentage of traffic beyond 40% today. We are actively working to return processing to normal. We will provide another update by Friday, 2020-05-08 07:00 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 07, 2020 | 13:52 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashlytics iOS crash processing is currently accepting 20% of traffic due to an ongoing incident. Over the next hour, we'll try to ramp up processing to 40% of iOS crashes. We won't increase the percentage of traffic beyond 40% today. We are actively working to return processing to normal. We will provide another update by Friday, 2020-05-08 18:00 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 07, 2020 | 13:10 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. Crashlytics iOS crash processing is currently accepting 20% of traffic due to an ongoing incident. We are actively working to return processing to normal. We will provide another update by Thursday, 2020-05-07 15:00 US/Pacific Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 07, 2020 | 09:07 | Description: Due to a significant increase in crashes across the iOS ecosystem, caused by an issue with a popular iOS SDK, iOS crash processing in Firebase Crashlytics was disabled by Wednesday, 2020-05-06 04:00 PM US/Pacific. We are actively working to return processing to normal, and apologize for the inconvenience. We will provide more information by Thursday, 2020-05-07 13:00 US/Pacific. Diagnosis: Customers impacted by this will not see iOS crashes starting at Wednesday, 2020-05-06 04:00 PM US/Pacific on the dashboard. Workaround: None at this time. |
|
| May 07, 2020 | 07:34 | Description: Our engineering team is still working on mitigation. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2020-05-07 11:00 US/Pacific. Workaround: None at this time. |
|
| May 07, 2020 | 06:58 | Description: Our engineering team is still working on mitigation. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2020-05-07 08:00 US/Pacific. Workaround: None at this time. |
|
| May 06, 2020 | 21:16 | Description: Our engineering team is still working on mitigation. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2020-05-07 07:00 US/Pacific. Workaround: None at this time. |
|
| May 06, 2020 | 19:55 | Description: Crashes on the Android platform is recovered. The iOS part is still suspended. Mitigation work is still underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2020-05-06 22:00 US/Pacific. Workaround: None at this time. |
|
| May 06, 2020 | 18:56 | 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 Wednesday, 2020-05-06 21:00 US/Pacific. Workaround: None at this time. |
|
| May 06, 2020 | 18:00 | Description: We are experiencing an issue with Firebase Crashlytics. The crash processing is delayed for the Android and suspended for iOS. Symptoms: Crashes may not reflect in the dashboard. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2020-05-06 20:00 US/Pacific with current details. Workaround: None at this time. |