Skip to content

Outage tracker / Cloudinary

Is Cloudinary down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Cloudinary from all 10 regions we check.

As of Oct 5, 2026, 8:14 PM UTC, Cloudinary answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:14 PM UTC
US-East386 msOperational
US-West670 msOperational
Europe602 msOperational
Asia-Pacific654 msOperational
US-Central363 msOperational
Canada272 msOperational
UK733 msOperational
Southeast Asia1186 msOperational
Australia675 msOperational
South America703 msOperational
their status pagetheir claim, not our reading

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

from Cloudinary's own status page, checked Oct 5, 2026, 7:52 PM 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

  • AWS ec2-us-east-1Operational
  • Adobe Creative Cloud ConnectorOperational
  • 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
  • AWS s3-us-standardOperational
  • Admin API - APOperational
  • Admin API - EUOperational
  • Admin API - USOperational
  • 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
710msp95 · 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-09-06 UTC: p95 240ms2026-09-07 UTC: p95 262ms2026-09-08 UTC: p95 233ms2026-09-09 UTC: p95 261ms2026-09-10 UTC: p95 454ms2026-09-11 UTC: p95 343ms2026-09-12 UTC: p95 325ms2026-09-13 UTC: p95 267ms2026-09-14 UTC: p95 286ms2026-09-15 UTC: p95 271ms2026-09-16 UTC: p95 813ms2026-09-17 UTC: p95 918ms2026-09-18 UTC: p95 885ms2026-09-19 UTC: p95 832ms2026-09-20 UTC: p95 828ms2026-09-21 UTC: p95 777ms2026-09-22 UTC: p95 669ms2026-09-23 UTC: p95 812ms2026-09-24 UTC: p95 857ms2026-09-25 UTC: p95 636ms2026-09-26 UTC: p95 776ms2026-09-27 UTC: p95 681ms2026-09-28 UTC: p95 636ms2026-09-29 UTC: p95 355ms2026-09-30 UTC: p95 273ms2026-10-01 UTC: p95 718ms2026-10-02 UTC: p95 333ms2026-10-03 UTC: p95 738ms2026-10-04 UTC: p95 771ms2026-10-05 UTC: p95 710ms
Sep 6Sep 20Oct 5
US-West
843msp95 · 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-09-06 UTC: p95 700ms2026-09-07 UTC: p95 746ms2026-09-08 UTC: p95 556ms2026-09-09 UTC: p95 441ms2026-09-10 UTC: p95 702ms2026-09-11 UTC: p95 749ms2026-09-12 UTC: p95 737ms2026-09-13 UTC: p95 528ms2026-09-14 UTC: p95 537ms2026-09-15 UTC: p95 604ms2026-09-16 UTC: p95 625ms2026-09-17 UTC: p95 372ms2026-09-18 UTC: p95 394ms2026-09-19 UTC: p95 295ms2026-09-20 UTC: p95 317ms2026-09-21 UTC: p95 385ms2026-09-22 UTC: p95 376ms2026-09-23 UTC: p95 334ms2026-09-24 UTC: p95 417ms2026-09-25 UTC: p95 411ms2026-09-26 UTC: p95 429ms2026-09-27 UTC: p95 369ms2026-09-28 UTC: p95 347ms2026-09-29 UTC: p95 202ms2026-09-30 UTC: p95 416ms2026-10-01 UTC: p95 589ms2026-10-02 UTC: p95 420ms2026-10-03 UTC: p95 718ms2026-10-04 UTC: p95 847ms2026-10-05 UTC: p95 843ms
Sep 6Sep 20Oct 5
Europe
735msp95 · 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-09-06 UTC: p95 376ms2026-09-07 UTC: p95 379ms2026-09-08 UTC: p95 352ms2026-09-09 UTC: p95 324ms2026-09-10 UTC: p95 338ms2026-09-11 UTC: p95 303ms2026-09-12 UTC: p95 317ms2026-09-13 UTC: p95 327ms2026-09-14 UTC: p95 267ms2026-09-15 UTC: p95 264ms2026-09-16 UTC: p95 325ms2026-09-17 UTC: p95 387ms2026-09-18 UTC: p95 410ms2026-09-19 UTC: p95 388ms2026-09-20 UTC: p95 404ms2026-09-21 UTC: p95 468ms2026-09-22 UTC: p95 457ms2026-09-23 UTC: p95 263ms2026-09-24 UTC: p95 257ms2026-09-25 UTC: p95 295ms2026-09-26 UTC: p95 356ms2026-09-27 UTC: p95 366ms2026-09-28 UTC: p95 456ms2026-09-29 UTC: p95 303ms2026-09-30 UTC: p95 410ms2026-10-01 UTC: p95 725ms2026-10-02 UTC: p95 743ms2026-10-03 UTC: p95 739ms2026-10-04 UTC: p95 691ms2026-10-05 UTC: p95 735ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 372ms2026-09-07 UTC: p95 364ms2026-09-08 UTC: p95 338ms2026-09-09 UTC: p95 402ms2026-09-10 UTC: p95 502ms2026-09-11 UTC: p95 541ms2026-09-12 UTC: p95 518ms2026-09-13 UTC: p95 352ms2026-09-14 UTC: p95 356ms2026-09-15 UTC: p95 327ms2026-09-16 UTC: p95 346ms2026-09-17 UTC: p95 426ms2026-09-18 UTC: p95 496ms2026-09-19 UTC: p95 512ms2026-09-20 UTC: p95 565ms2026-09-21 UTC: p95 587ms2026-09-22 UTC: p95 704ms2026-09-23 UTC: p95 587ms2026-09-24 UTC: p95 660ms2026-09-25 UTC: p95 552ms2026-09-26 UTC: p95 538ms2026-09-27 UTC: p95 517ms2026-09-28 UTC: p95 496ms2026-09-29 UTC: p95 587ms2026-09-30 UTC: p95 766ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
475msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 302ms2026-09-07 UTC: p95 306ms2026-09-08 UTC: p95 316ms2026-09-09 UTC: p95 333ms2026-09-10 UTC: p95 434ms2026-09-11 UTC: p95 398ms2026-09-12 UTC: p95 328ms2026-09-13 UTC: p95 305ms2026-09-14 UTC: p95 292ms2026-09-15 UTC: p95 381ms2026-09-16 UTC: p95 323ms2026-09-17 UTC: p95 293ms2026-09-18 UTC: p95 345ms2026-09-19 UTC: p95 344ms2026-09-20 UTC: p95 361ms2026-09-21 UTC: p95 355ms2026-09-22 UTC: p95 340ms2026-09-23 UTC: p95 260ms2026-09-24 UTC: p95 233ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 873ms2026-09-28 UTC: p95 894ms2026-09-29 UTC: p95 433ms2026-09-30 UTC: p95 417ms2026-10-01 UTC: p95 419ms2026-10-02 UTC: p95 411ms2026-10-03 UTC: p95 495ms2026-10-04 UTC: p95 536ms2026-10-05 UTC: p95 475ms
Sep 6Sep 20Oct 5
Canada
475msp95 · 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-06 UTC: p95 299ms2026-09-07 UTC: p95 302ms2026-09-08 UTC: p95 236ms2026-09-09 UTC: p95 303ms2026-09-10 UTC: p95 362ms2026-09-11 UTC: p95 355ms2026-09-12 UTC: p95 424ms2026-09-13 UTC: p95 361ms2026-09-14 UTC: p95 397ms2026-09-15 UTC: p95 459ms2026-09-16 UTC: p95 500ms2026-09-17 UTC: p95 465ms2026-09-18 UTC: p95 460ms2026-09-19 UTC: p95 456ms2026-09-20 UTC: p95 437ms2026-09-21 UTC: p95 430ms2026-09-22 UTC: p95 358ms2026-09-23 UTC: p95 379ms2026-09-24 UTC: p95 430ms2026-09-25 UTC: p95 466ms2026-09-26 UTC: p95 432ms2026-09-27 UTC: p95 526ms2026-09-28 UTC: p95 564ms2026-09-29 UTC: p95 536ms2026-09-30 UTC: p95 606ms2026-10-01 UTC: p95 488ms2026-10-02 UTC: p95 389ms2026-10-03 UTC: p95 420ms2026-10-04 UTC: p95 495ms2026-10-05 UTC: p95 475ms
Sep 6Sep 20Oct 5
UK
879msp95 · 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-06 UTC: p95 282ms2026-09-07 UTC: p95 224ms2026-09-08 UTC: p95 266ms2026-09-09 UTC: p95 216ms2026-09-10 UTC: p95 144ms2026-09-11 UTC: p95 149ms2026-09-12 UTC: p95 133ms2026-09-13 UTC: p95 127ms2026-09-14 UTC: p95 232ms2026-09-15 UTC: p95 228ms2026-09-16 UTC: p95 261ms2026-09-17 UTC: p95 268ms2026-09-18 UTC: p95 171ms2026-09-19 UTC: p95 199ms2026-09-20 UTC: p95 260ms2026-09-21 UTC: p95 363ms2026-09-22 UTC: p95 373ms2026-09-23 UTC: p95 366ms2026-09-24 UTC: p95 414ms2026-09-25 UTC: p95 356ms2026-09-26 UTC: p95 255ms2026-09-27 UTC: p95 339ms2026-09-28 UTC: p95 296ms2026-09-29 UTC: p95 230ms2026-09-30 UTC: p95 406ms2026-10-01 UTC: p95 524ms2026-10-02 UTC: p95 676ms2026-10-03 UTC: p95 597ms2026-10-04 UTC: p95 980ms2026-10-05 UTC: p95 879ms
Sep 6Sep 20Oct 5
Southeast Asia
1.4sp95 · 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-06 UTC: p95 616ms2026-09-07 UTC: p95 507ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 866ms2026-09-12 UTC: p95 676ms2026-09-13 UTC: p95 614ms2026-09-14 UTC: p95 824ms2026-09-15 UTC: p95 860ms2026-09-16 UTC: p95 738ms2026-09-17 UTC: p95 648ms2026-09-18 UTC: p95 763ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 783ms2026-09-24 UTC: p95 524ms2026-09-25 UTC: p95 602ms2026-09-26 UTC: p95 779ms2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 992ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
Australia
1.5sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 702ms2026-09-07 UTC: p95 465ms2026-09-08 UTC: p95 557ms2026-09-09 UTC: p95 503ms2026-09-10 UTC: p95 837ms2026-09-11 UTC: p95 666ms2026-09-12 UTC: p95 634ms2026-09-13 UTC: p95 530ms2026-09-14 UTC: p95 609ms2026-09-15 UTC: p95 550ms2026-09-16 UTC: p95 491ms2026-09-17 UTC: p95 516ms2026-09-18 UTC: p95 846ms2026-09-19 UTC: p95 694ms2026-09-20 UTC: p95 527ms2026-09-21 UTC: p95 530ms2026-09-22 UTC: p95 549ms2026-09-23 UTC: p95 610ms2026-09-24 UTC: p95 664ms2026-09-25 UTC: p95 650ms2026-09-26 UTC: p95 638ms2026-09-27 UTC: p95 698ms2026-09-28 UTC: p95 821ms2026-09-29 UTC: p95 681ms2026-09-30 UTC: p95 982ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 940ms2026-10-03 UTC: p95 887ms2026-10-04 UTC: p95 889ms2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
1.2sp95 · 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-06 UTC: p95 490ms2026-09-07 UTC: p95 837ms2026-09-08 UTC: p95 842ms2026-09-09 UTC: p95 381ms2026-09-10 UTC: p95 515ms2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 649ms2026-09-13 UTC: p95 734ms2026-09-14 UTC: p95 673ms2026-09-15 UTC: p95 777ms2026-09-16 UTC: p95 686ms2026-09-17 UTC: p95 953ms2026-09-18 UTC: p95 795ms2026-09-19 UTC: p95 788ms2026-09-20 UTC: p95 781ms2026-09-21 UTC: p95 684ms2026-09-22 UTC: p95 986ms2026-09-23 UTC: p95 906ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 737ms2026-09-26 UTC: p95 690ms2026-09-27 UTC: p95 704ms2026-09-28 UTC: p95 801ms2026-09-29 UTC: p95 303ms2026-09-30 UTC: p95 803ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 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 we measured, function by function

Cloudinary answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Cloudinary go down, and when it is back

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.

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: 386msstatus code: 401checked: Oct 5, 2026, 8:10 PM 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: 670msstatus code: 401checked: Oct 5, 2026, 8:13 PM 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: 363msstatus code: 401checked: Oct 5, 2026, 8:07 PM 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: 272msstatus code: 401checked: Oct 5, 2026, 8:14 PM 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: 703msstatus code: 401checked: Oct 5, 2026, 8:12 PM 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: 602msstatus code: 401checked: Oct 5, 2026, 8:06 PM 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: 733msstatus code: 401checked: Oct 5, 2026, 8:01 PM 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: 654msstatus code: 401checked: Oct 5, 2026, 8:08 PM 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: 1186msstatus code: 401checked: Oct 5, 2026, 7:55 PM 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: 675msstatus code: 401checked: Oct 5, 2026, 8:00 PM 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

Usage reports unavailable in Console Dashboard, 1mdeclared on their status page2026-10-05
Increased Error Rates – EU Region, 4h 35mdeclared on their status page2026-09-28
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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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

primaryfunctional: live API
https://api.cloudinary.com/v1_1/demo/resources/image
secondary
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. At least one endpoint we check for Cloudinary is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.