- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Media Transformation API - AP
- Down Index
- 40of 100
What to do
Check whether you use Cloudinary Media Transformation API - AP. 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 2h 24m it lasted.
Anything that failed between 2026-07-12 10:20 UTC and 2026-07-12 12:44 UTC may need a replay.Subscribe to Cloudinary's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudinary works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudinary 2
- monitoring
An issue affecting requests that included the g_auto transformation resulted in elevated error rates beginning at approximately 09:00 UTC on Sunday, July 12. The issue has been resolved, and we are continuing to monitor.
provider
- resolved
The incident has been resolved. Services have returned to normal, and all previously affected URLs are now functioning correctly.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e0ac35dad7
Is Cloudinary still down?
No, this incident was resolved 2026-07-12 12:44 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
2h 24m, from 2026-07-12 10:20 UTC to 2026-07-12 12:44 UTC, by the times Cloudinary posted.
What was affected?
Cloudinary named Media Transformation API - AP.
What caused it?
Cloudinary hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudinary's official status page, https://status.cloudinary.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.