Am identificat o corelare cu un incident Google Cloud în curs de desfășurare, care raportează pierderi ridicate de pachete și erori pentru mai multe servicii.
Vom continua să monitorizăm ratele de eroare și să oferim actualizări suplimentare, deoarece Google Cloud partajează mai multe informații.
identified
Continuăm să monitorizăm ratele de eroare în timp ce investigăm potențiale opțiuni de eșec pentru acest incident.
identified
Impingem schimbarile pentru a redirectiona traficul si vedem rate de eroare imbunatatite in cadrul serviciului.
Vom continua să facem actualizări și să monitorizăm situația.
identified
Observăm rate de eroare îmbunătățite în cadrul serviciului.
Vom continua să monitorizăm situaţia.
monitoring
Ratele de eroare au revenit la normal.
Vom continua să monitorizăm serviciul.
resolved
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
Erori crescute pentru cererile de read
A început 1 septembrie 2026 la 15:30 UTC · 51m
OutageIncident major
Componente afectate
Rendering Infrastructure
identified
Am identificat o creștere a erorilor pentru noi cereri de redare din cauza unui incident în curs cu un furnizor din amonte.
identified
Am identificat o corelare cu un incident Google Cloud în curs de desfășurare, care raportează pierderi ridicate de pachete și erori pentru mai multe servicii.
Vom continua să monitorizăm ratele de eroare și să oferim actualizări suplimentare, deoarece Google Cloud partajează mai multe informații.
monitoring
Ratele de eroare au revenit la nivelurile normale.
Continuăm să monitorizăm situația în timp ce așteptăm o actualizare de la Google Cloud.
resolved
This incident has been resolved.
Traducere automată din actualizarea oficială a incidentului.
Increased errors for new render requests
A început 14 august 2026 la 04:53 UTC · 35m
IssuesIncident minor
Componente afectate
Rendering Infrastructure
identified
We are observing an increase in 5xx errors for new render requests, correlating with an ongoing Google Cloud incident.
We will continue to monitor error rates and provide further updates as Google Cloud shares more information.
monitoring
Error rates have returned to normal levels.
We are continuing to monitor the situation while awaiting an update from Google Cloud.
resolved
While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
Prelucrarea întârziată a cererilor de purjare
A început 25 iunie 2026 la 10:28 UTC · 59m
IssuesIncident minor
Componente afectate
Purging
monitoring
Am detectat întârzieri în completarea cererilor de purjare. Problema este monitorizată în mod activ și este în prezent rezolvată. Locurile de muncă programate anterior vor fi procesate.
Readurile de imagini nu sunt afectate.
resolved
Acest incident a fost rezolvat. Toate cererile de purjare depuse anterior au fost prelucrate.
Traducere automată din actualizarea oficială a incidentului.
Increased errors for new render requests (Rendering & Legacy video APIs)
A început 4 iunie 2026 la 14:44 UTC · 2h 10m
OutageIncident major
Componente afectate
Rendering Infrastructure
investigating
We are currently investigating increased 5xx errors for new image and legacy video render requests.
identified
We have identified a correlation with an ongoing Google Cloud incident, which reports degradation for VM services in multiple locations.
We continue monitoring errors rates and updates from Google Cloud.
identified
We are seeing a large reduction in error rates. We will continue to monitor for updates.
monitoring
Error rates have subsided to normal levels. We will continue to monitor for updates.
resolved
This incident has been resolved.
Issues with Imgix web tools
A început 16 aprilie 2026 la 17:14 UTC · 29m
OutageIncident major
Componente afectate
Web Administration ToolsAPI Service
investigating
We are investigating issues with Imgix administration tools. There are reports of issues with logging into Dashboard and calling Imgix APIs.
The rendering service is not affected.
monitoring
A fix has been implemented and we are monitoring the admin service.
The rendering service is completely operational.
resolved
This incident has been resolved.
Asset Manager errors when uploading to an Azure Source
A început 3 februarie 2026 la 13:49 UTC · 2h 32m
IssuesIncident minor
Componente afectate
Web Administration Tools
identified
We are investigating uploading errors in the Asset Manager UI for Azure Sources.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Investigating errors with plan upgrades through the dashboard.
A început 26 ianuarie 2026 la 16:15 UTC · 8h 44m
IssuesIncident minor
Componente afectate
Web Administration Tools
identified
We are investigating a billing issue with upgrading plan types. If you need to upgrade your plan, please reach out to support as a workaround.
resolved
This incident has been resolved.
Uploading errors in Asset Manager
A început 12 ianuarie 2026 la 13:53 UTC · 53m
IssuesIncident minor
Componente afectate
Web Administration Tools
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.
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.
resolved
The uploading incident is resolved.
We will follow up with affected customers to restore visibility for previously uploaded assets.
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
Delayed Reports for CDN and Error Logs
A început 20 noiembrie 2025 la 02:04 UTC · 2h 33m
Pending
Componente afectate
API Service
monitoring
We’re currently experiencing delays in generating CDN and Error Log reports for 2025-11-20.
Our team is working on backfilling the data, and we expect the reports to be available by 2025-11-21 (UTC).
monitoring
The backfill for the CDN and Error Log reports is currently underway and is expected to complete within the next hour.
resolved
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.
Delay in Purge requests
A început 13 noiembrie 2025 la 05:02 UTC · 0m
Pending
resolved
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.
We are investigating increased latency for first time renders in EU
A început 29 octombrie 2025 la 11:34 UTC · 1h 12m
IssuesIncident minor
Componente afectate
Rendering Infrastructure
investigating
We are currently investigating this issue.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
# **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.
Investigating issues with changing account plans
A început 28 octombrie 2025 la 17:48 UTC · 10m
Pending
Componente afectate
Web Administration Tools
investigating
We are investigating issues with upgrading/downgrading account plans through the dashboard. In the meantime, please reach out to our support team if you need to change your plan.
resolved
This incident has been resolved.
Investigating increased latency for cache misses in the EU region
A început 27 octombrie 2025 la 14:07 UTC · 1h 49m
IssuesIncident minor
Componente afectate
Rendering Infrastructure
investigating
We are investigating increased latency for cache misses in the EU region.
identified
The issue has been identified and a fix is being implemented.
monitoring
Latency has returned to normal for the affected EU region. We will continue to monitor the situation.
resolved
This incident has been resolved.
Investigating increased latency for new renders
A început 21 octombrie 2025 la 09:26 UTC · 38m
IssuesIncident minor
Componente afectate
Rendering Infrastructure
investigating
We are investigating reports of increased latency for new renders.
monitoring
Rendering latency has been restored. We are monitoring the service.
resolved
This incident has been resolved.
Increase in intermittent 503 errors
A început 8 octombrie 2025 la 23:00 UTC · 0m
IssuesIncident minor
resolved
Between 2025-10-08 23:50 UTC and 2025-10-09 01:50 UTC, a subset of origin fetch requests failed and returned errors.
The issue has been identified and resolved.
Issues with Dashboard
A început 17 septembrie 2025 la 20:53 UTC · 14m
IssuesIncident minor
Componente afectate
Web Administration Tools
investigating
We are currently investigating an issue with the Sources and Analytics tabs in the Dashboard.
The rendering service is not impacted.
resolved
This incident has been resolved.
Elevated rendering errors
A început 12 iunie 2025 la 18:09 UTC · 2h 43m
OutageIncident major
Componente afectate
Web Administration ToolsRendering InfrastructureAPI Service
investigating
We are investigating elevated render error rates for the service.
Previously cached derivatives are not impacted.
identified
The issue has been identified and we are investigating a solution.
identified
The service is experiencing elevated error rates due to a major Google Cloud outage affecting services downstream.
Previously cached derivatives are not impacted.
We are investigating ways to mitigate this issue.
monitoring
The service is restored. We are monitoring the situation.
identified
The Rendering API has fully recovered.
We are continuing to investigate Web Administration related issues (login and Management API) related to the incident.
monitoring
The Rendering API is fully recovered.
Web Administration tooling (logins and the Management API) are recovering. We are monitoring the results.
resolved
The service is completely restored.
postmortem
# Incident Summary
Between **17:55 and 20:22 UTC** on **June 12, 2025**, Imgix services experienced major service disruptions across several key interfaces:
* **Dashboard and Asset Manager**: These interfaces were inaccessible, preventing users from managing their assets or viewing account information.
* **Management API**: Requests to the Management API consistently returned errors, affecting workflows reliant on programmatic updates or asset administration.
* **Rendering API:** Approximately 8% of all Imgix service requests failed due to a high error rate \(~80%\) for **uncached** assets via the Rendering API. Requests in the EU saw a lower failure rate \(~50%\) and a faster recovery time \(45 minutes\) for these uncached requests.
# What caused it
The incident was triggered by a global outage within Google Cloud, which serves as a core infrastructure provider for Imgix. The outage affected most services in all regions simultaneously.
You can read more about the [Google Cloud outage here](https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#RP1d9aZLNFZEJmTBk8e1).
# What happened
* **17:55 UTC:** Internal alerts triggered due to a spike in rendering errors and service timeouts.
* **18:01 UTC:** A short investigation uncovers several timeouts and increased error rates from Google Cloud.
* **18:09 UTC:** Our status page is updated.
* **18:53 UTC:** A major Google Cloud outage is confirmed, after which we update our status page.
* **18:00–20:16 UTC:** Mitigation efforts were hampered by the far-reaching effects of the outage, preventing us from redirecting traffic or applying configuration changes.
* **Throughout:** We confirm that cached images were not affected, though the downtime of several data sources prevents evaluating the full scope and effect of the outage.
* **20:16 UTC:** Google reported recovery in all regions except `us-central1`. This allowed us to verify **significantly lower error rates for EU traffic**
* **20:47 UTC:** Imgix systems achieved full recovery.
* **20:52 UTC:** The incident was officially resolved on our status page.
* **21:23 UTC:** Google confirms a full-service recovery at 21:23 UTC.
# What went wrong
* Google Cloud experienced an outage that simultaneously affected nearly every service in every region worldwide, negating our multi-region redundancy for the image rendering service.
* 3rd party services \(such as our CDN\) were also affected by the outage, which removed some of our options for redirecting traffic across regions based on performance.
* The outage included the control panes that Google provides to its customers, which removed additional options for redirecting traffic and implementing mitigations.
# What we will do to prevent this in the future
* Continuing our ongoing internal discussions and evaluations of a multi-cloud render stack to enable failover in the event of a provider-wide outages.
* Continue evaluating and improving tools to automatically and manually shift traffic as necessary at each layer of the stack.
* Review and enhance incident communication protocols, focusing on faster root cause disclosure and update frequency.
Elevated rendering errors
A început 20 mai 2025 la 15:40 UTC · 30m
IssuesIncident minor
Componente afectate
Web Administration ToolsRendering Infrastructure
investigating
We are currently investigating elevated render error rates for uncached derivative images and the Management API in the NA region. We will update once when we obtain more information.
Previously cached derivatives are not impacted.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Issues with logging in
A început 24 aprilie 2025 la 12:29 UTC · 3h 1m
IssuesIncident minor
Componente afectate
Web Administration Tools
identified
Some customers are experiencing issues with logging into the dashboard.
We have identified the issue and are working on a fix.
monitoring
A fix has been implemented and we are monitoring the results.