Histórico de interrupções do Imgix

1. 1 Gwengolo 2026 da 16:36 UTCidentified

   Identificamos uma correlação com um incidente contínuo do Google Cloud, que relata perdas elevadas de pacotes e erros para vários serviços. Continuaremos a monitorar as taxas de erro e fornecer novas atualizações, pois o Google Cloud compartilha mais informações.

2. 1 Gwengolo 2026 da 17:05 UTCidentified

   Continuamos a monitorar as taxas de erro enquanto investigamos possíveis opções de failover para este incidente.

3. 1 Gwengolo 2026 da 17:15 UTCidentified

   Estamos empurrando as mudanças para redirecionar o tráfego e estamos vendo taxas de erro melhoradas em todo o serviço. Continuaremos a fazer actualizações e a acompanhar a situação.

4. 1 Gwengolo 2026 da 18:06 UTCidentified

   Estamos observando taxas de erro melhoradas em todo o serviço. Continuaremos a acompanhar a situação.

5. 1 Gwengolo 2026 da 18:31 UTCmonitoring

   As taxas de erro voltaram ao normal. Continuaremos a monitorizar o serviço.

6. 1 Gwengolo 2026 da 18:48 UTCresolved

   Este incidente foi resolvido.

7. 11 Gwengolo 2026 da 19:25 UTCpostmortem

   # # Resumo Entre aproximadamente 7:49 AM e 10:57 PDT em 1o de setembro de 2026, uma falha de rede em uma região da Google Cloud Platform interrompeu a conectividade com infraestrutura que alimenta uma parte do pipeline de imagem e renderização de vídeo da Imgix. Isso resultou em uma taxa de erro média ~2% do total de solicitações atendidas durante essa janela. Anteriormente, imagens e vídeos em cache continuaram a ser servidos normalmente durante todo o incidente. # # O que correu mal O Google Cloud Platform experimentou uma falha de nível de rede afetando a infraestrutura de computação em uma de suas regiões dos EUA. A falha rompeu a conectividade entre os serviços GCP que compõem nossa infraestrutura de renderização, impedindo que uma parcela de pedidos de renderização naquela região completasse. O Google confirmou que a perturbação foi causada por um incidente que ocorreu durante a manutenção da rede e continua a rever o incidente. Podemos atualizar este relatório assim que recebermos mais informações. Apesar de termos configurações multizonais para nossos serviços, o tráfego foi impactado em toda a região, resultando na degradação que experimentamos. À medida que as taxas de erro aumentavam e caíam em ondas ao longo do incidente, realizamos um corte de tráfego phased para uma região saudável para reduzir o impacto, e devolvemos o tráfego ao normal uma vez que o problema foi resolvido. # # O que vamos fazer para evitar isso no futuro Estamos a aperfeiçoar os nossos critérios e procedimentos para as deslocações de tráfego inter-regionais para melhorar as nossas respostas em futuros incidentes.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gwengolo 2026 da 15:30 UTCidentified

   Identificamos um aumento de erros para novos pedidos de renderização devido a um incidente contínuo com um provedor upstream.

2. 1 Gwengolo 2026 da 15:35 UTCidentified

   Identificamos uma correlação com um incidente contínuo do Google Cloud, que relata perdas elevadas de pacotes e erros para vários serviços. Continuaremos a monitorar as taxas de erro e fornecer novas atualizações, pois o Google Cloud compartilha mais informações.

3. 1 Gwengolo 2026 da 16:07 UTCmonitoring

   As taxas de erro voltaram aos níveis normais. Continuamos a monitorar a situação enquanto aguardamos uma atualização do Google Cloud.

4. 1 Gwengolo 2026 da 16:22 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Eost 2026 da 04:53 UTCidentified

   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.

2. 14 Eost 2026 da 05:08 UTCmonitoring

   Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud.

3. 14 Eost 2026 da 05:28 UTCresolved

   While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.

1. 25 Mezheven 2026 da 10:28 UTCmonitoring

   Detectamos atrasos no preenchimento de pedidos de purga. A questão está a ser acompanhada activamente e está actualmente a ser resolvida. Trabalhos agendados anteriormente serão processados. Os renderizadores de imagens não são afetados.

2. 25 Mezheven 2026 da 11:27 UTCresolved

   Este incidente foi resolvido. Todos os pedidos de purga submetidos anteriormente foram processados.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Mezheven 2026 da 14:44 UTCinvestigating

   We are currently investigating increased 5xx errors for new image and legacy video render requests.

2. 4 Mezheven 2026 da 14:52 UTCidentified

   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.

3. 4 Mezheven 2026 da 15:45 UTCidentified

   We are seeing a large reduction in error rates. We will continue to monitor for updates.

4. 4 Mezheven 2026 da 16:00 UTCmonitoring

   Error rates have subsided to normal levels. We will continue to monitor for updates.

