- Level
- confirmed
- Worst impact
- Degraded
- Components
- Digital Asset Management (DAM)
- Down Index
- 28of 100
What to do
Check whether you use Cloudinary Digital Asset Management (DAM). 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 48m it lasted.
Anything that failed between 2025-08-13 19:33 UTC and 2025-08-13 20:21 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
- investigating
We are currently investigating a small subset of collections that are made public are not being detected.
provider
- monitoring
On Wednesday, August 13, 2025, at 19:48:15 UTC, our team identified the cause of the issue with the collections and reverted to a known working version. We expect the Collection's functionality to be fully restored, and we are continually monitoring the status.
provider
- resolved
This incident 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-c162c94a36
Is Cloudinary still down?
No, this incident was resolved 2025-08-13 20:21 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
48m, from 2025-08-13 19:33 UTC to 2025-08-13 20:21 UTC, by the times Cloudinary posted.
What was affected?
Cloudinary named Digital Asset Management (DAM).
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.