Cloudinary Status
Connection failures with the Cloudinary MCP Connector

Started

Resolved

Duration

12 hrs 16 min

Resolvedminor impactVendor link

Update timeline

Resolved

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

Monitoring

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

Investigating

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

Connection failures with the Cloudinary MCP Connector — Cloudinary Incident Timeline & Status — DevHelm