- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Cloudinary. 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-10-05 12:20 UTC and 2026-10-05 12:00 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 1
- resolved
Between approximately 11:29 and 12:02 UTC on October 5, 2026, usage reports in the Cloudinary Console Dashboard were unavailable. The issue has been resolved, and usage reporting functionality has been fully restored.
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-62f1e286c6
Is Cloudinary still down?
No, this incident was resolved 2026-10-05 12:00 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
0m, from 2026-10-05 12:20 UTC to 2026-10-05 12:00 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.