We are investigating increased latency for first time renders in EU

What to do

• Check whether you use imgix Rendering Infrastructure in eu. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 12m it lasted.

  Anything that failed between 2025-10-29 11:34 UTC and 2025-10-29 12:46 UTC may need a replay.

• Subscribe to imgix's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=imgix works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from imgix 5

1. investigatingOct 29, 2025, 11:34 AM UTC

   We are currently investigating this issue.

   provider

2. identifiedOct 29, 2025, 11:56 AM UTC

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

   provider

3. monitoringOct 29, 2025, 12:25 PM UTC

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

   provider

4. resolvedOct 29, 2025, 12:46 PM UTC

   This incident has been resolved.

   provider

5. postmortemNov 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.