Cloudinary: Collections are not being detected
Affected components: Digital Asset Management (DAM)
Timeline of updates
- investigating
We are currently investigating a small subset of collections that are made public are not being detected.
- monitoring
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.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
33100304e7ce2be6…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Cloudinary, started 2025-08-13 19:33 UTC, resolved after 48 min, 3 update(s).
- Title
- Collections are not being detected
- Vendor
- Cloudinary
- Date
- URL
- https://rewindex.com/company/cloudinary/incidents/n5zhvvq60q5k
Cloudinary profileRecent Cloudinary incidentsAll outages on August 13, 2025Cloudinary in August 2025MarkdownJSON