Increased errors for new render requests
While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
The latest update from imgix.
State
Resolved
Started
80 d ago
2026-08-14 04:53 UTC
Lasted
35 min
until 2026-08-14 05:28 UTC
Worst impact
Degraded
Timeline
3 updatesIdentified
15 min 43%
Monitoring
20 min 57%
Updates
Times in UTCAs posted by imgix
While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud.
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.
Affected components
1imgix in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
2
Median duration
51 min
This incident
32% shorter than the median
Other imgix incidents
All incidents
imgix·Increased errors for new render requests
## 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, tra
imgix·Increased errors for new render requests
This incident has been resolved.
Follow imgix
Your coding agent knows when imgix is down, and tells you when a failure is theirs, not yours. You can also get imgix incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "imgix" and tell me if imgix has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=imgix/feed subscribe https://outages.cc/feed.xml?providers=imgixFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane