Imgix partial outage and rendering errors

What to do

• Check whether your product depends on DatoCMS. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-02 13:11 UTC and 2026-09-02 13:11 UTC may need a replay.

• Subscribe to DatoCMS's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=datocms works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DatoCMS 1

1. resolvedSep 2, 2026, 1:11 PM UTC

   Resolved — This is now resolved. A date handling bug was hiding the Third-Party Components section whenever a provider had an ongoing incident, and several of the provider feeds we relied on had been discontinued upstream. Both are fixed, and the section now reads each provider's status API directly. Investigating — Separate from the Imgix outage, our status page (this current page) is not correctly showing our upstream provider statuses. We are investigating. Resolved — Earlier today, from approximately 15:00 to 19:00 UTC, our upstream image provider (Imgix) had a partial outage that resulted in occasional rendering errors for some customers in some situations. The issue should now be resolved (see details at https://status.imgix.com/incidents/ch5p1nlqnckd and https://status.imgix.com/incidents/7n22y1mt7jw1

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.