- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 34of 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 12h 16m it lasted.
Anything that failed between 2026-07-20 23:09 UTC and 2026-07-21 11:25 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 investigating an issue affecting connections to the Cloudinary MCP Connector. Users may receive a 502 Bad Gateway error.
provider
- monitoring
A fix has been issued to address the connection failures with our MCP connector, and we are actively monitoring to ensure ongoing stability.
provider
- resolved
The recent issue impacting the Cloudinary MCP Connector has been successfully resolved. We can confirm that all services are now back to normal operation.
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-2d019450bd
Is Cloudinary still down?
No, this incident was resolved 2026-07-21 11:25 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
12h 16m, from 2026-07-20 23:09 UTC to 2026-07-21 11:25 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.