Cloudinary incident

Failed transformation requests with combination of Strict Transformations and Auto-Upload

Minor Resolved View vendor source →

Cloudinary experienced a minor incident on December 15, 2025 affecting Media Transformation API - US and Media Transformation API - AP and 1 more component, lasting 4h 22m. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2025, 03:10 PM UTC
Resolved
Dec 15, 2025, 07:32 PM UTC
Duration
4h 22m
Detected by Pingoru
Dec 15, 2025, 03:10 PM UTC

Affected components

Media Transformation API - USMedia Transformation API - APUpload API - USUpload API - EUUpload API - APAdmin API - EU

Update timeline

  1. identified Dec 15, 2025, 03:10 PM UTC

    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

  2. identified Dec 15, 2025, 04:51 PM UTC

    We are working on deploying a fix for this issue; we'll provide a further update after the deployment is complete

  3. monitoring Dec 15, 2025, 05:42 PM UTC

    A fix has been deployed and affected requests should now be working as expected. We'll resolve the incident after some further monitoring.

  4. resolved Dec 15, 2025, 07:32 PM UTC

    This incident has been resolved.