Imgix reported this minor-impact incident on its official status page on May 1, 2023, 14:20 UTC. It was resolved after 1h 15m.
Right now Imgix is operational. Live Imgix status →
# What happened On May 1st, 2023, between the hours of 08:23 UTC and 15:08 UTC, imgix experienced intermittent errors affecting a small percentage of non-cached renders. # How were customers impacted? During the affected period, a small percentage of requests to the Rendering API returned a `502` or `503` error for non-cached requests. Errors slowly and gradually increased, with <.5% of requests returning an error at the height of the incident. # What went wrong during the incident? Our upstream provider experienced communication issues between CDN POPs, causing intermittent `502`/`503` responses in a small percentage of requests to our Rendering API. The increase in errors was so minor that it did not meet our monitoring thresholds for triggering alerts. One of our engineers observed a slow increase in errors and alerted other team members to a potential issue with our service. After tracing the issue to our upstream provider, we pushed a patch to mitigate intermittent connecti
This incident has been resolved.
A fix has been implemented, and we are monitoring the results.
The issue has been identified, and a fix is being implemented.
We are currently investigating reports of intermittent 5xx errors causing some images to initially return a 5xx error.
Our 5-minute checks didn't record a change in Imgix's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Imgix reported 3 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 51 min. See Imgix's uptime and incident history