We started checking imgix on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when imgix reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what imgix's own status page declared. Below it, any public chatter we saw about imgix and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what imgix's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about imgix in the last 24 hours, which is not evidence that nothing is wrong.
imgix's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is imgix's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention imgix next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
729
US-West
100.00%
578
Europe
100.00%
528
Asia-Pacific
100.00%
320
Their declared record
imgix's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Increased errors for new render requestsPartial outage
Sep 1, 2026, 4:36 PM UTC to Sep 1, 2026, 6:48 PM UTC (2h 13m)postmortem published
their latest update (Sep 11, 2026, 7: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 …
Increased errors for new render requestsPartial outage
Sep 1, 2026, 3:30 PM UTC to Sep 1, 2026, 4:22 PM UTC (51 min)resolved
their latest update (Sep 1, 2026, 4:22 PM UTC): This incident has been resolved.
Increased errors for new render requestsMinor incident
Aug 14, 2026, 4:53 AM UTC to Aug 14, 2026, 5:28 AM UTC (35 min)resolved
their latest update (Aug 14, 2026, 5: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.
Delayed purge request processingMinor incident
Jun 25, 2026, 10:28 AM UTC to Jun 25, 2026, 11:27 AM UTC (59 min)resolved
their latest update (Jun 25, 2026, 11:27 AM UTC): This incident has been resolved. All previously submitted purge requests have been processed.
Increased errors for new render requests (Rendering & Legacy video APIs)Partial outage
Jun 4, 2026, 2:44 PM UTC to Jun 4, 2026, 4:54 PM UTC (2h 10m)resolved
their latest update (Jun 4, 2026, 4:54 PM UTC): This incident has been resolved.
Issues with Imgix web toolsPartial outage
Apr 16, 2026, 5:14 PM UTC to Apr 16, 2026, 5:43 PM UTC (29 min)resolved
their latest update (Apr 16, 2026, 5:43 PM UTC): This incident has been resolved.
Asset Manager errors when uploading to an Azure SourceMinor incident
Feb 3, 2026, 1:49 PM UTC to Feb 3, 2026, 4:21 PM UTC (2h 32m)resolved
their latest update (Feb 3, 2026, 4:21 PM UTC): This incident has been resolved.
Investigating errors with plan upgrades through the dashboard.Minor incident
Jan 26, 2026, 4:15 PM UTC to Jan 27, 2026, 12:58 AM UTC (8h 44m)resolved
their latest update (Jan 27, 2026, 12:58 AM UTC): This incident has been resolved.
Uploading errors in Asset ManagerMinor incident
Jan 12, 2026, 1:53 PM UTC to Jan 12, 2026, 2:47 PM UTC (53 min)postmortem published
their latest update (Jan 28, 2026, 12:27 AM UTC): # 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 experienced transcoding delays as a result of the incident.
#…
Delayed Reports for CDN and Error LogsAll systems operational
Nov 20, 2025, 2:04 AM UTC to Nov 20, 2025, 4:36 AM UTC (2h 33m)resolved
their latest update (Nov 20, 2025, 4:36 AM UTC): The 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.
Showing the 10 most recent of 50 incidents imgix has declared in the history we hold.
These entries are imgix's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
imgix's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.