Cloudinary Status: How to Check If Cloudinary Is Down Right Now (2026)
Updated June 9, 2026 · 9 min read · API Status Check
Quick Answer
Check Cloudinary status at status.cloudinary.com (official). If uploads are failing but delivery is fine, check the Upload API component separately — they run on independent infrastructure.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official Cloudinary Status Page
Cloudinary maintains an official status page at status.cloudinary.com. It breaks down status by service component so you can pinpoint exactly which part of Cloudinary is experiencing issues:
What Each Cloudinary Status Indicator Means
Get alerted the instant Cloudinary goes down
Better Stack monitors your Cloudinary upload and delivery endpoints every 30 seconds and alerts your team before users notice broken images. Free tier included.
Try Better Stack Free →Cloudinary Components: What Can Fail Independently
Cloudinary is a multi-tier media platform. Upload infrastructure, CDN delivery, and AI processing run on separate systems — understanding which layer is broken tells you how to respond:
Cloudinary Upload API
What it is: The REST API at api.cloudinary.com/v1_1 that accepts file uploads. All upload methods (direct, signed, unsigned, SDK) route through here.
Signs of issues: HTTP 500 or 503 on upload requests, upload SDK throwing errors, files not appearing in Media Library after upload attempt.
Workaround: Queue uploads locally and retry with exponential backoff. Use signed upload presets so uploads can resume when the API recovers.
Cloudinary CDN Delivery
What it is: Global CDN that serves transformed images and videos via res.cloudinary.com or custom domains. This is what your end users hit.
Signs of issues: Images returning 404 or 503, delivery URLs timing out, broken images appearing in your app even for assets that were successfully uploaded.
Workaround: Implement an <img> onerror fallback to serve a local placeholder. CDN issues rarely affect all assets — test with a direct Cloudinary URL to confirm.
Cloudinary Transformations
What it is: On-the-fly image and video transformation pipeline — resizing, cropping, format conversion, watermarking applied via URL parameters.
Signs of issues: Transformed image URLs returning errors while original (untransformed) URLs work fine. Transformation parameters being ignored.
Workaround: Serve pre-transformed eager transformations as fallback. Eager transformations are pre-generated on upload and cached permanently.
Cloudinary Video Processing
What it is: Async video transcoding pipeline for format conversion, adaptive streaming (HLS), and video transformations.
Signs of issues: Video uploads succeed (raw file stored) but playback URLs return errors. HLS manifests 404. Video transcoding jobs stuck in queue.
Workaround: Serve the original uploaded video file (with f_auto) as fallback while transcoding jobs are queued. Check transcoding status via Admin API.
Cloudinary Admin API
What it is: Management API for searching assets, managing folders, updating metadata, and configuring presets.
Signs of issues: Admin API calls (list assets, search, delete) returning 500s. Upload presets failing to load. Asset management in console broken.
Workaround: Admin API outages rarely affect upload or delivery. Queue admin operations and retry. Your end-user experience is typically unaffected.
Is Cloudinary Down or Is It My Configuration?
Many Cloudinary errors look like outages but are actually configuration issues. Before concluding Cloudinary is down:
Verify your cloud name at cloudinary.com/console → Settings → Cloud name. A typo in the cloud name makes every URL invalid.
Regenerate API credentials at cloudinary.com/console → Settings → Access Keys. Never embed credentials in client-side code.
Use the Cloudinary URL generator at cloudinary.com/tools/url-generator to validate transformation parameters. Invalid transformations throw 400, not 500.
Verify the upload preset exists and is set to "unsigned" in Media Library → Settings → Upload → Upload presets.
Check your plan storage usage at cloudinary.com/console → Account → Usage. Free plan has 25 credits/month.
5 Ways to Check Cloudinary Status Right Now
Official Cloudinary Status Page
Visit status.cloudinary.com for real-time component-level status. Subscribe to email notifications for incident alerts. Check historical incidents to understand past outage patterns.
status.cloudinary.com →Test Your Delivery URL Directly
Fetch a known Cloudinary delivery URL directly in your browser or via curl. A 200 response confirms CDN delivery is working. A 502/503 confirms a CDN outage.
curl -o /dev/null -w "%{http_code}" https://res.cloudinary.com/<cloud>/image/upload/sample.jpgCloudinary Support Portal
For paid plans, Cloudinary's support portal at support.cloudinary.com has incident history and allows opening support tickets. Enterprise plans get SLA-backed response times.
support.cloudinary.com →Community Forums & Stack Overflow
Search Stack Overflow for "cloudinary" + current date or check the Cloudinary Community Forum. During outages, multiple developers report similar errors within minutes.
Stack Overflow: cloudinary tag →Third-Party Independent Monitor
Use Better Stack or UptimeRobot to create synthetic monitors against your Cloudinary upload and delivery endpoints. Independent monitoring catches incidents before the official status page is updated.
Cloudinary Error Codes During Outages
When Cloudinary is down or degraded, your app sees specific HTTP status codes:
503Service UnavailableCloudinary service is down or overloaded. Check status.cloudinary.com immediately. Retry with exponential backoff.500Internal Server ErrorUnexpected Cloudinary server error. Retry 2-3 times. If persistent, likely an active incident.429Rate LimitedToo many requests to the Upload API. Implement request queuing and respect rate limits. Not an outage — reduce upload concurrency.400Bad RequestInvalid transformation parameters, missing required upload fields, or malformed request. Check your transformation syntax — this is a config issue, not an outage.401UnauthorizedInvalid or expired API key/secret. Verify credentials in Cloudinary console settings. Not an outage.404 on deliveryAsset Not FoundThe asset public_id does not exist in your Cloudinary account, or the cloud name is wrong. Check your asset exists in Media Library.Monitor your Cloudinary media pipeline automatically
Better Stack creates synthetic monitors for your Cloudinary upload API and delivery URLs — alerts your team the instant images start failing. Free for small teams.
Try Better Stack Free →What to Do When Cloudinary Is Down
Immediate Triage
- Check status.cloudinary.com for component status
- Identify if Upload API, CDN Delivery, or both are affected
- Test a direct delivery URL to confirm CDN status
- Check if it's affecting all assets or a specific transformation
- Verify API credentials are valid (not an auth issue)
Engineering Response
- Show local placeholder images during CDN outages
- Queue failed uploads and retry when API recovers
- Pre-generate eager transformations for critical assets
- Set up a fallback CDN (e.g., serve originals from S3) for critical images
- Use f_auto,q_auto for all delivery URLs to maximize cacheability
Frequently Asked Questions
Where is the official Cloudinary status page?
Cloudinary's official status page is at status.cloudinary.com. It shows component-level status for Upload API, Delivery (CDN), Admin API, Media Library, and Video Processing. You can subscribe to email or webhook notifications for incident updates.
Why are Cloudinary uploads failing but delivery is fine?
Cloudinary's Upload API and CDN Delivery are separate infrastructure components. During partial outages, the Upload API can be degraded or down while previously uploaded assets continue to deliver normally via CDN. Check status.cloudinary.com to see which specific component is affected.
What does Cloudinary status degraded mean?
Degraded Cloudinary status means the service is operational but slower than normal. You may see higher upload latency, transformation queue delays, or CDN cache-miss response times. Most degraded events resolve within 30-60 minutes. Cache transformed images aggressively using long TTLs to insulate end users from delivery slowdowns.
How do I get alerts when Cloudinary goes down?
Subscribe to email notifications at status.cloudinary.com, or use Better Stack to create synthetic monitors against your Cloudinary delivery URLs. For critical media pipelines, monitor both your upload endpoint and a sample delivery URL to catch component-specific outages.
Is Cloudinary down or is my configuration wrong?
Check status.cloudinary.com first. If the status page shows green but you're seeing errors: verify your cloud name (a typo makes all delivery URLs 404), check your API key/secret, and validate your transformation syntax using the Cloudinary URL builder. Invalid transformations return 400 errors that can look like outages.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Cloudinary goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Cloudinary + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial