imgix

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. identified 2026-09-01 16:36 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 2026-09-01 17:05 UTC

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

3. identified 2026-09-01 17:15 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 2026-09-01 18:06 UTC

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

5. monitoring 2026-09-01 18:31 UTC

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

6. resolved 2026-09-01 18:48 UTC

   This incident has been resolved.

7. postmortem 2026-09-11 19:25 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...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. identified 2026-09-01 15:30 UTC

   We've identified an increase in errors for new rendering requests due to an ongoing incident with an upstream provider.

2. identified 2026-09-01 15:35 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.

3. monitoring 2026-09-01 16:07 UTC

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

4. resolved 2026-09-01 16:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-08-14 04:53 UTC

   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. monitoring 2026-08-14 05:08 UTC

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

3. resolved 2026-08-14 05:28 UTC

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

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Purging

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-25 10:28 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 2026-06-25 11:27 UTC

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

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-04 14:44 UTC

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

2. identified 2026-06-04 14:52 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 2026-06-04 15:45 UTC

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

4. monitoring 2026-06-04 16:00 UTC

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

5. resolved 2026-06-04 16:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools, API Service

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-16 17:14 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 2026-04-16 17:27 UTC

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

3. resolved 2026-04-16 17:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-02-03 13:49 UTC

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

2. monitoring 2026-02-03 16:00 UTC

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

3. resolved 2026-02-03 16:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-26 16:15 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 2026-01-27 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-12 13:53 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...

2. monitoring 2026-01-12 14:37 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 2026-01-12 14:47 UTC

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

4. postmortem 2026-01-28 00:27 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. #...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: API Service

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-20 02:04 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 2025-11-20 04:14 UTC

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

3. resolved 2025-11-20 04:36 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.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-13 05:02 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.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-29 11:34 UTC

   We are currently investigating this issue.

2. identified 2025-10-29 11:56 UTC

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

3. monitoring 2025-10-29 12:25 UTC

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

4. resolved 2025-10-29 12:46 UTC

   This incident has been resolved.

5. postmortem 2025-11-11 00:18 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...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-28 17:48 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 2025-10-28 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-27 14:07 UTC

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

2. identified 2025-10-27 14:23 UTC

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

3. monitoring 2025-10-27 15:25 UTC

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

4. resolved 2025-10-27 15:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-21 09:26 UTC

   We are investigating reports of increased latency for new renders.

2. monitoring 2025-10-21 09:50 UTC

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

3. resolved 2025-10-21 10:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-10-08 23:00 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.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-17 20:53 UTC

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

2. resolved 2025-09-17 21:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure, Web Administration Tools, API Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 18:09 UTC

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

2. identified 2025-06-12 18:15 UTC

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

3. identified 2025-06-12 18:53 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 2025-06-12 20:26 UTC

   The service is restored. We are monitoring the situation.

5. identified 2025-06-12 20:38 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 2025-06-12 20:47 UTC

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

7. resolved 2025-06-12 20:52 UTC

   The service is completely restored.

8. postmortem 2025-06-20 19:03 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...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure, Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-20 15:40 UTC

   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. identified 2025-05-20 15:57 UTC

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

3. monitoring 2025-05-20 16:01 UTC

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

4. resolved 2025-05-20 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-04-24 12:29 UTC

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

2. monitoring 2025-04-24 14:10 UTC

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

3. resolved 2025-04-24 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-17 05:48 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 2025-03-18 18:56 UTC

   The root problem of the incident has been resolved. Some assets may still return an error. Please get in touch with support@imgix.com if you are experiencing issues

3. postmortem 2025-03-31 17:12 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...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Purging

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-16 06:21 UTC

   We have identified an issue with our purging service, causing new purge requests to be delayed in execution. (10mins+) Rendering services remain unaffected.

2. identified 2024-12-16 06:42 UTC

   The issue has been identified and we are working on a fix. To speed up processing of queued purge requests, we will have to temporarily disable purge requests for images that use any of the following AI-parameters: - bg-replace - compositions (any two or more ai features...

3. identified 2024-12-16 07:01 UTC

   Purge requests for images that use any of the below AI-parameters have been restored, but we are still observing longer purge times with a high queue. - bg-replace - compositions (any two or more ai features composed together, like bg-remove=true&upscale=true) We are looking at...

4. monitoring 2024-12-16 09:02 UTC

   A fix has been implemented and new purge requests should again complete within expected times. We are continuing to monitor the situation.

5. monitoring 2024-12-16 13:02 UTC

   We are continuing to monitor for any further issues.

6. resolved 2024-12-16 13:03 UTC

   The purge queue and purge time has been stable since the last provided update.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-12-10 03:00 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 2024-12-13 17:58 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...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure, Content Delivery Network

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-26 14:55 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 2024-11-26 15:39 UTC

   We are continuing to investigate this issue.

3. resolved 2024-11-26 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools, API Service

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-11-14 20:18 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 2024-11-15 02:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Purging

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-08 06:55 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...

2. resolved 2024-11-08 16:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-11-06 17:47 UTC

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

2. resolved 2024-11-06 21:29 UTC

   We have fixed the support@imgix.com 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

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-25 17:16 UTC

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

2. resolved 2024-10-26 20:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-10 18:44 UTC

   We are investigating issues with connecting to the imgix dashboard (https://dashboard.imgix.com). The imgix APIs are not affected by this incident.

2. identified 2024-10-10 18:55 UTC

   We have identified the issue and are working on a fix for logging into the dashboard. The imgix APIs (Rendering, Video and the Management API) are all working normally.

3. monitoring 2024-10-10 19:40 UTC

   A fix has been implemented, restoring access to the dashboard. We are monitoring the results.

4. resolved 2024-10-10 20:29 UTC

   This incident is resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-25 16:08 UTC

   We identified an issue with the support contact form not working. Please email support@imgix.com for any support request while we look into fixing the contact form.

2. resolved 2024-09-25 17:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-09-13 04:48 UTC

   We have resolved the issue where some browsers received unsupported image formats, affecting a small number of renders. The changes have been rolled back, and services are fully restored

2. postmortem 2024-09-24 22:30 UTC

   ## What happened? On September 12, 2024, imgix deployed a change to optimize image delivery for Safari browsers. This update inadvertently impacted a small number of browsers by delivering image formats they could not display. imgix identified the issue on September 14 and...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-08-07 20:15 UTC

   Dashboard and documentation tools were affected by an upstream service provider outage. Rendering services were not impacted.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Newark (EWR)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-07-08 19:22 UTC

   We are currently seeing an issue with an upstream service provider. Images served from the Newark (EWR) node may intermittently return 502s. All other POP nodes are working as expected.

2. monitoring 2024-07-08 19:47 UTC

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

3. resolved 2024-07-08 20:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-06-17 00:21 UTC

   We are currently investigating elevated render error rates for uncached derivative images. We will update once when we obtain more information. Previously cached derivatives are not impacted.

2. identified 2024-06-17 00:50 UTC

   The issue has been identified and our engineering team is developing a fix.

3. identified 2024-06-17 00:51 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2024-06-17 01:06 UTC

   A fix has been implemented and error rates are returning to normal. We are continuing to monitor the service.

5. resolved 2024-06-17 01:19 UTC

   This incident has been resolved.

6. postmortem 2024-06-21 23:54 UTC

   ## What happened? On June 17, 2024, at 00:00 UTC, imgix experienced an extreme spike in requests to our render stack. This unexpected surge caused a failure in our auto-scaling infrastructure, leading to an inability to manage all incoming traffic effectively. A fix was...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-05-23 19:44 UTC

   On May 23rd, 19:19 UTC, we identified an issue affecting our rendering services due to a caching problem. This caused elevated rendering times and intermittent failures for some users. Our engineering team quickly diagnosed the issue and implemented a fix at 19:36 UTC. We are...

2. resolved 2024-05-23 19:50 UTC

   This incident has been resolved.

3. postmortem 2024-05-24 20:50 UTC

   # **Postmortem** # **What happened?** On May 23, 2024, at 19:23 UTC, an increased load on the rendering infrastructure was detected. Actions were taken to scale out our system to handle the additional traffic. This incident was resolved at 19:36. # **How were customers...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-05-09 05:13 UTC

   We have identified an issue that is causing assets to not display in the Asset Manager within the imgix dashboard. A fix has been deployed which is gradually restoring the Asset Manager. We expect all assets to be visible again in the Asset Manager within a few hours. The imgix...

2. resolved 2024-05-09 15:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-04-09 19:13 UTC

   We are investigating issues with creating Microsoft Azure Sources. All images from existing Azure sources are unaffected.

2. resolved 2024-04-09 22:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-21 11:30 UTC

   We have identified an issue that was preventing some newly fetched Origin images from being inserted into our Origin image cache, causing the same images to be re-fetched multiple times for new render requests. The impact time (UTC) was 3/21 20:30 - 3/29 0:50. The issue is...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Purging

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-20 21:35 UTC

   Our engineering team is investigating a delay in purge requests. The rendering service is not impacted.

2. resolved 2024-02-20 21:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-02-20 17:00 UTC

   We are investigating issues with imgix administration tools. There are reports of problems with calling our imgix upload API. The rendering service is not affected.

2. postmortem 2024-03-08 22:58 UTC

   # Postmortem # **What happened?** On Feb 20, 2024, at 19:00 UTC, Uploads using the \`/api/v1/sources/upload/\` API endpoint experienced slowness and some timeouts during this time. The issue had been completely resolved by Feb 21, 2024, 20:00 UTC. # **How were customers...

Excerpts are shortened. Read the full incident on imgix's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-01-22 21:00 UTC

   We have identified the issue and are currently applying a fix. The rendering service is not affected.

2. postmortem 2024-02-26 17:42 UTC

   # Postmortem # **What happened?** On January 22, 2024, 07:38 UTC, some Web Folder requests to the imgix service began to return a `403` response. By 11:56 UTC, the issue had been completely resolved. # **How were customers impacted?** Between 07:38 UTC and 11:36 UTC, several...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools, API Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-11-11 08:06 UTC

   We have identified the issue and are currently applying a fix. The rendering service is not affected.

2. identified 2023-11-11 08:06 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2023-11-11 08:07 UTC

   We are monitoring issues with the Management API, specifically with PATCH requests to an asset. The rendering service is not affected.

4. monitoring 2023-11-11 18:41 UTC

   We are continuing to monitor for any further issues.

5. resolved 2023-11-11 18:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-23 22:34 UTC

   We are investigating an issue affecting a small percentage of renders.

2. monitoring 2023-10-23 23:15 UTC

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

3. resolved 2023-10-23 23:32 UTC

   This incident has been resolved.

4. postmortem 2023-11-02 18:52 UTC

   # What happened? On October 23, 2023, between 21:43 UTC and 23:14 UTC, imgix experienced a partial outage affecting images served from the Rendering API. During this time, a small percentage \(<0.45% on average\) of non-cached requests returned a server error. A fix was...

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: API Service

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-07 02:19 UTC

   We are investigating issues with patching requests to the Management API. The rendering service is not affected.

2. identified 2023-08-07 03:50 UTC

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

3. monitoring 2023-08-07 10:49 UTC

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

4. resolved 2023-08-07 11:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools, API Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-05 23:39 UTC

   We are investigating issues of deploying new/updated Source configurations. The rendering service is not affected by this incident.

2. monitoring 2023-07-06 00:02 UTC

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

3. resolved 2023-07-06 00:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-06-30 19:48 UTC

   The issue has been identified and our engineering team is developing a fix.

2. resolved 2023-06-30 20:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: API Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-31 23:38 UTC

   We are investigating issues with requests to the Management API. The rendering service is not affected.

2. identified 2023-05-31 23:51 UTC

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

3. monitoring 2023-06-01 00:55 UTC

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

4. resolved 2023-06-01 01:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Web Administration Tools

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-25 18:25 UTC

   We are investigating reports of Dashboard unavailability. The rendering service is not affected by this incident.

2. monitoring 2023-05-25 19:58 UTC

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

3. resolved 2023-05-25 20:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-18 15:52 UTC

   We are currently investigating reports of intermittent rendering errors affecting a small percentage of images.

2. monitoring 2023-05-18 15:56 UTC

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

3. investigating 2023-05-18 16:28 UTC

   We are currently investigating this issue.

4. monitoring 2023-05-18 16:57 UTC

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

5. monitoring 2023-05-18 16:58 UTC

   We are continuing to monitor for any further issues.

6. resolved 2023-05-18 17:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on imgix's status page.

Affected: Rendering Infrastructure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-05-01 14:20 UTC

   We are currently investigating reports of intermittent 5xx errors causing some images to initially return a 5xx error.

2. identified 2023-05-01 14:47 UTC

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

3. monitoring 2023-05-01 15:08 UTC

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

4. resolved 2023-05-01 15:35 UTC

   This incident has been resolved.

5. postmortem 2023-05-11 20:37 UTC

   # What happened On May 1st, 2023, between the hours of 08:23 UTC and 15:08 UTC, imgix experienced intermittent errors affecting a small percentage of non-cached renders. # How were customers impacted? During the affected period, a small percentage of requests to the Rendering...

Excerpts are shortened. Read the full incident on imgix's status page.