imgix Outage History

Started Sep 01, 2026, 04:36 PM UTC· resolved Sep 01, 2026, 06:48 PM UTC

1. identified Sep 01, 2026, 04:36 PM UTC

   We have identified a correlation with an ongoing Google Cloud incident, which reports elevated packet loss and errors for multiple services. We will continue to monitor error rates and provide further updates as Google Cloud shares more information.

2. identified Sep 01, 2026, 05:05 PM UTC

   We are continuing to monitor error rates while investigating potential failover options for this incident.

3. identified Sep 01, 2026, 05:15 PM UTC

   We are pushing out changes to redirect traffic and are seeing improved error rates across the service. We will continue to make updates and monitor the situation.

4. identified Sep 01, 2026, 06:06 PM UTC

   We are observing improved error rates across the service. We will continue to monitor the situation.

5. monitoring Sep 01, 2026, 06:31 PM UTC

   Error rates are back to normal. We will continue to monitor the service.

6. resolved Sep 01, 2026, 06:48 PM UTC

   This incident has been resolved.

7. postmortem Sep 11, 2026, 07:25 PM UTC

   ## Summary Between approximately 7:49 AM and 10:57 AM PDT on September 1, 2026, a network fault in a Google Cloud Platform region disrupted connectivity to infrastructure that powers a portion of Imgix's image and video rendering pipeline. This resulted in an average error rate ~2% of total requests served during that window. Previously cached images and videos continued to be served normally throughout the incident. ## What Went Wrong Google Cloud Platform experienced a network-level fault affecting compute infrastructure in one of its US regions. The fault disrupted connectivity between the GCP services that make up our rendering infrastructure, preventing a share of render requests in that region from completing. Google has confirmed the disruption was caused by an incident that occurred during their network maintenance and is continuing to review the incident. We may update this report once we receive more information. Despite having multi-zonal configurations for our services, traffic was impacted across the whole region resulting in the degradation we experienced. As error rates rose and fell in waves throughout the incident, we performed a phased cutover of traffic to a healthy region to reduce impact, and returned traffic to normal once the issue cleared. ## What We Will Do To Prevent This In The Future We are refining our criteria and procedures for cross-regional traffic shifts to improve our responses in future incidents.

Read the full incident report →

Started Jun 25, 2026, 10:28 AM UTC· resolved Jun 25, 2026, 11:27 AM UTC

1. monitoring Jun 25, 2026, 10:28 AM UTC

   We've detected delays in completing purge requests. The issue is being actively monitored and is currently resolving. Previously scheduled jobs will be processed. Image renders are not affected.

2. resolved Jun 25, 2026, 11:27 AM UTC

   This incident has been resolved. All previously submitted purge requests have been processed.

Read the full incident report →

Started Jun 04, 2026, 02:44 PM UTC· resolved Jun 04, 2026, 04:54 PM UTC

1. investigating Jun 04, 2026, 02:44 PM UTC

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

2. identified Jun 04, 2026, 02:52 PM UTC

   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. identified Jun 04, 2026, 03:45 PM UTC

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

4. monitoring Jun 04, 2026, 04:00 PM UTC

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

5. resolved Jun 04, 2026, 04:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2026, 05:14 PM UTC· resolved Apr 16, 2026, 05:43 PM UTC

1. investigating Apr 16, 2026, 05:14 PM UTC

   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. monitoring Apr 16, 2026, 05:27 PM UTC

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

3. resolved Apr 16, 2026, 05:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 03, 2026, 01:49 PM UTC· resolved Feb 03, 2026, 04:21 PM UTC

1. identified Feb 03, 2026, 01:49 PM UTC

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

2. monitoring Feb 03, 2026, 04:00 PM UTC

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

3. resolved Feb 03, 2026, 04:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 26, 2026, 04:15 PM UTC· resolved Jan 27, 2026, 12:58 AM UTC

1. identified Jan 26, 2026, 04:15 PM UTC

   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. resolved Jan 27, 2026, 12:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 12, 2026, 01:53 PM UTC· resolved Jan 12, 2026, 02:47 PM UTC

1. investigating Jan 12, 2026, 01:53 PM UTC

   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. monitoring Jan 12, 2026, 02:37 PM UTC

   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. resolved Jan 12, 2026, 02:47 PM UTC

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

4. postmortem Jan 28, 2026, 12:27 AM UTC

   # 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

