outages.live
Live

Cloudinary

Cloudinary is operational

Checked 24 s ago Operational

History

90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

1 h 47 min

Longest incident

24 h 41 min

Components

41

US Datacenter

Media Transformation API - US Operational
90 days agoNo incidentsToday
Upload API - US Operational
90 days agoNo incidentsToday
Admin API - US Operational
90 days agoNo incidentsToday
Webhooks / HTTP notifications - US Operational
90 days agoNo incidentsToday

Third-Party - Amazon Web Services

AWS ec2-us-east-1 Operational
90 days agoNo incidentsToday
AWS s3-us-standard Operational
90 days agoNo incidentsToday
AWS sqs-us-east-1 Operational
90 days agoNo incidentsToday
AWS ec2-eu-west-1 Operational
90 days agoNo incidentsToday
AWS ec2-ap-southeast-1 Operational
90 days agoNo incidentsToday

EU Datacenter

Media Transformation API - EU Operational
90 days ago1 day with an incidentToday
Upload API - EU Operational
90 days ago1 day with an incidentToday
Admin API - EU Operational
90 days agoNo incidentsToday
Webhooks / HTTP notifications - EU Operational
90 days agoNo incidentsToday

AP Datacenter

Media Transformation API - AP Operational
90 days agoNo incidentsToday
Upload API - AP Operational
90 days agoNo incidentsToday
Admin API - AP Operational
90 days agoNo incidentsToday
Webhooks / HTTP notifications - AP Operational
90 days agoNo incidentsToday

Integrations

Adobe Creative Cloud Connector Operational
90 days agoNo incidentsToday
WordPress Plugin Operational
90 days agoNo incidentsToday
Magento Extension Operational
90 days agoNo incidentsToday
SalesForce CC Page Designer Cartridge Operational
90 days agoNo incidentsToday
SalesForce CC Site Cartridge Operational
90 days agoNo incidentsToday
Heroku plugin Operational
90 days agoNo incidentsToday
Akeneo PIM Integration Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 24, 2026

Duration1 min07:03 to 07:03Notice regarding recently-reported Ruby regular expression vulnerabilities (CVE-2026-89078, CVE-2026-93577, CVE-2026-97229, CVE-2026-110264)Notice

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).

Oct 21, 2026

Duration1 min18:22 to 18:22Notice regarding recently-reported PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619Notice

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

Oct 16, 2026

Duration1 h 47 min20:06 to 21:53Issues accessing the Cloudinary web UIPartial outage

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

Sep 28, 2026

Duration4 h 35 min09:58 to 14:33Increased Error Rates – EU RegionPartial outage

This incident has been resolved.

Aug 13, 2026

Duration24 h 41 min17:04 to 17:45Media Library / asset visibilityDegraded

This incident has been resolved.

Follow Cloudinary

Your coding agent knows when Cloudinary is down, and tells you when a failure is theirs, not yours. You can also get Cloudinary incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudinary" and tell me if Cloudinary has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cloudinary
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudinary

Go from tracking outages to fixing production issues with Polylane.

Try Polylane