Imgix の障害履歴

1. 2026年9月1日 16:36 UTCidentified

   継続的なGoogle Cloudインシデントとの相関性を検証し、複数のサービスのパケットロスとエラーを報告しています。 今後も、Google Cloudがより多くの情報を共有し、エラー率を監視し、更なるアップデートを提供してまいります.

2. 2026年9月1日 17:05 UTCidentified

   このインシデントの潜在的な障害オプションを調査しながら、エラー率を監視しています.

3. 2026年9月1日 17:15 UTCidentified

   トラフィックをリダイレクトする変更を押し出し、サービス全体でエラー率が向上しています。 今後もアップデートを行い、状況を監視してまいります.

4. 2026年9月1日 18:06 UTCidentified

   サービス全体で改善されたエラーレートを観察しています。 今後も状況を監視してまいります.

5. 2026年9月1日 18:31 UTCmonitoring

   エラー率は正常に戻ります。 今後もサービスを監視してまいります.

6. 2026年9月1日 18:48 UTCresolved

   この事件は解決しました.

7. 2026年9月11日 19:25 UTCpostmortem

   ## 概要 約7:49 AMと10:57 AM PDT 9月 1, 2026, Googleクラウドプラットフォーム領域のネットワーク障害は、Imgixの画像とビデオレンダリングパイプラインの一部を出力するインフラへの接続を中断しました. この結果は、そのウィンドウの間に提供される総リクエストの平均エラー率〜2%になります。 過去にキャッシュされた画像や動画は、インシデント全体で正常に配信されるようになりました。 ## どのWent Wrong Google Cloud Platformは、米国地域におけるコンピューティングインフラに影響を及ぼすネットワークレベルの障害を経験しました。 レンダリングインフラストラクチャを構成するGCPサービス間の障害は、その地域のレンダリングリクエストの共有を防ぎます。 グーグルは、ネットワークのメンテナンス中に発生した事故による混乱が確認され、事件の見直しを継続しています。 詳細は、このレポートを更新することがあります。 多角的なサービス構成を持つにもかかわらず、我々は経験した劣化をもたらす地域全体にトラフィックが影響されました。 誤差率が上昇し、事件全体に波に落ちたため、問題が明らかになったら、事故を削減し、正常にトラフィックを戻すために、健康な領域へのトラフィックの相続カットを実行しました。 ## 未来でこれを防ぐために何をすべきか 今後の事故の対応を改善するために、横断的なトラフィックシフトの基準と手順を精査しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月1日 15:30 UTCidentified

   上流プロバイダーとの継続的なインシデントにより、新しいレンダリングリクエストに対するエラーの増加を特定しました.

2. 2026年9月1日 15:35 UTCidentified

   継続的なGoogle Cloudインシデントとの相関性を検証し、複数のサービスのパケットロスとエラーを報告しています。 今後も、Google Cloudがより多くの情報を共有し、エラー率を監視し、更なるアップデートを提供してまいります.

3. 2026年9月1日 16:07 UTCmonitoring

   エラーレートは通常のレベルに戻りました。 Google Cloudのアップデートを待ってから、状況を監視し続けています.

4. 2026年9月1日 16:22 UTCresolved

   This incident has been resolved.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月14日 4: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. 2026年8月14日 5:08 UTCmonitoring

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

3. 2026年8月14日 5: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. 2026年6月25日 10:28 UTCmonitoring

   パージリクエストを補完する遅延を検出しました。 問題は積極的に監視されており、現在解決しています。 過去に予定されているジョブが処理されます。 画像レンダリングは影響しません.

2. 2026年6月25日 11:27 UTCresolved

   この事件は解決しました。 以前に提出されたパージリクエストは処理済みです.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月4日 14:44 UTCinvestigating

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

2. 2026年6月4日 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. 2026年6月4日 15:45 UTCidentified

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

4. 2026年6月4日 16:00 UTCmonitoring

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

5. 2026年6月4日 16:54 UTCresolved

   This incident has been resolved.

1. 2026年4月16日 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. 2026年4月16日 17:27 UTCmonitoring

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

3. 2026年4月16日 17:43 UTCresolved

   This incident has been resolved.

1. 2026年2月3日 13:49 UTCidentified

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

2. 2026年2月3日 16:00 UTCmonitoring

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

3. 2026年2月3日 16:21 UTCresolved

   This incident has been resolved.

1. 2026年1月26日 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. 2026年1月27日 0:58 UTCresolved

   This incident has been resolved.

1. 2026年1月12日 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. 2026年1月12日 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. 2026年1月12日 14:47 UTCresolved

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

4. 2026年1月28日 0: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. 2025年11月20日 2: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. 2025年11月20日 4:14 UTCmonitoring

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

3. 2025年11月20日 4: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. 2025年11月13日 5: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. 2025年10月29日 11:34 UTCinvestigating

   We are currently investigating this issue.

2. 2025年10月29日 11:56 UTCidentified

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

3. 2025年10月29日 12:25 UTCmonitoring

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

4. 2025年10月29日 12:46 UTCresolved

   This incident has been resolved.

5. 2025年11月11日 0: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. 2025年10月28日 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. 2025年10月28日 17:58 UTCresolved

   This incident has been resolved.

1. 2025年10月27日 14:07 UTCinvestigating

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

2. 2025年10月27日 14:23 UTCidentified

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

3. 2025年10月27日 15:25 UTCmonitoring

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

4. 2025年10月27日 15:56 UTCresolved

   This incident has been resolved.

1. 2025年10月21日 9:26 UTCinvestigating

   We are investigating reports of increased latency for new renders.

2. 2025年10月21日 9:50 UTCmonitoring

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

3. 2025年10月21日 10:04 UTCresolved

   This incident has been resolved.

1. 2025年10月9日 1: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. 2025年9月17日 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. 2025年9月17日 21:07 UTCresolved

   This incident has been resolved.

1. 2025年6月12日 18:09 UTCinvestigating

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

2. 2025年6月12日 18:15 UTCidentified

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

3. 2025年6月12日 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. 2025年6月12日 20:26 UTCmonitoring

   The service is restored. We are monitoring the situation.

5. 2025年6月12日 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. 2025年6月12日 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. 2025年6月12日 20:52 UTCresolved

   The service is completely restored.

8. 2025年6月20日 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. 2025年5月20日 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. 2025年5月20日 15:57 UTCidentified

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

3. 2025年5月20日 16:01 UTCmonitoring

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

4. 2025年5月20日 16:10 UTCresolved

   This incident has been resolved.

1. 2025年4月24日 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. 2025年4月24日 14:10 UTCmonitoring

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

3. 2025年4月24日 15:31 UTCresolved

   This incident has been resolved.