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

What to do

• Check whether you use Cloudinary Media Transformation API - US, Media Transformation API - AP, Upload API - US, Upload API - EU and 2 more in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 22m it lasted.

  Anything that failed between 2025-12-15 15:10 UTC and 2025-12-15 19:32 UTC may need a replay.

• Subscribe to Cloudinary's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=cloudinary works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudinary 4

1. identifiedDec 15, 2025, 3: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

   provider

2. identifiedDec 15, 2025, 4:51 PM UTC

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

   provider

3. monitoringDec 15, 2025, 5: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.

   provider

4. resolvedDec 15, 2025, 7:32 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.