Störungsverlauf von Imgix

1. 1. September 2026 um 16:36 UTCidentified

   Wir haben eine Korrelation mit einem laufenden Google Cloud-Vorfall identifiziert, der einen erhöhten Paketverlust und Fehler für mehrere Dienste meldet. Wir werden weiterhin die Fehlerquoten überwachen und weitere Updates bereitstellen, da Google Cloud weitere Informationen weitergibt.

2. 1. September 2026 um 17:05 UTCidentified

   Wir überwachen weiterhin die Fehlerquoten und untersuchen mögliche Failover-Optionen für diesen Vorfall.

3. 1. September 2026 um 17:15 UTCidentified

   Wir schieben Änderungen zur Umleitung des Datenverkehrs aus und sehen verbesserte Fehlerraten im gesamten Dienst. Wir werden weiterhin Updates vornehmen und die Situation überwachen.

4. 1. September 2026 um 18:06 UTCidentified

   Wir beobachten verbesserte Fehlerquoten im gesamten Service. Wir werden die Situation weiterhin beobachten.

5. 1. September 2026 um 18:31 UTCmonitoring

   Die Fehlerquoten sind wieder normal. Wir werden den Service weiterhin überwachen.

6. 1. September 2026 um 18:48 UTCresolved

   Dieser Vorfall wurde behoben.

7. 11. September 2026 um 19:25 UTCpostmortem

   ## Zusammenfassung Zwischen etwa 7:49 Uhr und 10:57 Uhr PDT am 1. September 2026 störte ein Netzwerkfehler in einer Google Cloud Platform-Region die Konnektivität mit der Infrastruktur, die einen Teil der Bild- und Video-Rendering-Pipeline von Imgix unterstützt. Dies führte zu einer durchschnittlichen Fehlerrate von ~ 2% der gesamten Anfragen, die während dieses Fensters bearbeitet wurden. Zuvor zwischengespeicherte Bilder und Videos wurden während des gesamten Vorfalls weiterhin normal serviert. Was schief gelaufen ist Die Google Cloud Platform hatte einen Fehler auf Netzwerkebene, der die Recheninfrastruktur in einer ihrer US-Regionen beeinträchtigte. Der Fehler unterbrach die Konnektivität zwischen den GCP-Diensten, aus denen unsere Rendering-Infrastruktur besteht, und verhinderte, dass ein Teil der Renderanfragen in dieser Region abgeschlossen wurde. Google hat bestätigt, dass die Störung durch einen Vorfall verursacht wurde, der während der Netzwerkwartung aufgetreten ist, und überprüft den Vorfall weiterhin. Wir können diesen Bericht aktualisieren, sobald wir weitere Informationen erhalten. Trotz der mehrzonalen Konfigurationen für unsere Dienste wurde der Verkehr in der gesamten Region beeinträchtigt, was zu der Verschlechterung führte, die wir erlebten. Da die Fehlerraten während des Vorfalls in Wellen anstiegen und fielen, führten wir eine schrittweise Reduzierung des Datenverkehrs in eine gesunde Region durch, um die Auswirkungen zu reduzieren, und kehrten den Datenverkehr wieder auf den Normalzustand zurück, sobald das Problem behoben war. Was wir tun werden, um dies in Zukunft zu verhindern Wir verfeinern unsere Kriterien und Verfahren für überregionale Verkehrsverlagerungen, um unsere Reaktionen auf zukünftige Vorfälle zu verbessern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. September 2026 um 15:30 UTCidentified

   Wir haben eine Zunahme von Fehlern bei neuen Rendering-Anfragen aufgrund eines laufenden Vorfalls bei einem Upstream-Anbieter festgestellt.

2. 1. September 2026 um 15:35 UTCidentified

   Wir haben eine Korrelation mit einem laufenden Google Cloud-Vorfall identifiziert, der einen erhöhten Paketverlust und Fehler für mehrere Dienste meldet. Wir werden weiterhin die Fehlerquoten überwachen und weitere Updates bereitstellen, da Google Cloud weitere Informationen weitergibt.

3. 1. September 2026 um 16:07 UTCmonitoring

   Die Fehlerquoten sind auf ein normales Niveau zurückgekehrt. Wir beobachten die Situation weiterhin, während wir auf ein Update von Google Cloud warten.

4. 1. September 2026 um 16:22 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 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. August 2026 um 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. August 2026 um 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. Juni 2026 um 10:28 UTCmonitoring

   Wir haben Verzögerungen beim Ausfüllen von Bereinigungsanfragen festgestellt. Das Problem wird aktiv überwacht und wird derzeit gelöst. Zuvor geplante Jobs werden bearbeitet. Bildwiedergaben sind nicht betroffen.

2. 25. Juni 2026 um 11:27 UTCresolved

   Dieser Vorfall wurde behoben. Alle zuvor eingereichten Bereinigungsanfragen wurden bearbeitet.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Juni 2026 um 14:44 UTCinvestigating

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

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

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

4. 4. Juni 2026 um 16:00 UTCmonitoring

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

5. 4. Juni 2026 um 16:54 UTCresolved

   This incident has been resolved.

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

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

3. 16. April 2026 um 17:43 UTCresolved

   This incident has been resolved.

1. 3. Februar 2026 um 13:49 UTCidentified

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

2. 3. Februar 2026 um 16:00 UTCmonitoring

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

3. 3. Februar 2026 um 16:21 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

4. 28. Januar 2026 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 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. Oktober 2025 um 11:34 UTCinvestigating

   We are currently investigating this issue.

2. 29. Oktober 2025 um 11:56 UTCidentified

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

3. 29. Oktober 2025 um 12:25 UTCmonitoring

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

4. 29. Oktober 2025 um 12:46 UTCresolved

   This incident has been resolved.

5. 11. November 2025 um 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. Oktober 2025 um 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. Oktober 2025 um 17:58 UTCresolved

   This incident has been resolved.

1. 27. Oktober 2025 um 14:07 UTCinvestigating

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

2. 27. Oktober 2025 um 14:23 UTCidentified

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

3. 27. Oktober 2025 um 15:25 UTCmonitoring

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

4. 27. Oktober 2025 um 15:56 UTCresolved

   This incident has been resolved.

1. 21. Oktober 2025 um 09:26 UTCinvestigating

   We are investigating reports of increased latency for new renders.

2. 21. Oktober 2025 um 09:50 UTCmonitoring

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

3. 21. Oktober 2025 um 10:04 UTCresolved

   This incident has been resolved.

1. 9. Oktober 2025 um 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. September 2025 um 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. September 2025 um 21:07 UTCresolved

   This incident has been resolved.

1. 12. Juni 2025 um 18:09 UTCinvestigating

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

2. 12. Juni 2025 um 18:15 UTCidentified

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

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

   The service is restored. We are monitoring the situation.

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

   The service is completely restored.

8. 20. Juni 2025 um 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 um 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 um 15:57 UTCidentified

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

3. 20. Mai 2025 um 16:01 UTCmonitoring

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

4. 20. Mai 2025 um 16:10 UTCresolved

   This incident has been resolved.

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

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

3. 24. April 2025 um 15:31 UTCresolved

   This incident has been resolved.