Cloudinary outage history

On October 23, 2026, the Ruby project released security fixes for vulnerabilities in its regular expression engine (CVE-2026-89078, CVE-2026-93577, CVE-2026-97229, CVE-2026-110264). Cloudinary upgraded its core platform, including its upload, transformation, and delivery APIs and Console, to the patched Ruby version on the same day. Our review found no evidence of exploitation and no impact on customers or customer data. No action is required on your part for the Cloudinary platform. Customers who use Ruby in their own applications, including with the Cloudinary Ruby SDK, should update Ruby in their environments to a patched release (3.3.13, 3.4.12, 4.0.9 or later).

Regarding the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 Cloudinary’s core platform, including its upload, transformation, and delivery APIs and Console, does not use PHP and is not affected by these vulnerabilities. Please note that customers who use the Cloudinary PHP SDK in their own applications should update PHP in their respective environments

We are currently investigating an issue affecting the Cloudinary web UI. Some users may be unable to log in or use the Console and Media Library. Our engineering team is actively working on it. Image and video delivery, uploads and API requests using API credentials are not affected. We will post another update as soon as we have more information.

A fix has been implemented for the issue affecting the UI and console. We are now monitoring the system to ensure stability. Users who still see errors should refresh the page and log in again.

This incident has been resolved. The UI and console, including login, is operating normally. We apologize for the inconvenience.

Between approximately 11:29 and 12:02 UTC on October 5, 2026, usage reports in the Cloudinary Console Dashboard were unavailable. The issue has been resolved, and usage reporting functionality has been fully restored.

We are currently investigating increased error rates in the EU region affecting uploads (eager transformations), transformations, and delivery. The issue began at approximately 06:15 UTC. We will provide updates as more information becomes available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Since approximately 12:30 UTC, some users may experience issues where assets not appearing when browsing folders in the Media Library. Affected assets remain available and may still be accessible through search. Our team is investigating the issue and working to restore normal folder visibility. We will provide another update as soon as more information is available.

We have identified the root cause of the issue affecting asset visibility in the Media Library. Our engineering team is actively working on a resolution. Asset delivery is not impacted. We will provide another update as soon as more information is available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Since approximately 13:50 UTC, users have been unable to install add-ons. Installation attempts are failing and may display an “Installation failed” message. Our team is investigating the issue and working to restore installation functionality. We will provide another update as soon as more information is available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating an issue affecting connections to the Cloudinary MCP Connector. Users may receive a 502 Bad Gateway error.

A fix has been issued to address the connection failures with our MCP connector, and we are actively monitoring to ensure ongoing stability.

The recent issue impacting the Cloudinary MCP Connector has been successfully resolved. We can confirm that all services are now back to normal operation.

Due to a change in security parameters, some customers are experiencing failures when attempting to sign in to Cloudinary via the Cloudinary Figma plugin (https://www.figma.com/community/plugin/1451492041396730459/cloudinary)

An issue affecting requests that included the g_auto transformation resulted in elevated error rates beginning at approximately 09:00 UTC on Sunday, July 12. The issue has been resolved, and we are continuing to monitor.

The incident has been resolved. Services have returned to normal, and all previously affected URLs are now functioning correctly.

We are currently experiencing delays in MediaFlows execution. Some flows may not run immediately after being triggered. Our team is actively investigating the issue. We expect all affected flow runs to be processed, though with delays. We will provide further updates as more information becomes available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue affecting recently added, deleted, or modified assets that may not appear up to date when viewed via the DAM. The issue began at approximately 1:17 PM UTC on June 7, 2026. Although asset views in the DAM may not be reflected accurately, any actions taken on assets are still being applied, and the API continues to function as usual. Please continue to follow this page for updates, and contact [email protected] if you need any assistance. Thank you!

The issue was identified, and a fix has been implemented.

The issue has been resolved, and all services are operating normally.

We want to inform you that starting 16:23 UTC, we're investigating issues affecting our customers relating to displaying/creating API secrets in the Management Console. The usage of API credentials is functioning as intended. Our team is actively investigating the issue to identify the root cause and implement a resolution.

We have rolled out a fix on recent issue on displaying/creating API secrets in the Management Console and currently monitoring our system. All services appear to functioning normally.

We confirm that the update rolled out today has fixed the issue.

We're currently investigating a reported issue when users are attempting to sign up. Our engineering team is working to restore normal operation, and we will provide further updates shortly.

A fix for this issue has been deployed, and we are currently monitoring the results.

The recent sign-up issue has been resolved. All services are now operating normally.

We want to inform you that we have identified an issue affecting MediaFlows where some event-based triggers may not execute as expected. As a result, certain MediaFlows may not run when triggered by events such as metadata updates. Our engineering team is working to restore normal operation, and we will provide further updates shortly.

We have resolved the issues and are monitoring.

The recent issue impacting MediaFlows, where some event-based triggers did not execute as expected, has been resolved. All services are now operating normally.

We want to inform you that we have identified an issue affecting Saved Searches when using Structured Metadata fields that contain spaces in their name (for example, “production type”). As a result, some saved searches may not behave as expected. We are currently performing final testing and deploying a fix.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

From 2:30 PM UTC, we are seeing degraded performance when accessing the Cloudinary console. We are currently investigating the issue.

A fix has been implemented and we are monitoring the results.

The issue has been resolved, and system performance has returned to normal.

Started around 04:30 UTC, search API functionality may be non-functional and newly uploaded assets may not be visible in the Media Library.

This incident has been resolved.

Starting 2:45 PM UTC, we are seeing degraded performance when accessing the Media Library via the console and the widget. We are currently investigating the issue.

Our team identified the cause of the issue and reverted to a known working version. We expect the Media Library's functionality to be fully restored, and we are continually monitoring the status.

This incident has been resolved.

We’re currently experiencing an issue affecting a subset of PDF uploads and deliveries. Some PDF processing operations may fail under specific conditions such as q_auto.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and this issue has been resolved