API and service
Cloudinary: status and incident history today
Cloudinary Status shows no open incidents right now.
Last checked against Cloudinary Status.
Status now
No open incidents or maintenance right now.
6 incidents in the last 90 days (2 major). Most recent major: “Issues accessing the Cloudinary web UI” (2026-10-16).
Alternatives
AWS S3
Industry-standard object storage service
Strengths
- Highly durable (99.999999999%)
- Scalable to exabytes
Trade-offs
- AWS vendor lock-in
- Eventual consistency (some operations)
Google Cloud Storage
GCP object storage with global edge caching
Strengths
- Strong consistency
- Global CDN integration
Trade-offs
- GCP vendor lock-in
- Smaller ecosystem than S3
Azure Blob Storage
Microsoft Azure object storage service
Strengths
- Deep Azure ecosystem integration
- Multiple access tiers (hot, cool, archive)
Trade-offs
- Azure vendor lock-in
- Smaller ecosystem than S3
Backblaze B2
Cost-effective S3-compatible object storage
Strengths
- S3-compatible API
- Free egress to CDN partners (Cloudflare)
Trade-offs
- Smaller ecosystem than S3/GCS
- Limited regional availability
Docs and release notes
Check Cloudinary in your own stack
This page checks Cloudinary in general. Your repo pins specific versions: the free dependency check reads your manifests and lists what to fix first. Prism Agent runs the same live checks on your whole stack and turns them into a plan your coding agent can build.