Minor impactResolvedMedia

Cloudinary incident: High latency when using the Cloudinary console

Cloudinary reported this minor-impact incident on its official status page on Feb 10, 2026, 15:44 UTC. It was resolved after 15h 20m.

Right now Cloudinary is operational. Live Cloudinary status →

🔔 Get alerted when Cloudinary has issuesFree · email alerts · no credit card
Feb 10, 2026, 15:44 UTC
started
Feb 11, 2026, 07:04 UTC
resolved
15h 20m
duration
Minor
impact

Affected components

  • Digital Asset Management (DAM)
  • Management Console

Timeline

updates from Cloudinary's status page ↗
  1. resolvedFeb 11, 2026, 07:04 UTC

    The issue has been resolved, and system performance has returned to normal.

  2. monitoringFeb 10, 2026, 17:55 UTC

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

  3. investigatingFeb 10, 2026, 15:44 UTC

    From 2:30 PM UTC, we are seeing degraded performance when accessing the Cloudinary console. We are currently investigating the issue.

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: Search API and Media Library Issues (Feb 10, 2026)Next: Saved search fails for SMDs with spaces in name. (Feb 26, 2026) →
Cloudinary incident on Feb 10, 2026: High latency when using the Cloudinary console · APIStatus.watch