Is imgix down?
Last checked just nowNo incidents right now.
imgix is operational right now. Last checked just now; the most recent incident resolved 60d ago.
Real-time imgix status, recent outages, and incident history: pulled directly from imgix's official status page at status.imgix.com every 5 minutes. Pingoru tracks 85 imgix services and has captured 3 incidents in the last 90 days (99.97% uptime). Get email, Slack, Discord, or webhook alerts the moment imgix reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Rendering Infrastructure
Timeline · 7 updates
- 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.
- identified · Sep 01, 2026, 05:05 PM UTC
We are continuing to monitor error rates while investigating potential failover options for this incident.
- 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.
- identified · Sep 01, 2026, 06:06 PM UTC
We are observing improved error rates across the service. We will continue to monitor the situation.
- monitoring · Sep 01, 2026, 06:31 PM UTC
Error rates are back to normal. We will continue to monitor the service.
- resolved · Sep 01, 2026, 06:48 PM UTC
This incident has been resolved.
- 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.
Latest: ## 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 powe…
-
- Rendering Infrastructure
Timeline · 4 updates
- identified · Sep 01, 2026, 03:30 PM UTC
We've identified an increase in errors for new rendering requests due to an ongoing incident with an upstream provider.
- identified · Sep 01, 2026, 03:35 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.
- monitoring · Sep 01, 2026, 04:07 PM UTC
Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud.
- resolved · Sep 01, 2026, 04:22 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Rendering Infrastructure
Timeline · 3 updates
- identified · Aug 14, 2026, 04:53 AM 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.
- monitoring · Aug 14, 2026, 05:08 AM UTC
Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud.
- resolved · Aug 14, 2026, 05:28 AM UTC
While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
Latest: While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 85 components checked every 5 minutesThe longest incident in the last year, Delay in Purge requests on November 13, 2025, ran for 24 hours.
Most affected components, last 12 months
- Rendering Infrastructure4
- Web Administration Tools4
- API Service2
- Purging1
Latest incidents
- Increased errors for new render requests
We have identified a correlation with an ongoing Google Cloud incident, which reports elevated packet loss and errors for multiple services. We will continue…
- Increased errors for new render requests
We've identified an increase in errors for new rendering requests due to an ongoing incident with an upstream provider.
- Increased errors for new render requests
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…
- Started Sep 01, 2026, 04:36 PM UTC · Resolved Sep 01, 2026, 06:48 PM UTC · 2h 12m
- Started Sep 01, 2026, 03:30 PM UTC · Resolved Sep 01, 2026, 04:22 PM UTC · 51m
- Started Aug 14, 2026, 04:53 AM UTC · Resolved Aug 14, 2026, 05:28 AM UTC · 34m