Elevated erroneous 404 response codes impacting some S3 sources

Incident Report for imgix

Resolved

Approximately Jul 18 2017 - 18:35 GMT, an engineer performed a validated two stage deployment to imgix's object fetching service. This deployment was accidentally allowed to proceed to the second stage with one host left running the old code version. This caused a minimal increase in erroneous 404 response codes for newly fetched content from S3 sources, which was diagnosed at 02:45 GMT and verified resolved at 03:00 GMT.

Posted Jul 18, 2017 - 21:00 PDT