Read the full incident report →

Started Nov 20, 2025, 02:04 AM UTC· resolved Nov 20, 2025, 04:36 AM UTC

1. monitoring Nov 20, 2025, 02:04 AM UTC

   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. monitoring Nov 20, 2025, 04:14 AM UTC

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

3. resolved Nov 20, 2025, 04:36 AM UTC

   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.

Read the full incident report →

Started Nov 13, 2025, 05:02 AM UTC· resolved Nov 14, 2025, 05:00 AM UTC

1. resolved Nov 13, 2025, 05:02 AM UTC

   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.

Read the full incident report →

Started Oct 29, 2025, 11:34 AM UTC· resolved Oct 29, 2025, 12:46 PM UTC

1. investigating Oct 29, 2025, 11:34 AM UTC

   We are currently investigating this issue.

2. identified Oct 29, 2025, 11:56 AM UTC

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

3. monitoring Oct 29, 2025, 12:25 PM UTC

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

4. resolved Oct 29, 2025, 12:46 PM UTC

   This incident has been resolved.

5. postmortem Nov 11, 2025, 12:18 AM UTC

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

Read the full incident report →

Started Oct 28, 2025, 05:48 PM UTC· resolved Oct 28, 2025, 05:58 PM UTC

1. investigating Oct 28, 2025, 05:48 PM UTC

   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. resolved Oct 28, 2025, 05:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 02:07 PM UTC· resolved Oct 27, 2025, 03:56 PM UTC

1. investigating Oct 27, 2025, 02:07 PM UTC

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

2. identified Oct 27, 2025, 02:23 PM UTC

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

3. monitoring Oct 27, 2025, 03:25 PM UTC

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

4. resolved Oct 27, 2025, 03:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2025, 09:26 AM UTC· resolved Oct 21, 2025, 10:04 AM UTC

1. investigating Oct 21, 2025, 09:26 AM UTC

   We are investigating reports of increased latency for new renders.

2. monitoring Oct 21, 2025, 09:50 AM UTC

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

3. resolved Oct 21, 2025, 10:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 08, 2025, 11:00 PM UTC· resolved Oct 09, 2025, 01:50 AM UTC

1. resolved Oct 09, 2025, 01:20 AM UTC

   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.

Read the full incident report →

Started Sep 17, 2025, 08:53 PM UTC· resolved Sep 17, 2025, 09:07 PM UTC

1. investigating Sep 17, 2025, 08:53 PM UTC

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

2. resolved Sep 17, 2025, 09:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:09 PM UTC· resolved Jun 12, 2025, 08:52 PM UTC

1. investigating Jun 12, 2025, 06:09 PM UTC

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

2. identified Jun 12, 2025, 06:15 PM UTC

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

3. identified Jun 12, 2025, 06:53 PM UTC

   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. monitoring Jun 12, 2025, 08:26 PM UTC

   The service is restored. We are monitoring the situation.

5. identified Jun 12, 2025, 08:38 PM UTC

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

6. monitoring Jun 12, 2025, 08:47 PM UTC

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

7. resolved Jun 12, 2025, 08:52 PM UTC

   The service is completely restored.

8. postmortem Jun 20, 2025, 07:03 PM UTC

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

Read the full incident report →

Started Apr 24, 2025, 12:29 PM UTC· resolved Apr 24, 2025, 03:31 PM UTC

1. identified Apr 24, 2025, 12:29 PM UTC

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

2. monitoring Apr 24, 2025, 02:10 PM UTC

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

3. resolved Apr 24, 2025, 03:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2025, 05:48 AM UTC· resolved Mar 18, 2025, 06:56 PM UTC

1. identified Mar 17, 2025, 05:48 AM UTC

   We have identified an issue affecting the Imgix Asset Manager. Users may experience difficulties searching for previously indexed assets and delays in indexing new assets. A fix is currently in progress. The rendering service remains unaffected.

2. resolved Mar 18, 2025, 06:56 PM UTC

   The root problem of the incident has been resolved. Some assets may still return an error. Please get in touch with [email protected] if you are experiencing issues

