# imgix: Encoding Error for Web folder

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2024-02-26 17:41 UTC · Resolved: 2024-01-22 21:00 UTC · Duration: -50201 min
- Updates: 2
- [Vendor status page: https://stspg.io/lv70kd0ft813](https://stspg.io/lv70kd0ft813)
- [Company: imgix](https://rewindex.com/company/imgix.md)

## Timeline of updates

- **resolved** 2024-01-22 21:00 UTC: We have identified the issue and are currently applying a fix. The rendering service is not affected.
- **postmortem** 2024-02-26 17:42 UTC: \# Postmortem \# \*\*What happened?\*\* On January 22, 2024, 07:38 UTC, some Web Folder requests to the imgix service began to return a \`403\` response.  By 11:56 UTC, the issue had been completely resolved. \# \*\*How were customers impacted?\*\* Between 07:38 UTC and 11:36 UTC, several requests to web folder sources began to return a \`403\` error. This affected a small amount of assets \\(\<0.1%\\).  \# \*\*What went wrong during the incident?\*\* A service update caused an issue with web folders with directories using double slashes at the Origin URL \\(\`//\`\\). This update caused an encoding error, leading to \`403\` responses for Origins matching the double slash pattern. A fix was pushed to resolve this URL pattern, allowing us to fetch images from affected Origins. \# \*\*What will imgix do to prevent this in the future?\*\* We will update our tests to catch encoding issues in the future.


---
Canonical: https://rewindex.com/company/imgix/incidents/g4g3780hlrsv · Markdown: https://rewindex.com/company/imgix/incidents/g4g3780hlrsv.md · JSON: https://rewindex.com/api/v1/companies/imgix/incidents/g4g3780hlrsv · Generated 2026-10-20T00:52:15.484Z