Cloudinary

This incident has been resolved.

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

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.

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

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

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

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

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.

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)

This incident has been resolved.

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

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.