3. postmortem Mar 31, 2025, 05:12 PM UTC

   # What happened Between **March 17th, 5:48 AM UTC** and **March 18th, 6:56 PM UTC**, the Asset Manager experienced an indexing outage. During this period, newly uploaded assets and a very small percentage of pre-existing assets were not appearing in the Asset Manager UI. These assets were still successfully uploaded to the Origin and were accessible via the Rendering API. # How it happened An unannounced maintenance from our upstream provider caused a node failure in our Asset Manager infrastructure, resulting in the temporary loss of indexed asset data. # What went wrong Several things went wrong during this incident: * Our service provider failed to notify us of the maintenance window * Our Asset Manager infrastructure was not adequately provisioned to tolerate failures during the maintenance * A large amount of data was required to be restored, resulting in a severely prolonged restoration process # What we are doing to address this incident * We have migrated and optimized infrastructure configurations to better tolerate node failures * We created additional backups and introduced additional indexing layers to improve redundancy and resilience * We are evaluating alternative upstream providers to reduce dependency risks

Read the full incident report →

Started Dec 10, 2024, 03:00 AM UTC· resolved Dec 11, 2024, 06:38 AM UTC

1. resolved Dec 13, 2024, 05:57 PM UTC

   A small percentage of image requests served by a single machine in the EU region experienced quality degradation between December 9th, 11:08 AM UTC - December 10th, 6:38 AM UTC

2. postmortem Dec 13, 2024, 05:58 PM UTC

   # Timeframe December 9th, 11:08 AM UTC - December 10th, 6:38 AM UTC # Impact A small percentage of image requests served by a single machine in the EU region experienced quality degradation. # Root Cause A hardware failure on one of the rendering machines resulted in images with artifacts being delivered to users. # Contributing Factors An absence of automated testing for faulty renders across active machines caused assets to be cached undetected. The lapse between when the issue was detected and when the issue began culminated in an unknown number of renders that needed to be purged from the cache. Along with inadequate cache tooling for purging affected images, these factors caused the issue to fully resolve in a longer timeframe than expected. # Corrective Actions To prevent this issue from happening in the future, we will: * Investigate and implement automated image quality testing for active rendering machines * Replace and refresh machines on a more frequent basis to minimize impact of single machine failures * Upgrade cache tooling for targeted issue resolution

Read the full incident report →

Started Nov 26, 2024, 02:55 PM UTC· resolved Nov 26, 2024, 05:37 PM UTC

1. investigating Nov 26, 2024, 02:55 PM UTC

   We are investigating an issue with SSL certificate renewals for a small subset of our custom domains. Reports indicate that SSL certificates have expired and images might not be accessible over https, when using custom domains

2. investigating Nov 26, 2024, 03:39 PM UTC

   We are continuing to investigate this issue.

3. resolved Nov 26, 2024, 05:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2024, 08:18 PM UTC· resolved Nov 15, 2024, 02:56 AM UTC

1. identified Nov 14, 2024, 08:18 PM UTC

   We have identified an issue with newly uploaded images not appearing in Asset Manager after being uploaded. Note that the upload will succeed and the asset can be served, but it may not appear in Asset Manager. We are applying a fix. The rendering service is not affected.

2. resolved Nov 15, 2024, 02:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 08, 2024, 06:55 AM UTC· resolved Nov 08, 2024, 04:48 PM UTC

1. investigating Nov 08, 2024, 06:55 AM UTC

   Our engineering team is currently investigating an issue with our Purge API, where requests to purge assets may not consistently result in the latest asset version being displayed. The rendering service remains unaffected, and we are working to identify the root cause to resolve this as quickly as possible.

2. resolved Nov 08, 2024, 04:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 06, 2024, 05:47 PM UTC· resolved Nov 06, 2024, 09:29 PM UTC

1. identified Nov 06, 2024, 05:47 PM UTC

   We have identified an issue with receiving support requests to [email protected] and are working on a fix. In the meantime, please use our contact form to reach support: https://dashboard.imgix.com/contact

2. resolved Nov 06, 2024, 09:29 PM UTC

   We have fixed the [email protected] email address and are processing our backlog of support requests. If you sent an email and have not received a reply until today, please reach back out to us through our contact form: https://dashboard.imgix.com/contact

Read the full incident report →

Started Oct 25, 2024, 05:16 PM UTC· resolved Oct 26, 2024, 08:40 PM UTC

1. investigating Oct 25, 2024, 05:16 PM UTC

   We are investigating a delay in the availability of our analytics data. API services are not impacted.

2. resolved Oct 26, 2024, 08:40 PM UTC

   This incident has been resolved.

Read the full incident report →