outages.live
Live
I

imgix

imgix is operational

Checked 57 s ago Operational

History

90 days agoToday

Incidents in 90 days

3

Days with an incident

2

Median duration

51 min

Longest incident

2 h 13 min

Components

85
Rendering Infrastructure Operational
90 days ago2 days with an incidentToday
Web Administration Tools Operational
90 days agoNo incidentsToday
API Service Operational
90 days agoNo incidentsToday
Sandbox Operational
90 days agoNo incidentsToday
Purging Operational
90 days agoNo incidentsToday
Docs Operational
90 days agoNo incidentsToday
Stripe API Operational
90 days agoNo incidentsToday

Content Delivery Network

Content Delivery Network Operational
90 days agoNo incidentsToday
Auckland (AKL) Operational
90 days agoNo incidentsToday
Brisbane (BNE) Operational
90 days agoNo incidentsToday
Hong Kong (HKG) Operational
90 days agoNo incidentsToday
Osaka (ITM) Operational
90 days agoNo incidentsToday
Melbourne (MEL) Operational
90 days agoNo incidentsToday
Tokyo (NRT) Operational
90 days agoNo incidentsToday
Perth (PER) Operational
90 days agoNo incidentsToday
Singapore (SIN) Operational
90 days agoNo incidentsToday
Sydney (SYD) Operational
90 days agoNo incidentsToday
Wellington (WLG) Operational
90 days agoNo incidentsToday
Amsterdam (AMS) Operational
90 days agoNo incidentsToday
Stockholm (BMA) Operational
90 days agoNo incidentsToday
Paris (CDG) Operational
90 days agoNo incidentsToday
Frankfurt (FRA) Operational
90 days agoNo incidentsToday
Frankfurt (HHN) Operational
90 days agoNo incidentsToday
London (LCY) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 1, 2026

Duration2 h 13 min16:36 to 18:48Increased errors for new render requestsPartial outage

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

Duration51 min15:30 to 16:22Increased errors for new render requestsPartial outage

This incident has been resolved.

Aug 14, 2026

Duration35 min04:53 to 05:28Increased errors for new render requestsDegraded

While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident 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.

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

RSS
https://outages.cc/feed.xml?providers=imgix
Slack
/feed subscribe https://outages.cc/feed.xml?providers=imgix

Go from tracking outages to fixing production issues with Polylane.

Try Polylane