Increased errors for new render requests (Rendering & Legacy video APIs)
Resolved
This incident has been resolved.
Jun 4, 2:44 PMResolved Jun 4, 4:54 PMMajorRendering Infrastructure
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Visual media transformation and optimization with intelligent caching for faster engagement.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 1h ago
88
Components
0
Active incidents
0
Maintenance
33.33%
90d uptime
Increased errors for new render requests (Rendering & Legacy video APIs)
Jun 4, 2:44 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 88 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Content Delivery Network | Operational | Group | Not recorded |
DNS | Operational | Group | Not recorded |
Storage Backends | Operational | Group | Not recorded |
Content Delivery Network | Operational | Component | Not recorded |
Google Cloud Storage | Operational | Component | Not recorded |
Rendering Infrastructure | Operational | Component | Not recorded |
Auckland (AKL) | Operational | Component | Not recorded |
Google Cloud DNS | Operational | Component | Not recorded |
Web Administration Tools | Operational | Component | Not recorded |
s3-ap-northeast-1 | Operational | Component | Not recorded |
API Service | Operational | Component | Not recorded |
Brisbane (BNE) | Operational | Component | Not recorded |
s3-ap-northeast-2 | Operational | Component | Not recorded |
Hong Kong (HKG) | Operational | Component | Not recorded |
Sandbox Tool for building and editing imgix URLs | Operational | Component | Not recorded |
s3-ap-southeast-1 | Operational | Component | Not recorded |
Osaka (ITM) | Operational | Component | Not recorded |
s3-ap-southeast-2 | Operational | Component | Not recorded |
Melbourne (MEL) | Operational | Component | Not recorded |
s3-ca-central-1 | Operational | Component | Not recorded |
Tokyo (NRT) | Operational | Component | Not recorded |
s3-eu-central-1 | Operational | Component | Not recorded |
Perth (PER) | Operational | Component | Not recorded |
Purging | Operational | Component | Not recorded |
s3-eu-west-1 | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Imgix is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
33.33%
Known uptime
3 known history days
88
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
24
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
API Service
Operational
Amsterdam (AMS)
Operational
Ashburn (BWI)
Operational
Ashburn (DCA)
Operational
Ashburn (IAD)
Operational
1
operational days
0
degraded days
2
outage days
0
maintenance days
87
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
# 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
The backfill for the CDN and Error Log reports has been completed. You should now be able to download the reports from the Dashboard or via the API as usual.
Purge requests were not executed between 2025-11-12 23:00 UTC and 2025-11-13 05:00 UTC. The issue has been mitigated, and purge functionality has been fully restored. All purge requests that failed during the impact window are being automatically retried.
# **Summary** Between October 21 and October 29, customers in Europe experienced 3 separate periods of increased latency for rendering requests. In a small number of cases, requests temporarily failed with โ429 โ concurrency limit reachedโ responses. # **What Went Wrong** The incident was traced to a GPU scaling issue from one of our upstream infrastructure providers. This led to temporary slowdowns and under higher-than-usual load. ### **Timeline** * **October 21:** Increased rendering latency in EU region, self-resolved. Investigation traced issue to GPU scaling in upstream infrastructure. Mitigation prepared. * **October 27:** Issue recurred. Manual mitigation deployed to stabilize rendering and automate future handling. * **October 29:** Latency alert triggered again. Previous fix mitigates impact, but latency becomes intermittent; additional configuration changes implemented to fully restore service and prevent recurrence. # What we will do to prevent this in the future While the new configurations will prevents recurring incidents, we are making further improvements to rendering resiliency and recovery speed: * Added more GPU hardware types to reduce the risk of scaling delays during peak demand. * Testing and evaluating additional hardware configurations to improve resiliency. * Finalizing fine-tuning of current configurations and exploring cross-regional load-balancing capabilities to further strengthen reliability. * Adjusted alerting thresholds to provide earlier notification of emerging issues.
This incident has been resolved.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance for Background Removals has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Imgix status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.imgix.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
