Skip to content

Outage tracker / Cloudinary

Is Cloudinary down?

I'm having a problem

Vendor reports no incidentWhat Cloudinary reports

Cloudinary reports no incident on its status page.

As of the last successful poll, 2026-10-23 12:43 UTC.

Cloudinary's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Cloudinary pass from all 10 regions we check.

As of Oct 23, 2026, 12:44 PM UTC, RealUptime's checks of Cloudinary passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 12:44 PM UTC
US-East604 msChecks passing
US-West990 msChecks passing
Europe764 msChecks passing
Asia-Pacific1061 msChecks passing
US-Central562 msChecks passing
Canada183 msChecks passing
UK692 msChecks passing
Southeast Asia2294 msChecks passing
Australia686 msChecks passing
South America756 msChecks passing
their status pagetheir claim, not our reading

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

from Cloudinary's own status page, checked Oct 23, 2026, 12:41 PM UTC
Cloudinary's own status page shows no incident, and our checks of Cloudinary pass 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
960msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 707ms2026-10-06 UTC: p95 710ms2026-10-07 UTC: p95 751ms2026-10-08 UTC: p95 767ms2026-10-09 UTC: p95 777ms2026-10-10 UTC: p95 666ms2026-10-11 UTC: p95 713ms2026-10-12 UTC: p95 684ms2026-10-13 UTC: p95 742ms2026-10-14 UTC: p95 562ms2026-10-15 UTC: p95 564ms2026-10-16 UTC: p95 610ms2026-10-17 UTC: p95 875ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 960ms
Sep 24Oct 8Oct 23
US-West
1.6sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 899ms2026-10-06 UTC: p95 832ms2026-10-07 UTC: p95 789ms2026-10-08 UTC: p95 815ms2026-10-09 UTC: p95 784ms2026-10-10 UTC: p95 802ms2026-10-11 UTC: p95 871ms2026-10-12 UTC: p95 803ms2026-10-13 UTC: p95 817ms2026-10-14 UTC: p95 847ms2026-10-15 UTC: p95 896ms2026-10-16 UTC: p95 838ms2026-10-17 UTC: p95 737ms2026-10-18 UTC: p95 859ms2026-10-19 UTC: p95 937ms2026-10-20 UTC: p95 962ms2026-10-21 UTC: p95 851ms2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.6s
Sep 24Oct 8Oct 23
Europe
864msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 713ms2026-10-06 UTC: p95 698ms2026-10-07 UTC: p95 729ms2026-10-08 UTC: p95 890ms2026-10-09 UTC: p95 887ms2026-10-10 UTC: p95 892ms2026-10-11 UTC: p95 886ms2026-10-12 UTC: p95 904ms2026-10-13 UTC: p95 831ms2026-10-14 UTC: p95 859ms2026-10-15 UTC: p95 827ms2026-10-16 UTC: p95 787ms2026-10-17 UTC: p95 406ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 778ms2026-10-23 UTC: p95 864ms
Sep 24Oct 8Oct 23
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.1s
Sep 24Oct 8Oct 23
US-Central
691msp95 · 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-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 473ms2026-10-06 UTC: p95 403ms2026-10-07 UTC: p95 359ms2026-10-08 UTC: p95 449ms2026-10-09 UTC: p95 528ms2026-10-10 UTC: p95 499ms2026-10-11 UTC: p95 435ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 610ms2026-10-14 UTC: p95 517ms2026-10-15 UTC: p95 448ms2026-10-16 UTC: p95 426ms2026-10-17 UTC: p95 296ms2026-10-18 UTC: p95 290ms2026-10-19 UTC: p95 272ms2026-10-20 UTC: p95 439ms2026-10-21 UTC: p95 472ms2026-10-22 UTC: p95 717ms2026-10-23 UTC: p95 691ms
Sep 24Oct 8Oct 23
Canada
312msp95 · 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-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 484ms2026-10-06 UTC: p95 625ms2026-10-07 UTC: p95 286ms2026-10-08 UTC: p95 601ms2026-10-09 UTC: p95 646ms2026-10-10 UTC: p95 342ms2026-10-11 UTC: p95 333ms2026-10-12 UTC: p95 361ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 524ms2026-10-15 UTC: p95 400ms2026-10-16 UTC: p95 311ms2026-10-17 UTC: p95 386ms2026-10-18 UTC: p95 446ms2026-10-19 UTC: p95 600ms2026-10-20 UTC: p95 334ms2026-10-21 UTC: p95 308ms2026-10-22 UTC: p95 281ms2026-10-23 UTC: p95 312ms
Sep 24Oct 8Oct 23
UK
906msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 910ms2026-10-06 UTC: p95 962ms2026-10-07 UTC: p95 862ms2026-10-08 UTC: p95 844ms2026-10-09 UTC: p95 911ms2026-10-10 UTC: p95 875ms2026-10-11 UTC: p95 894ms2026-10-12 UTC: p95 853ms2026-10-13 UTC: p95 823ms2026-10-14 UTC: p95 796ms2026-10-15 UTC: p95 779ms2026-10-16 UTC: p95 728ms2026-10-17 UTC: p95 410ms2026-10-18 UTC: p95 687ms2026-10-19 UTC: p95 746ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 818ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 906ms
Sep 24Oct 8Oct 23
Southeast Asia
2.6sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.4s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.6s
Sep 24Oct 8Oct 23
Australia
870msp95 · 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-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.3s2026-10-06 UTC: p95 899ms2026-10-07 UTC: p95 931ms2026-10-08 UTC: p95 893ms2026-10-09 UTC: p95 994ms2026-10-10 UTC: p95 941ms2026-10-11 UTC: p95 887ms2026-10-12 UTC: p95 917ms2026-10-13 UTC: p95 985ms2026-10-14 UTC: p95 903ms2026-10-15 UTC: p95 899ms2026-10-16 UTC: p95 999ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 870ms
Sep 24Oct 8Oct 23
South America
2.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 954ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 891ms2026-10-15 UTC: p95 904ms2026-10-16 UTC: p95 911ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 2.7s
Sep 24Oct 8Oct 23

