- Level
- confirmed
- Worst impact
- Degraded
- Components
- Third-Party - Add-ons
- Down Index
- 34of 100
What to do
Check whether you use Cloudinary Third-Party - Add-ons. 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 13h 34m it lasted.
Anything that failed between 2025-06-17 10:04 UTC and 2025-06-17 23:38 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
From 9:30am UTC, customers who are using the Aspose addon might experience some errors. We are actively working on it and will update with any insights.
provider
- identified
The issue appears to be related to timeouts when awaiting a response from the Aspose service. Failed requests are retried automatically and most succeed upon retry, so the Add-on may appear to work as normal but with slower responses than usual. We're continuing to monitor the issue and will provide updates when we have more information to share.
provider
- resolved
At approximately Jun 17 22:10:46 UTC 2025, the Aspose add-on intermittent issue has been resolved. Customers should no longer experience issues with file-related conversions when calling the Aspose service.
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-154519ee17
Is Cloudinary still down?
No, this incident was resolved 2025-06-17 23:38 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
13h 34m, from 2025-06-17 10:04 UTC to 2025-06-17 23:38 UTC, by the times Cloudinary posted.
What was affected?
Cloudinary named Third-Party - Add-ons.
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.