- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks / HTTP notifications - US
- Regions
- us
- Down Index
- 38of 100
What to do
Check whether you use Cloudinary Webhooks / HTTP notifications - US in us. 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 29m it lasted.
Anything that failed between 2025-10-16 07:52 UTC and 2025-10-16 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 2
- monitoring
We experienced a failure in delivering webhook notifications starting at around 05:57 UTC, lasting approximately 1.5 hours. The issue has been resolved, and we are currently monitoring to ensure system stability.
provider
- resolved
We've confirmed that any backlog was processed and the system is stable.
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-c9ee58a9c1
Is Cloudinary still down?
No, this incident was resolved 2025-10-16 20:21 UTC. For Cloudinary's live state, see https://down.guide/cloudinary.
How long did it last?
12h 29m, from 2025-10-16 07:52 UTC to 2025-10-16 20:21 UTC, by the times Cloudinary posted.
What was affected?
Cloudinary named Webhooks / HTTP notifications - US in us.
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.