CheckUpstream measured Cloudinary at 100.000% availability across 2828 independent checks (global · api). 7 incidents were recorded in the past 12 months; the most recent resolved 18 days ago after 25 hours. Status signals are polled from Cloudinary's official Atlassian Statuspage status page, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2828 · p95 591ms (30d)
Share of our own checks against Cloudinary endpoints that returned Cloudinary's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 6 incidents · 88 of 90 days with none posted · 7h 25m of declared impact
Fewer incidents in the last 30 days than 44% of 232 tracked services.
Share of each window with no impact declared by Cloudinary
7d
100.000%
30d
98.968%
90d
99.656%
180d
99.783%
1y
99.893%
Downtime like this can be refundable
If you're a paying Cloudinary customer, outages in these windows may count against Cloudinary's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Cloudinary entitlement →Does Cloudinary actually matter to you?
A Cloudinary outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 6 incidents Cloudinary published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Cloudinary takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 13, 17:04 UTC · resolved in 1d · Resolved
Jul 29, 13:35 UTC · resolved in 1h 25m · Resolved
Jul 20, 23:09 UTC · resolved in 12h 20m · Resolved
2signals across 1 source
Synthetic probes 2
All of these are CheckUpstream's own probes. Nobody else has reported Cloudinary in this window, so nothing here is corroboration.
Live Cloudinary status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/cloudinary)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Cloudinary is currently Operational. CheckUpstream tracks Cloudinary in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Cloudinary down" view? See the Cloudinary Live status page.
Jul 12, 10:20 UTC · resolved in 2h 29m · Resolved
Cloudinary's last resolved incident started 18 days ago and lasted 1 day (degraded performance).
Cloudinary's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Cloudinary endpoints. It is the share of checks that returned the expected response, not a figure taken from Cloudinary's status page.
Sign up to CheckUpstream and add Cloudinary to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Cloudinary's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.