Skip to main content
Cloudinary logo

Is Cloudinary Down?

No — Cloudinary is up
Cloudinary's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 113 ms

Right now

The verdict is the worse of these two. How we decide

Cloudinary's status page

status.cloudinary.com · read · checked every 3 minutes

Operational
Cloudinary's components, as its status page reports them
ComponentStatus
Adobe Creative Cloud ConnectorOperational
WordPress PluginOperational
Magento ExtensionOperational
SalesForce CC Page Designer CartridgeOperational
SalesForce CC Site CartridgeOperational
Heroku pluginOperational
Akeneo PIM IntegrationOperational
Figma PluginOperational
ConsoleOperational
Flow EngineOperational
AWS s3-us-standardOperational
Media DeliveryOperational
13 more, all operational · show all 25
All of Cloudinary's components
ComponentStatus
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
Third-Party - Amazon Web Services
AWS s3-us-standardOperational
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
16 locations All operational

FlareWarden checks

res.cloudinary.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
113 ms
Checked

By region

  • Amsterdam reachable, 72 ms
  • Chicago reachable, 199 ms
  • London reachable, 109 ms
  • San Jose reachable, 101 ms
  • Singapore reachable, 115 ms
  • Sydney reachable, 41 ms
  • Tokyo reachable, 200 ms
  • Toronto reachable, 74 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam47 ms3 ms7 ms65 ms
Chicago130 ms3 ms15 ms196 ms
London55 ms3 ms9 ms105 ms
San Jose52 ms2 ms9 ms97 ms
Singapore85 ms1 ms4 ms110 ms
Sydney7 ms1 ms6 ms37 ms
Tokyo172 ms1 ms7 ms196 ms
Toronto60 ms1 ms5 ms71 ms
We check that res.cloudinary.com loads, not every feature behind it. Test it yourself

History

Incidents Cloudinary reported

Since Oct 25, 12 days · from status.cloudinary.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Cloudinary website availability

Measured by FlareWarden · res.cloudinary.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
217ms

Last 30 days

12-day clean streak
Oct 7: no data
Oct 8: no data
Oct 9: no data
Oct 10: no data
Oct 11: no data
Oct 12: no data
Oct 13: no data
Oct 14: no data
Oct 15: no data
Oct 16: no data
Oct 17: no data
Oct 18: no data
Oct 19: no data
Oct 20: no data
Oct 21: no data
Oct 22: no data
Oct 23: no data
Oct 24: no data
Oct 25: 100.00% uptime, 16 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of res.cloudinary.com from multiple regions every 6 hours. Cloudinary's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Cloudinary does

Cloudinary stores a site's images and videos, transforms them on request through URL parameters such as resizing, cropping and format conversion, and delivers the results through a CDN from res.cloudinary.com. Developers upload through its API, SDKs or Upload Widget, and teams manage files in the Console and Media Library. It also runs plugins for WordPress, Magento and Salesforce Commerce Cloud, each listed on its status page.

What an outage looks like

Images and videos load as broken placeholders or return errors from res.cloudinary.com, uploads fail, and transformation URLs return errors. On September 28, 2026 the EU region saw increased error rates for uploads, transformations and delivery. Console problems are separate: on October 16, 2026 users could not log in to the Console or Media Library while delivery and API uploads kept working.

What to do about it

Check status.cloudinary.com, which splits Upload, Admin and Media Transformation APIs by US, EU and AP datacenter and lists Media Delivery, the Console and integrations on their own rows. Failed webhook notifications are retried three times, after 3, 6 and 9 minutes. For a URL that still returns a 404 after a fix, read its X-Cld-Error header, since the error may be cached at the CDN.

Is it down for everyone, or just you?

If this page says Cloudinary is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cloudinary outage FAQ

Is Cloudinary down or is it my account?
If status.cloudinary.com is clear, inspect the failing URL. Cloudinary's docs say a failed delivery URL returns an HTTP 40X status and often an X-Cld-Error response header naming the specific reason, which you can read in your browser's developer tools Network tab. Cloudinary's onboarding FAQ also points to its ping endpoint for checking API server availability programmatically.
Why does an image still fail after Cloudinary fixed the problem?
The error itself may be cached. Cloudinary caches 40X responses at the CDN per exact URL, first for 1 minute and then doubling on each repeated failure up to 24 hours. Its docs suggest appending a no-impact transformation such as a_0 to the URL: if that variant loads while the original still fails, you are seeing a cached error.
Can the Cloudinary Console be down while images still load?
Yes. On October 16, 2026 Cloudinary reported that some users could not log in or use the Console and Media Library for about 1 hour 45 minutes, and stated that image and video delivery, uploads and API requests using API credentials were not affected. The status page tracks the Console and Media Delivery as separate components.
Will I miss Cloudinary webhook notifications during an outage?
Not if your endpoint recovers quickly. Cloudinary's notifications docs say that when a notification URL does not answer 200 OK, it makes three more attempts: after 3 minutes, after 6 minutes and a final one after 9 minutes. An endpoint still down after the last retry at 9 minutes gets no further attempts under that policy.
What does the check on this page measure?
It loads sample.jpg from res.cloudinary.com/demo, the demo product environment Cloudinary uses in its own documentation examples. That measures media delivery from res.cloudinary.com only. It does not test the Console, the Upload API or the Admin API, which Cloudinary's status page tracks separately for its US, EU and AP datacenters, so those can fail while this check stays green.

How we measure this

  • We request Cloudinary's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Cloudinary publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Cloudinary itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Cloudinary goes down

We check Cloudinary every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required