Minor impactResolvedMedia

Cloudinary incident: Issues with MediaFlows Event Triggers

Cloudinary reported this minor-impact incident on its official status page on Mar 11, 2026, 18:19 UTC. It was resolved after 15h 5m.

Right now Cloudinary is operational. Live Cloudinary status →

🔔 Get alerted when Cloudinary has issuesFree · email alerts · no credit card
Mar 11, 2026, 18:19 UTC
started
Mar 12, 2026, 09:23 UTC
resolved
15h 5m
duration
Minor
impact

Affected components

  • Flow Engine

Timeline

updates from Cloudinary's status page ↗
  1. resolvedMar 12, 2026, 09:23 UTC

    The recent issue impacting MediaFlows, where some event-based triggers did not execute as expected, has been resolved. All services are now operating normally.

  2. monitoringMar 11, 2026, 20:36 UTC

    We have resolved the issues and are monitoring.

  3. investigatingMar 11, 2026, 18:19 UTC

    We want to inform you that we have identified an issue affecting MediaFlows where some event-based triggers may not execute as expected. As a result, certain MediaFlows may not run when triggered by events such as metadata updates. Our engineering team is working to restore normal operation, and we will provide further updates shortly.

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: Saved search fails for SMDs with spaces in name. (Feb 26, 2026)Next: Errors with Account Creation (Mar 19, 2026) →
Cloudinary incident on Mar 11, 2026: Issues with MediaFlows Event Triggers · APIStatus.watch