Cloudinary incident: Saved search fails for SMDs with spaces in name.

Affected components

• Digital Asset Management (DAM)

1. resolvedFeb 26, 2026, 18:22 UTC

   This incident has been resolved.

2. monitoringFeb 26, 2026, 16:27 UTC

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

3. identifiedFeb 26, 2026, 12:50 UTC

   We want to inform you that we have identified an issue affecting Saved Searches when using Structured Metadata fields that contain spaces in their name (for example, “production type”). As a result, some saved searches may not behave as expected. We are currently performing final testing and deploying a fix.

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.

• GitBook: Site wide outageCritical · Feb 26, 2026, 17:15 UTC
• Confluent Cloud: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors ratesMajor · Feb 25, 2026, 05:01 UTC
• Confluent Cloud: Network provisioning service in Azure East US region is degradedMajor · Feb 26, 2026, 13:59 UTC
• LaunchDarkly: Investigating Issues with LaunchDarkly Application and AuthenticationMajor · Feb 26, 2026, 15:43 UTC
• Miro: MCP server performance degradedMinor · Feb 26, 2026, 13:27 UTC

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