- Level
- confirmed
- Worst impact
- Degraded
- Components
- Flow Engine
- Down Index
- 34of 100
What to do
Check whether you use Cloudinary Flow Engine. 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 15h 17m it lasted.
Anything that failed between 2026-06-16 15:19 UTC and 2026-06-17 06:36 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 experiencing delays in MediaFlows execution. Some flows may not run immediately after being triggered. Our team is actively investigating the issue. We expect all affected flow runs to be processed, though with delays. We will provide further updates as more information becomes available.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-400ab8f137
Is Cloudinary still down?
No, this incident was resolved 2026-06-17 06:36 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
15h 17m, from 2026-06-16 15:19 UTC to 2026-06-17 06:36 UTC, by the times Cloudinary posted.
What was affected?
Cloudinary named Flow Engine.
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.