imgix logo

Is imgix Down?

CDN & EdgeLive status, outages, and incident history

No. imgix is up right now.

Every monitored imgix system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · 60s while moving

Know the moment imgix breaks

imgix is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official imgix status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

imgix Component Status

The main imgix systems on this page. All 85 are operational right now.

85operational
API Service
Operational
Content Delivery Network » Amsterdam
Operational
Content Delivery Network » Ashburn
Operational

82 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Content Delivery Network » Atlanta, Content Delivery Network » Auckland, Content Delivery Network » Boston, Content Delivery Network » Brisbane, Content Delivery Network » Buenos Aires, Content Delivery Network » Cape Town, Content Delivery Network » Chennai, Content Delivery Network » Chicago, Content Delivery Network » Columbus, Content Delivery Network » Content Delivery Network, Content Delivery Network » Copenhagen, and 71 more.

See all of them free

Component statuses may change independently during partial outages.

Recent imgix Outages & Incidents

Incident history from the official imgix status page, including resolution updates.

Increased errors for new render requestsResolved Sep 1, 2026 · 2h 12mResolved

## 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. --- [2026-09-01T11:48:57.733-07:00] (resolved) This incident has been resolved. --- [2026-09-01T11:31:45.032-07:00] (monitoring) Error rates are back to normal. We will continue to monitor the service. --- [2026-09-01T11:06:44.490-07:00] (identified) We are observing improved error rates across the service. We will continue to monitor the situation. --- [2026-09-01T10:15:22.781-07:00] (identified) 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. --- [2026-09-01T10:05:55.615-07:00] (identified) We are continuing to monitor error rates while investigating potential failover options for this incident. --- [2026-09-01T09:36:25.121-07:00] (identified) 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.

Increased errors for new render requestsResolved Sep 1, 2026 · 51 minResolved

This incident has been resolved. --- [2026-09-01T09:07:13.399-07:00] (monitoring) Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud. --- [2026-09-01T08:35:08.695-07:00] (identified) 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. --- [2026-09-01T08:30:42.201-07:00] (identified) 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 requestsResolved Aug 14, 2026 · 34 minResolved

While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved. --- [2026-08-13T22:08:51.086-07:00] (monitoring) Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud. --- [2026-08-13T21:53:52.472-07:00] (identified) 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.

imgix Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a imgix incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live imgix Outage Reports

Problems reported by engineers using imgix. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No imgix problems reported yet.

Something wrong with imgix on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About imgix

imgix exposes 88 monitored components on its status page at status.imgix.com — Rendering Infrastructure, Content Delivery Network and Google Cloud Storage among them. Follow imgix downtime, degraded performance and resolved incidents here, with uptime history alongside your other CDN and edge delivery services.

Over the past 30 days, PulsAPI has measured imgix uptime at 100.00%. Response times, incident history, and SLA tracking for imgix are available on the PulsAPI dashboard.

imgix Status FAQ

Is imgix down right now?

The verdict at the top of this page comes from the latest poll of the official imgix status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if imgix is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until imgix recovers.

How do I check imgix uptime history?

PulsAPI tracks imgix uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever imgix changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect imgix outages?

PulsAPI reads the official imgix status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual imgix components?

Yes. PulsAPI monitors 85 individual imgix components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when imgix goes down?

Yes. Create a free account and subscribe to imgix: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with imgix to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot imgix problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor imgix?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so imgix plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track imgix with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services