Historique des pannes de Imgix

1. 1 septembre 2026 à 16:36 UTCidentified

   Nous avons identifié une corrélation avec un incident de Google Cloud en cours, qui signale une perte de paquets élevée et des erreurs pour plusieurs services. Nous continuerons de surveiller les taux d'erreurs et de fournir d'autres mises à jour puisque Google Cloud partage plus d'informations.

2. 1 septembre 2026 à 17:05 UTCidentified

   Nous continuons de surveiller les taux d'erreurs tout en étudiant les options de rupture possibles pour cet incident.

3. 1 septembre 2026 à 17:15 UTCidentified

   Nous poussons les changements à rediriger le trafic et voyons des taux d'erreur améliorés dans l'ensemble du service. Nous continuerons de faire des mises à jour et de surveiller la situation.

4. 1 septembre 2026 à 18:06 UTCidentified

   Nous observons des taux d'erreur améliorés dans l'ensemble du service. Nous continuerons de suivre la situation.

5. 1 septembre 2026 à 18:31 UTCmonitoring

   Les taux d'erreur sont de retour à la normale. Nous continuerons de surveiller le service.

6. 1 septembre 2026 à 18:48 UTCresolved

   Cet incident a été résolu.

7. 11 septembre 2026 à 19:25 UTCpostmortem

   Résumé Entre 7h49 et 10h57 le 1er septembre 2026, une faille réseau dans une région de Google Cloud Platform a perturbé la connectivité à une infrastructure qui alimente une partie du pipeline de rendu d'images et de vidéos d'Imgix. Cela a entraîné un taux d'erreur moyen d'environ 2 % du nombre total de demandes servies pendant cette fenêtre. Les images et vidéos précédemment mises en cache ont continué à être servies normalement tout au long de l'incident. Ce qui ne va pas Google Cloud Platform a connu une faille de niveau réseau affectant l'infrastructure de calcul dans une de ses régions américaines. La faute a perturbé la connectivité entre les services GCP qui composent notre infrastructure de rendu, empêchant une partie des demandes de rendu dans cette région de remplir. Google a confirmé que la perturbation a été causée par un incident survenu pendant leur maintenance du réseau et continue d'examiner l'incident. Nous pourrons mettre à jour ce rapport une fois que nous aurons reçu plus d'information. Malgré des configurations multizones pour nos services, le trafic a été touché dans toute la région, ce qui a entraîné la dégradation de nos services. Au fur et à mesure que les taux d'erreur se sont accrus et ont chuté en vagues tout au long de l'incident, nous avons procédé à une réduction progressive du trafic vers une région saine afin de réduire l'impact et de rétablir le trafic à la normale une fois le problème réglé. Ce que nous ferons pour éviter cela dans l'avenir Nous peaufinons nos critères et nos procédures pour les déplacements de trafic transrégionaux afin d'améliorer nos réponses dans les incidents futurs.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 1 septembre 2026 à 15:30 UTCidentified

   Nous avons relevé une augmentation des erreurs pour les nouvelles demandes de rendu en raison d'un incident continu avec un fournisseur en amont.

2. 1 septembre 2026 à 15:35 UTCidentified

   Nous avons identifié une corrélation avec un incident de Google Cloud en cours, qui signale une perte de paquets élevée et des erreurs pour plusieurs services. Nous continuerons de surveiller les taux d'erreurs et de fournir d'autres mises à jour puisque Google Cloud partage plus d'informations.

3. 1 septembre 2026 à 16:07 UTCmonitoring

   Les taux d'erreur sont revenus à des niveaux normaux. Nous continuons à surveiller la situation en attendant une mise à jour de Google Cloud.

4. 1 septembre 2026 à 16:22 UTCresolved

   This incident has been resolved.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 14 août 2026 à 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 août 2026 à 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 août 2026 à 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 juin 2026 à 10:28 UTCmonitoring

   Nous avons détecté des retards dans le traitement des demandes de purge. La question fait l'objet d'un suivi actif et est actuellement résolue. Les emplois précédemment prévus seront traités. Les rendus d'images ne sont pas affectés.

2. 25 juin 2026 à 11:27 UTCresolved

   Cet incident a été résolu. Toutes les demandes de purge soumises antérieurement ont été traitées.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 4 juin 2026 à 14:44 UTCinvestigating

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

2. 4 juin 2026 à 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 juin 2026 à 15:45 UTCidentified

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

4. 4 juin 2026 à 16:00 UTCmonitoring

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

5. 4 juin 2026 à 16:54 UTCresolved

   This incident has been resolved.

1. 16 avril 2026 à 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 avril 2026 à 17:27 UTCmonitoring

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

3. 16 avril 2026 à 17:43 UTCresolved

   This incident has been resolved.

1. 3 février 2026 à 13:49 UTCidentified

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

2. 3 février 2026 à 16:00 UTCmonitoring

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

3. 3 février 2026 à 16:21 UTCresolved

   This incident has been resolved.

1. 26 janvier 2026 à 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 janvier 2026 à 00:58 UTCresolved

   This incident has been resolved.

1. 12 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 14:47 UTCresolved

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

4. 28 janvier 2026 à 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 novembre 2025 à 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 novembre 2025 à 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 novembre 2025 à 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 novembre 2025 à 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 octobre 2025 à 11:34 UTCinvestigating

   We are currently investigating this issue.

2. 29 octobre 2025 à 11:56 UTCidentified

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

3. 29 octobre 2025 à 12:25 UTCmonitoring

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

4. 29 octobre 2025 à 12:46 UTCresolved

   This incident has been resolved.

5. 11 novembre 2025 à 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 octobre 2025 à 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 octobre 2025 à 17:58 UTCresolved

   This incident has been resolved.

1. 27 octobre 2025 à 14:07 UTCinvestigating

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

2. 27 octobre 2025 à 14:23 UTCidentified

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

3. 27 octobre 2025 à 15:25 UTCmonitoring

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

4. 27 octobre 2025 à 15:56 UTCresolved

   This incident has been resolved.

1. 21 octobre 2025 à 09:26 UTCinvestigating

   We are investigating reports of increased latency for new renders.

2. 21 octobre 2025 à 09:50 UTCmonitoring

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

3. 21 octobre 2025 à 10:04 UTCresolved

   This incident has been resolved.

1. 9 octobre 2025 à 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 septembre 2025 à 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 septembre 2025 à 21:07 UTCresolved

   This incident has been resolved.

1. 12 juin 2025 à 18:09 UTCinvestigating

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

2. 12 juin 2025 à 18:15 UTCidentified

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

3. 12 juin 2025 à 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 juin 2025 à 20:26 UTCmonitoring

   The service is restored. We are monitoring the situation.

5. 12 juin 2025 à 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 juin 2025 à 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 juin 2025 à 20:52 UTCresolved

   The service is completely restored.

8. 20 juin 2025 à 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 mai 2025 à 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 mai 2025 à 15:57 UTCidentified

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

3. 20 mai 2025 à 16:01 UTCmonitoring

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

4. 20 mai 2025 à 16:10 UTCresolved

   This incident has been resolved.

1. 24 avril 2025 à 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 avril 2025 à 14:10 UTCmonitoring

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

3. 24 avril 2025 à 15:31 UTCresolved

   This incident has been resolved.