Skip to content

Outage tracker / Cloudinary

Is Cloudinary down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Cloudinary from all 10 regions we check.

Reachability verified

No outage recorded in the 14 days we have measured Cloudinary (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:05 AM UTC
US-East203 msOperational
US-West278 msOperational
Europe146 msOperational
Asia-Pacific104 msOperational
US-Central406 msOperational
Canada232 msOperational
UK132 msOperational
Southeast Asia605 msOperational
Australia493 msOperational
South America211 msOperational
their status pagetheir claim, not our reading

Cloudinary reports: All systems operational (“All Systems Operational”)

from Cloudinary's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Cloudinary's own status page agree: both show Cloudinary as reachable right now.

Cloudinary's own component breakdown, as they publish it

  • Adobe Creative Cloud ConnectorOperational
  • AWS ec2-us-east-1Operational
  • ConsoleOperational
  • Media Transformation API - APOperational
  • Media Transformation API - EUOperational
  • Media Transformation API - USOperational
  • Flow EngineOperational
  • Upload API - APOperational
  • Upload API - EUOperational
  • Upload API - USOperational
  • WordPress PluginOperational
  • Admin API - APOperational
  • Admin API - EUOperational
  • Admin API - USOperational
  • AWS s3-us-standardOperational
  • Magento ExtensionOperational
  • AWS sqs-us-east-1Operational
  • Media DeliveryOperational
  • SalesForce CC Page Designer CartridgeOperational
  • Webhooks / HTTP notifications - APOperational
  • Webhooks / HTTP notifications - EUOperational
  • Webhooks / HTTP notifications - USOperational
  • AWS ec2-eu-west-1Operational
  • Digital Asset Management (DAM)Operational
  • SalesForce CC Site CartridgeOperational
  • AWS ec2-ap-southeast-1Operational
  • Heroku pluginOperational
  • Management ConsoleOperational
  • Akeneo PIM IntegrationOperational
  • Website & DocumentationOperational
  • Figma PluginOperational
  • Upload WidgetOperational
  • Product Gallery WidgetOperational
  • Media Library WidgetOperational
  • Video PlayerOperational
  • Media Editing WidgetOperational
  • Third-Party - Add-onsOperational
  • Support SiteOperational
  • BillingOperational
  • EmailsOperational
  • Assetlink for ShopifyOperational

These are Cloudinary's components, named and scored by Cloudinary. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Cloudinary's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Cloudinary response time, by region

US-East
307msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 640ms2026-08-23 UTC: p95 731ms2026-08-24 UTC: p95 735ms2026-08-25 UTC: p95 753ms2026-08-26 UTC: p95 629ms2026-08-27 UTC: p95 646ms2026-08-28 UTC: p95 492ms2026-08-29 UTC: p95 400ms2026-08-30 UTC: p95 308ms2026-08-31 UTC: p95 314ms2026-09-01 UTC: p95 473ms2026-09-02 UTC: p95 288ms2026-09-03 UTC: p95 459ms2026-09-04 UTC: p95 391ms2026-09-05 UTC: p95 307ms
Aug 7Aug 21Sep 5
US-West
712msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 410ms2026-08-23 UTC: p95 359ms2026-08-24 UTC: p95 290ms2026-08-25 UTC: p95 422ms2026-08-26 UTC: p95 373ms2026-08-27 UTC: p95 552ms2026-08-28 UTC: p95 475ms2026-08-29 UTC: p95 339ms2026-08-30 UTC: p95 362ms2026-08-31 UTC: p95 353ms2026-09-01 UTC: p95 393ms2026-09-02 UTC: p95 636ms2026-09-03 UTC: p95 605ms2026-09-04 UTC: p95 626ms2026-09-05 UTC: p95 712ms
Aug 7Aug 21Sep 5
Europe
150msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 355ms2026-08-23 UTC: p95 403ms2026-08-24 UTC: p95 389ms2026-08-25 UTC: p95 304ms2026-08-26 UTC: p95 406ms2026-08-27 UTC: p95 268ms2026-08-28 UTC: p95 536ms2026-08-29 UTC: p95 283ms2026-08-30 UTC: p95 346ms2026-08-31 UTC: p95 458ms2026-09-01 UTC: p95 441ms2026-09-02 UTC: p95 401ms2026-09-03 UTC: p95 355ms2026-09-04 UTC: p95 339ms2026-09-05 UTC: p95 150ms
Aug 7Aug 21Sep 5
Asia-Pacific
422msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 250ms2026-08-23 UTC: p95 672ms2026-08-24 UTC: p95 539ms2026-08-25 UTC: p95 610ms2026-08-26 UTC: p95 758ms2026-08-27 UTC: p95 784ms2026-08-28 UTC: p95 839ms2026-08-29 UTC: p95 971ms2026-08-30 UTC: p95 767ms2026-08-31 UTC: p95 628ms2026-09-01 UTC: p95 677ms2026-09-02 UTC: p95 934ms2026-09-03 UTC: p95 911ms2026-09-04 UTC: p95 778ms2026-09-05 UTC: p95 422ms
Aug 7Aug 21Sep 5
US-Central
498msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 953ms2026-09-04 UTC: p95 844ms2026-09-05 UTC: p95 498ms
Aug 7Aug 21Sep 5
Canada
378msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 783ms2026-09-04 UTC: p95 850ms2026-09-05 UTC: p95 378ms
Aug 7Aug 21Sep 5
UK
157msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 628ms2026-09-04 UTC: p95 252ms2026-09-05 UTC: p95 157ms
Aug 7Aug 21Sep 5
Southeast Asia
896msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 896ms
Aug 7Aug 21Sep 5
Australia
805msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 925ms2026-09-04 UTC: p95 511ms2026-09-05 UTC: p95 805ms
Aug 7Aug 21Sep 5
South America
606msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 606ms
Aug 7Aug 21Sep 5

Is it Cloudinary, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Cloudinary -- it cannot diagnose Cloudinary's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 203msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Cloudinary normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 278msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Cloudinary normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 406msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Cloudinary normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 232msstatus code: 200checked: Sep 5, 2026, 1:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Cloudinary normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 211msstatus code: 200checked: Sep 5, 2026, 1:56 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Cloudinary normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 146msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Cloudinary normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 132msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Cloudinary normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 104msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Cloudinary normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 605msstatus code: 200checked: Sep 5, 2026, 1:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Cloudinary normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 493msstatus code: 200checked: Sep 5, 2026, 1:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Cloudinary normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Cloudinary, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Cloudinary yet, which is not evidence that nothing is wrong.

Recent outages

Media Library / asset visibility, 24h 41mdeclared on their status page2026-08-13
Add-on installations are unavailable, 1h 22mdeclared on their status page2026-07-29
Connection failures with the Cloudinary MCP Connector, 12h 16mdeclared on their status page2026-07-20
Some customers experience authentication problems when accessing Cloudinary's Figma plugin, 1mdeclared on their status page2026-07-14
Elevated Error Rates for Requests Using g_auto, 2h 24mdeclared on their status page2026-07-12
Delays in MediaFlows, 15h 17mdeclared on their status page2026-06-16
DAM View Assets Error, 17h 1mdeclared on their status page2026-06-07
Management of API credentials is currently experiencing issues, 2h 44mdeclared on their status page2026-03-24

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Cloudinary since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Cloudinary covering any window you pick, with our measurements and Cloudinary's own claim at the time, side by side.

Full availability history for Cloudinary: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Cloudinary, and again when they can reach it again. That is our own measurement from ten regions, not Cloudinary's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Cloudinary uptime measured by RealUptimeLive, from this page's own readings.
[![Cloudinary uptime measured by RealUptime](https://realuptime.io/outages/cloudinary/badge.svg?days=30)](https://realuptime.io/outages/cloudinary)
<a href="https://realuptime.io/outages/cloudinary"><img src="https://realuptime.io/outages/cloudinary/badge.svg?days=30" alt="Cloudinary uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Cloudinary's SLA implies, from our measurement

At or above your target

We measured none of downtime for Cloudinary over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Cloudinary's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://cloudinary.com/
secondary
https://status.cloudinary.com/api/v2/status.json
RealUptime is not affiliated with Cloudinary; the name identifies what we measured, and nothing here speaks for Cloudinary's own team. We send a single web request to Cloudinary from 10 regions on our own schedule and time the response. We do not see inside Cloudinary's systems, do not use an account or real transaction, and are not the same signal Cloudinary's own team has access to. Treat this as one external data point, not a verdict. What we check for Cloudinary proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.