imgix Outage History

11 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded imgix Incident

imgix incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 1, 2026Increased 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…2h 12mResolved
Sep 1, 2026Increased errors for new render requestsThis incident has been resolved.51 minResolved
Aug 14, 2026Increased errors for new render requestsWhile Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.34 minResolved
Jun 25, 2026Delayed purge request processingThis incident has been resolved. All previously submitted purge requests have been processed.58 minResolved
Jun 4, 2026Increased errors for new render requests (Rendering & Legacy video APIs)This incident has been resolved.2h 9mResolved
Apr 16, 2026Issues with Imgix web toolsThis incident has been resolved.28 minResolved
Feb 3, 2026Asset Manager errors when uploading to an Azure SourceThis incident has been resolved.2h 32mResolved
Jan 26, 2026Investigating errors with plan upgrades through the dashboard.This incident has been resolved.8h 43mResolved
Jan 12, 2026Uploading errors in Asset Manager# Summary Between 2026-01-09 21:26 UTC and 2026-01-12 14:18 UTC, some asset uploads returned an upload failure error in Asset Manager despite the uploads completing successfully. Additionally, legacy video customers…53 minResolved
Nov 20, 2025Delayed Reports for CDN and Error LogsThe backfill for the CDN and Error Log reports has been completed. You should now be able to download the reports from the Dashboard or via the API as usual.2h 32mResolved
Nov 13, 2025Delay in Purge requestsPurge requests were not executed between 2025-11-12 23:00 UTC and 2025-11-13 05:00 UTC. The issue has been mitigated, and purge functionality has been fully restored. All purge requests that failed during the impact…0 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next imgix incident opens instead, at the point where knowing still changes what you do.

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

How to Read This imgix Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before imgix acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single imgix outage in this window ran 8h 43m, against a mean recovery of 1h 59m. If you depend on imgix in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.