Collections are not being detected
Aug 13, 19:33 UTCAug 13, 20:21 UTC
Duration
48m
Impact
Minor
Root cause
Not disclosed
Cloudinary, 90 days
5 incidents
Affected
Digital Asset Management (DAM)
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 13, 20:21 UTC
This incident has been resolved.
- Monitoring · Aug 13, 19:52 UTC
On Wednesday, August 13, 2025, at 19:48:15 UTC, our team identified the cause of the issue with the collections and reverted to a known working version. We expect the Collection's functionality to be fully restored, and we are continually monitoring the status.
- Investigating · Aug 13, 19:33 UTC
We are currently investigating a small subset of collections that are made public are not being detected.
More from Cloudinary
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Aug 1317:04 UTC | Media Library / asset visibility | minor | 24h 41m |
| Jul 2913:35 UTC | Add-on installations are unavailable | minor | 1h 22m |
| Jul 2023:09 UTC | Connection failures with the Cloudinary MCP Connector | minor | 12h 16m |
| Jul 1410:17 UTC | Some customers experience authentication problems when accessing Cloudinary's Figma plugin | minor | 0m |
| Jul 1210:20 UTC | Elevated Error Rates for Requests Using g_auto | major | 2h 24m |
| Jun 1615:19 UTC | Delays in MediaFlows | minor | 15h 17m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.