imgix: Elevated 404 rates from S3 sources
Timeline of updates
- resolved
A recent deployment caused our object fetching service to update its S3 requirements, which caused a problem that affected a percentage of traffic specific to a few S3 locations. A fix has been deployed and we previously 404ing URLs are now resulting in 200 responses.
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: minor) posted by imgix, started 2017-07-19 14:16 UTC, resolved after 2.4 h, 1 update(s).
- Title
- Elevated 404 rates from S3 sources
- Vendor
- imgix
- Date
- URL
- https://rewindex.com/company/imgix/incidents/csltvnhq6fz0
imgix profileRecent imgix incidentsAll outages on July 19, 2017imgix in July 2017MarkdownJSON