Minor impactResolvedMedia

Cloudinary incident: Slow/failing asset delivery & API calls

Cloudinary reported this minor-impact incident on its official status page on May 22, 2025, 15:39 UTC. It was resolved after 4h 6m.

Right now Cloudinary is operational. Live Cloudinary status →

🔔 Get alerted when Cloudinary has issuesFree · email alerts · no credit card
May 22, 2025, 15:39 UTC
started
May 22, 2025, 19:45 UTC
resolved
4h 6m
duration
Minor
impact

Affected components

  • Admin API - US
  • Media Delivery
  • Media Transformation API - US
  • Upload API - US

Timeline

updates from Cloudinary's status page ↗
  1. resolvedMay 22, 2025, 19:45 UTC

    This incident has been resolved.

  2. monitoringMay 22, 2025, 16:23 UTC

    A fix has been implemented and we are monitoring the results.

  3. investigatingMay 22, 2025, 15:39 UTC

    We want to inform you that starting 14:52 UTC, we're investigating slow/failing asset delivery and API calls, affecting a small number of our customers. Our team is actively investigating the issue to identify the root cause and implement a resolution.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudinary's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cloudinary have incidents?

Cloudinary reported 6 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 4h 35m. See Cloudinary's uptime and incident history

← Previous: Notification Management increased response time (webhook) (Apr 27, 2025)Next: Webhook notifications are currently delayed in EU and AP regions (May 30, 2025) →
Cloudinary incident on May 22, 2025: Slow/failing asset delivery & API calls · APIStatus.watch