5. 4 Mezheven 2026 da 16:54 UTCresolved

   This incident has been resolved.

1. 16 Ebrel 2026 da 17:14 UTCinvestigating

   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.

2. 16 Ebrel 2026 da 17:27 UTCmonitoring

   A fix has been implemented and we are monitoring the admin service. The rendering service is completely operational.

3. 16 Ebrel 2026 da 17:43 UTCresolved

   This incident has been resolved.

1. 3 Cʼhwevrer 2026 da 13:49 UTCidentified

   We are investigating uploading errors in the Asset Manager UI for Azure Sources.

2. 3 Cʼhwevrer 2026 da 16:00 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 3 Cʼhwevrer 2026 da 16:21 UTCresolved

   This incident has been resolved.

1. 26 Genver 2026 da 16:15 UTCidentified

   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.

2. 27 Genver 2026 da 00:58 UTCresolved

   This incident has been resolved.

1. 12 Genver 2026 da 13:53 UTCinvestigating

   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.

2. 12 Genver 2026 da 14:37 UTCmonitoring

   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.

3. 12 Genver 2026 da 14:47 UTCresolved

   The uploading incident is resolved. We will follow up with affected customers to restore visibility for previously uploaded assets.

4. 28 Genver 2026 da 00:27 UTCpostmortem

   # 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

1. 20 Du 2025 da 02:04 UTCmonitoring

   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).

2. 20 Du 2025 da 04:14 UTCmonitoring

   The backfill for the CDN and Error Log reports is currently underway and is expected to complete within the next hour.

3. 20 Du 2025 da 04:36 UTCresolved

   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.

1. 13 Du 2025 da 05:02 UTCresolved

   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.

1. 29 Here 2025 da 11:34 UTCinvestigating

   We are currently investigating this issue.

2. 29 Here 2025 da 11:56 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29 Here 2025 da 12:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 29 Here 2025 da 12:46 UTCresolved

   This incident has been resolved.

5. 11 Du 2025 da 00:18 UTCpostmortem

   # **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.

1. 28 Here 2025 da 17:48 UTCinvestigating

   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.

2. 28 Here 2025 da 17:58 UTCresolved

   This incident has been resolved.

1. 27 Here 2025 da 14:07 UTCinvestigating

   We are investigating increased latency for cache misses in the EU region.

2. 27 Here 2025 da 14:23 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 27 Here 2025 da 15:25 UTCmonitoring

   Latency has returned to normal for the affected EU region. We will continue to monitor the situation.

4. 27 Here 2025 da 15:56 UTCresolved

   This incident has been resolved.

1. 21 Here 2025 da 09:26 UTCinvestigating

   We are investigating reports of increased latency for new renders.

2. 21 Here 2025 da 09:50 UTCmonitoring

   Rendering latency has been restored. We are monitoring the service.

3. 21 Here 2025 da 10:04 UTCresolved

   This incident has been resolved.

1. 9 Here 2025 da 01:20 UTCresolved

   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.

1. 17 Gwengolo 2025 da 20:53 UTCinvestigating

   We are currently investigating an issue with the Sources and Analytics tabs in the Dashboard. The rendering service is not impacted.

2. 17 Gwengolo 2025 da 21:07 UTCresolved

   This incident has been resolved.

1. 12 Mezheven 2025 da 18:09 UTCinvestigating

   We are investigating elevated render error rates for the service. Previously cached derivatives are not impacted.

2. 12 Mezheven 2025 da 18:15 UTCidentified

   The issue has been identified and we are investigating a solution.

3. 12 Mezheven 2025 da 18:53 UTCidentified

   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.

4. 12 Mezheven 2025 da 20:26 UTCmonitoring

   The service is restored. We are monitoring the situation.

5. 12 Mezheven 2025 da 20:38 UTCidentified

   The Rendering API has fully recovered. We are continuing to investigate Web Administration related issues (login and Management API) related to the incident.

6. 12 Mezheven 2025 da 20:47 UTCmonitoring

   The Rendering API is fully recovered. Web Administration tooling (logins and the Management API) are recovering. We are monitoring the results.

7. 12 Mezheven 2025 da 20:52 UTCresolved

   The service is completely restored.

8. 20 Mezheven 2025 da 19:03 UTCpostmortem

   # 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.

1. 20 Mae 2025 da 15:40 UTCinvestigating

   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.

2. 20 Mae 2025 da 15:57 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 20 Mae 2025 da 16:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 20 Mae 2025 da 16:10 UTCresolved

   This incident has been resolved.

1. 24 Ebrel 2025 da 12:29 UTCidentified

   Some customers are experiencing issues with logging into the dashboard. We have identified the issue and are working on a fix.

2. 24 Ebrel 2025 da 14:10 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 24 Ebrel 2025 da 15:31 UTCresolved

   This incident has been resolved.