imgix: Elevated erroneous 404 response codes impacting some S3 sources
Timeline of updates
- 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.
From imgix’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.imgix.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by imgix, started 2017-07-19 04:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated erroneous 404 response codes impacting some S3 sources
- Vendor
- imgix
- Date
- URL
- https://rewindex.com/company/imgix/incidents/fbz8shkb8kvx
imgix profileRecent imgix incidentsAll outages on July 19, 2017imgix in July 2017MarkdownJSON