Where does this status come from?

From Cloudinary's own status page API at https://status.cloudinary.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cloudinary's words.

How can my agent or app check Cloudinary status?

Fetch https://upbutler.com/status/cloudinary/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cloudinary"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Cloudinary's?

Add "cloudinary" to the dependencies of your UpButler workspace. When one of your monitors fails while Cloudinary has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Cloudinary down?

Right now

No. Cloudinary is operational.

No incidents reported.

Read from status.cloudinary.com 73 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/cloudinary/status.agent.json

MCP: upstream_status {"service":"cloudinary"}

Image and video upload, transformation and delivery.

What Cloudinary reports

Operational

Taken as is from Cloudinary's own status page API. Incident titles and component names below are theirs.

Open status.cloudinary.com

UpButler's independent probe

There is no keyless endpoint of Cloudinary that says anything useful, so UpButler does not probe it. To check your own Cloudinary account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Cloudinary components

41 operational

US Datacenter

Media Transformation API - USOperational
Upload API - USOperational
Admin API - USOperational
Webhooks / HTTP notifications - USOperational

Third-Party - Amazon Web Services

AWS ec2-us-east-1Operational
AWS s3-us-standardOperational
AWS sqs-us-east-1Operational
AWS ec2-eu-west-1Operational
AWS ec2-ap-southeast-1Operational

EU Datacenter

Media Transformation API - EUOperational
Upload API - EUOperational
Admin API - EUOperational
Webhooks / HTTP notifications - EUOperational

AP Datacenter

Media Transformation API - APOperational
Upload API - APOperational
Admin API - APOperational
Webhooks / HTTP notifications - APOperational

Integrations

Adobe Creative Cloud ConnectorOperational
WordPress PluginOperational
Magento ExtensionOperational
SalesForce CC Page Designer CartridgeOperational
SalesForce CC Site CartridgeOperational
Heroku pluginOperational
Akeneo PIM IntegrationOperational
Figma PluginOperational

MediaFlows

ConsoleOperational
Flow EngineOperational

Media DeliveryOperational
Digital Asset Management (DAM)Operational
Management ConsoleOperational
Website & DocumentationOperational
Upload WidgetOperational
Product Gallery WidgetOperational
Media Library WidgetOperational
Video PlayerOperational
Media Editing WidgetOperational
Third-Party - Add-onsOperational
Support SiteOperational
BillingOperational
EmailsOperational
Assetlink for ShopifyOperational

Cloudinary incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Cloudinary.

Started (UTC)	Incident	Impact	Lasted
2026-10-05 12:20	Usage reports unavailable in Console Dashboard	minor	under a minute
2026-09-28 09:58	Increased Error Rates – EU Region	major	4 h 35 min

Tell your outage from Cloudinary's

Declare that your project depends on Cloudinary. When one of your monitors fails while Cloudinary has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - cloudinary

Ask before you retry

curl -s https://upbutler.com/status/cloudinary/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "cloudinary",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Cloudinary down right now?: No. As of 2026-10-10 05:09 UTC, Cloudinary is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Cloudinary's own status page API at https://status.cloudinary.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cloudinary's words.
How can my agent or app check Cloudinary status?: Fetch https://upbutler.com/status/cloudinary/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cloudinary"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Cloudinary's?: Add "cloudinary" to the dependencies of your UpButler workspace. When one of your monitors fails while Cloudinary has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in media

UpButler is not affiliated with Cloudinary. Status and incident text belong to Cloudinary and are read from their public status source; the probe result is UpButler's own measurement.