Vendor record
Cloudinary
Checked
Front door check counts and Cloudinary’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Cloudinary endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.cloudinary.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Cloudinary product, region or your app worked.
How we count front door checksCloudinary says
Incident posts from Cloudinary’s status page, with its titles, impact levels and times. They say what Cloudinary chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
1
incidents Cloudinary posted, last 30 days
Most recent records · all dates
Increased Error Rates – EU Region
MajorCloudinary’s postStarted, per Cloudinary
Closed in our record(4h 41m)
Media Library / asset visibility
MinorCloudinary’s postStarted, per Cloudinary
Closed in our record(1d)
Add-on installations are unavailable
MinorCloudinary’s postStarted, per Cloudinary
Closed in our record(1h 25m)
Connection failures with the Cloudinary MCP Connector
MinorCloudinary’s postStarted, per Cloudinary
Closed in our record(12h 20m)
Elevated Error Rates for Requests Using g_auto
MajorCloudinary’s postStarted, per Cloudinary
Closed in our record(2h 29m)
3 older records
Delays in MediaFlows
MinorCloudinary’s postStarted, per Cloudinary
Closed in our record(15h 20m)
DAM View Assets Error
MajorCloudinary’s postStarted, per Cloudinary
Closed in our record(17h 10m)
Management of API credentials is currently experiencing issues
MajorCloudinary’s postStarted, per Cloudinary
Closed in our record(2h 45m)
Your code, your dependencies
See which of your code paths call Cloudinary
Connect GitHub or GitLab to find where your public or private repository uses Cloudinary. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Cloudinary status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Cloudinary currently down?
Cloudinary's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Cloudinary last have an outage?
The most recent closed incident record began 18 days ago and spans 4h 41m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Cloudinary?
No. CheckUpstream checks Cloudinary’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Cloudinary in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Cloudinary?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.