Cloudinary incident: Collections are not being detected

Affected components

• Digital Asset Management (DAM)

1. resolvedAug 13, 2025, 20:21 UTC

   This incident has been resolved.

2. monitoringAug 13, 2025, 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.

3. investigatingAug 13, 2025, 19:33 UTC

   We are currently investigating a small subset of collections that are made public are not being detected.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudinary's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

How often does Cloudinary have incidents?

Cloudinary reported 6 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 4h 35m. See Cloudinary's uptime and incident history