- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Cloudinary. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 26m it lasted.
Anything that failed between 2025-06-03 16:33 UTC and 2025-06-03 18:59 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 3
- identified
Around ~3 hours ago, the super resolution model was deployed to fix a customer issue. This introduced possible degradation in some super resolution results. We are working on the fix.
provider
- monitoring
A fix has been deployed, and we are monitoring.
provider
- resolved
The issue has been resolved.
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-befa174bbb
Is Cloudinary still down?
No, this incident was resolved 2025-06-03 18:59 UTC. For Cloudinary's live state, see https://down.guide/providers/cloudinary.
How long did it last?
2h 26m, from 2025-06-03 16:33 UTC to 2025-06-03 18:59 UTC, by the times Cloudinary posted.
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.