# Uploading errors in Asset Manager

- Provider: [imgix](https://down.guide/imgix)
- Level: confirmed
- Impact: Degraded
- lasted 53m
- started 2026-01-12 13:53 UTC
- Web Administration Tools
- id: DWN-052720fd7d
- Official page: https://stspg.io/8z2lf40w4ndh

## Updates from imgix
### 2026-01-12 13:53 UTC: investigating
We are investigating an issue where Asset Manager returns errors for uploaded assets. Affected assets can still be served through the Rendering API but will not be visible in Asset Manager.
Customers using the legacy Long Form Video feature may also encounter video delivery errors.
We are investigating this issue.

### 2026-01-12 14:37 UTC: monitoring
We have identified the issue and deployed a fix that applies to newly uploaded assets.
We are continuing to investigate a solution to restore visibility for assets uploaded prior to the fix in Asset Manager.

### 2026-01-12 14:47 UTC: resolved
The uploading incident is resolved.
We will follow up with affected customers to restore visibility for previously uploaded assets.

### 2026-01-28 00:27 UTC: postmortem
# Summary
Between 2026-01-09 21:26 UTC and 2026-01-12 14:18 UTC, some asset uploads returned an upload failure error in Asset Manager despite the uploads completing successfully.
Additionally, legacy video customers experienced transcoding delays as a result of the incident.
# What Went Wrong
A production misconfiguration caused a validation step in the Asset Manager pipeline to fail.
As a result:
\* The legacy video encoding process did not initiate for uploaded videos
\* Assets did not appear in Asset Manager because they failed validation
While affected assets were still available at the origin and accessible via the Rendering and Video APIs, they did not appear in the Asset Manager UI and were not available through the legacy Long-Form Video API.
# What we will do to prevent this in the future
We have done the following things:
1. Added more alerting and patched logging gaps to catch the issue sooner
2. Fix a flaw in our build system that allowed a two-step deploy to get out of sync

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).