Firebase Status Dashboard
NOTE
For incidents related to Cloud Functions, Cloud Firestore and Cloud Storage, please see Cloud Status Dashboard. And for incidents related to Google Analytics, please see Ads Status Dashboard.
Incident affecting AB Testing (BETA)
Firebase Remote Config Experiments with A/B Testing not getting experimental variants
Incident began at 2019-12-13 10:00 and ended at 2019-12-13 13:42 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 13 Dec 2019 | 13:44 PST | The issue with Firebase Remote Config Experiments with A/B Testing has been resolved for all affected users as of Friday, 2019-12-13 13:42 US/Pacific. We thank you for your patience while we've worked on resolving the issue. |
| 13 Dec 2019 | 13:36 PST | We believe the issue with Firebase Remote Config Experiments with A/B Testing has been partially resolved by the rollback. Our engineering team is continuing to monitor the rollback and system metrics to ensure the service returns to normal operation We will provide an update by Friday, 2019-12-13 14:30 US/Pacific with current details. |
| 13 Dec 2019 | 13:13 PST | We are experiencing an issue with Firebase A/B Testing’s integration with Firebase Remote Config, beginning at Friday, 2019-12-13 10:00 US/Pacific. As a result, there might be an extended delay in the propagation of experiments to devices. Our engineering team has a rollback in progress which we believe will mitigate this issue. We will provide an update by Friday, 2019-12-13 14:00 US/Pacific with current details. Self-Diagnosis: Firebase Remote Config that use A/B testing only get default parameter, no experiment data being collected. Workaround: none at this time. |
- All times are US/Pacific