Check your own site while you wait on Cloudinary

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Cloudinary reports an incident on its status page, and again when it reports it resolved.

Get an email when Cloudinary reports an incident

Email me when Cloudinary reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Cloudinary's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 604msstatus code: 401checked: Oct 23, 2026, 12:44 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
      Checks passinglatency: 990msstatus code: 401checked: Oct 23, 2026, 12:37 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
      Checks passinglatency: 562msstatus code: 401checked: Oct 23, 2026, 12:39 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
      Checks passinglatency: 183msstatus code: 401checked: Oct 23, 2026, 12:32 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
    Checks passinglatency: 756msstatus code: 401checked: Oct 23, 2026, 12:33 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 764msstatus code: 401checked: Oct 23, 2026, 12:40 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
      Checks passinglatency: 692msstatus code: 401checked: Oct 23, 2026, 12:41 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1061msstatus code: 401checked: Oct 23, 2026, 12:44 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
      Checks passinglatency: 2294msstatus code: 401checked: Oct 23, 2026, 12:41 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
      Checks passinglatency: 686msstatus code: 401checked: Oct 23, 2026, 12:26 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 probe events

Notice regarding recently-reported PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619, 1mdeclared on their status page2026-10-21
Issues accessing the Cloudinary web UI, 1h 47mdeclared on their status page2026-10-16
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-12

check 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 check readings and Cloudinary's own claim at the time, side by side.

Full check history for Cloudinary: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Cloudinary uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Cloudinary down?", https://realuptime.io/outages/cloudinary. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.cloudinary.com

RealUptime is not affiliated with Cloudinary; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.