imgix: Elevated 500-level rates
Timeline of updates
- resolved
The situation is resolved. We encountered some bottlenecks in our service that caused a backlog in requests, resulting in an uptick of 500-level errors. An operator error also occurred while we worked to move traffic and reduce the errors. After the error was fixed, the backlog of requests came through and completed correctly.
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-02-02 20:58 UTC, resolved after 2.0 h, 1 update(s).
- Title
- Elevated 500-level rates
- Vendor
- imgix
- Date
- URL
- https://rewindex.com/company/imgix/incidents/k3kvpylc89fq
imgix profileRecent imgix incidentsAll outages on February 2, 2017imgix in February 2017MarkdownJSON