Cloudinary reported this minor-impact incident on its official status page on Dec 15, 2025, 15:10 UTC. It was resolved after 4h 22m.
Right now Cloudinary is operational. Live Cloudinary status →
This incident has been resolved.
A fix has been deployed and affected requests should now be working as expected. We'll resolve the incident after some further monitoring.
We are working on deploying a fix for this issue; we'll provide a further update after the deployment is complete
We are currently working to resolve a reported issue when using both Strict Transformations and the Auto-Upload feature. Until we resolve the issue, you may see "Transformation ... is not allowed" errors on requests that should trigger an auto upload from a remote URL or bucket. Until we resolve the issue, you can work around the issue by temporarily disabling Strict Transformations or using another method to allow the transformation to proceed such as signing the URL or adding an Strict Referral Domain: https://cloudinary.com/documentation/control_access_to_media#strict_transformations
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.
Overlapping incidents aren't necessarily related.
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