Cloudinary status · Data & Backend · checked (5m ago)
Operational
No — Cloudinary is not down. All Cloudinary systems are reported operational.
According to Cloudinary's official status page, Cloudinary was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Cloudinary's feed reported no outage in 100.00% of our checks.
No outage reported (30d)
100.00%
Share of our checks where Cloudinary's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
1.12 s
How long the last status check took
Reported by
Operational
All Systems Operational
Is Cloudinary down for you right now?
Everything above is read from Cloudinary's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Cloudinary in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Cloudinary is
Cloudinary handles image and video storage, transformation and delivery — resizing, format conversion and optimisation applied through the URL, served over a CDN. Broken images across a site is the usual symptom.
What Cloudinary's status feed covers
Cloudinary's status page separates delivery (the CDN that serves finished assets) from the transformation pipeline, uploads and the admin API. Delivery is the resilient path: already-transformed assets are cached at the edge and keep serving through incidents that stop new uploads or new transformations from being processed.
One bar per day. Each shows the share of that day's checks where Cloudinary's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Cloudinary was down.
2026-08-2530 of 30 days recordedToday
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 5m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Cloudinary's status endpoint.
Cloudinary outage history
Cloudinary has published 27 incidents in the last 12 months, the 20 most recent shown here. Only what Cloudinary posted itself — not every problem users hit.
No — Cloudinary is not down. All Cloudinary systems are reported operational. Checked (5m ago).
What is Cloudinary's status right now?
Cloudinary is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 1.12 s. isuptime reads this from Cloudinary's own published feed and does not test Cloudinary independently.
When did Cloudinary last go down?
The most recent incident Cloudinary published was “Media Library / asset visibility”, opened Aug 13, 05:04 PM UTC (41d ago) and marked resolved Aug 14, 05:45 PM UTC. That is the latest entry in Cloudinary's own incident feed, not every problem users experienced.
What is Cloudinary's uptime?
isuptime does not measure Cloudinary's uptime directly — it reads Cloudinary's own published status feed. Over the last 30 days, Cloudinary's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Cloudinary down for everyone?
Cloudinary reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Cloudinary says operational but it is not working for me
A broken image URL is usually the transformation string or a missing asset rather than an outage — request the original without transformations to check. Signed URLs that have expired return errors that look like failures. Free-plan credit exhaustion stops transformations while cached assets carry on serving, which produces a confusing half-broken site.
