Hosting Incident #19007
Firebase Hosting is currently experiencing an issue where some requests for static content may be incorrectly returning HTTP 404 errors.
Incident began at 2019-04-11 15:44 and ended at 2019-04-11 16:24 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Apr 12, 2019 | 12:12 | A small percentage of our origin serving infrastructure was inadvertently reverted to an older version, which began serving spurious "Site not Found" pages. A small percentage of overall traffic was being served by affected origins, but because erroneous responses were cached, the overall error rate compounded during the 30 minute incident. Once identified, traffic to the problematic origins was drained and the CDN was purged. |
|
| Apr 11, 2019 | 16:42 | The issue with Firebase Hosting incorrectly returning HTTP 404 ("Not Found") for some static content requests has been resolved for all affected users as of Thursday, 2019-04-11 16:24 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 11, 2019 | 16:29 | Mitigation work is currently underway by our Engineering Team. We will provide another status update by Thursday, 2019-04-11 16:50 US/Pacific with current details. |
|
| Apr 11, 2019 | 16:29 | Firebase Hosting is currently experiencing an issue where some requests for static content may be incorrectly returning HTTP 404 errors. |