Störungsverlauf von Cloudinary

1. 13. August 2026 um 17:04 UTCinvestigating

   Seit ungefähr 12:30 UTC können bei einigen Benutzern Probleme auftreten, bei denen Assets beim Durchsuchen von Ordnern in der Medienbibliothek nicht angezeigt werden. Betroffene Assets bleiben verfügbar und können durch die Suche weiterhin zugänglich sein. Unser Team untersucht das Problem und arbeitet daran, die normale Ordnersichtbarkeit wiederherzustellen. Wir werden ein weiteres Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 13. August 2026 um 19:10 UTCidentified

   We have identified the root cause of the issue affecting asset visibility in the Media Library. Our engineering team is actively working on a resolution. Asset delivery is not impacted. We will provide another update as soon as more information is available.

3. 13. August 2026 um 20:11 UTCmonitoring

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

4. 14. August 2026 um 17:45 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juli 2026 um 13:35 UTCinvestigating

   Seit ungefähr 13:50 UTC können Benutzer keine Add-Ons installieren. Installationsversuche sind fehlgeschlagen und zeigen möglicherweise eine Meldung „Installation failed an. Unser Team untersucht das Problem und arbeitet daran, die Installationsfunktionalität wiederherzustellen. Wir werden ein weiteres Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 29. Juli 2026 um 14:00 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 29. Juli 2026 um 14:58 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 23:09 UTCinvestigating

   Wir untersuchen ein Problem, das Verbindungen zum Cloudinary MCP Connector betrifft. Benutzer können einen 502 Bad Gateway-Fehler erhalten.

2. 21. Juli 2026 um 08:33 UTCmonitoring

   Es wurde ein Fix herausgegeben, um die Verbindungsfehler mit unserem MCP-Anschluss zu beheben, und wir überwachen aktiv, um eine anhaltende Stabilität zu gewährleisten.

3. 21. Juli 2026 um 11:25 UTCresolved

   Das jüngste Problem, das den Cloudinary MCP Connector betrifft, wurde erfolgreich behoben. Wir können bestätigen, dass alle Dienste nun wieder normal funktionieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Juli 2026 um 10:17 UTCresolved

   Aufgrund einer Änderung der Sicherheitsparameter treten bei einigen Kunden Fehler auf, wenn sie versuchen, sich über das Cloudinary Figma-Plugin bei Cloudinary anzumelden (https://www.figma.com/community/plugin/1451492041396730459/cloudinary)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juli 2026 um 10:20 UTCmonitoring

   Ein Problem mit Anfragen, die die g auto-Transformation enthielten, führte zu erhöhten Fehlerraten, die am Sonntag, dem 12. Juli, um etwa 09:00 Uhr UTC begannen. Das Problem ist gelöst, und wir werden es weiterhin beobachten.

2. 12. Juli 2026 um 12:44 UTCresolved

   Der Vorfall wurde behoben. Die Dienste haben sich wieder normalisiert und alle zuvor betroffenen URLs funktionieren jetzt korrekt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 15:19 UTCinvestigating

   We are currently experiencing delays in MediaFlows execution. Some flows may not run immediately after being triggered. Our team is actively investigating the issue. We expect all affected flow runs to be processed, though with delays. We will provide further updates as more information becomes available.

2. 16. Juni 2026 um 17:45 UTCmonitoring

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

3. 17. Juni 2026 um 06:36 UTCresolved

   This incident has been resolved.

1. 7. Juni 2026 um 13:30 UTCinvestigating

   We are currently investigating an issue affecting recently added, deleted, or modified assets that may not appear up to date when viewed via the DAM. The issue began at approximately 1:17 PM UTC on June 7, 2026. Although asset views in the DAM may not be reflected accurately, any actions taken on assets are still being applied, and the API continues to function as usual. Please continue to follow this page for updates, and contact [email protected] if you need any assistance. Thank you!

2. 7. Juni 2026 um 13:54 UTCmonitoring

   The issue was identified, and a fix has been implemented.

3. 8. Juni 2026 um 06:31 UTCresolved

   The issue has been resolved, and all services are operating normally.

1. 24. März 2026 um 16:51 UTCinvestigating

   We want to inform you that starting 16:23 UTC, we're investigating issues affecting our customers relating to displaying/creating API secrets in the Management Console. The usage of API credentials is functioning as intended. Our team is actively investigating the issue to identify the root cause and implement a resolution.

2. 24. März 2026 um 18:18 UTCmonitoring

   We have rolled out a fix on recent issue on displaying/creating API secrets in the Management Console and currently monitoring our system. All services appear to functioning normally.

3. 24. März 2026 um 19:35 UTCresolved

   We confirm that the update rolled out today has fixed the issue.

1. 19. März 2026 um 16:48 UTCinvestigating

   We're currently investigating a reported issue when users are attempting to sign up. Our engineering team is working to restore normal operation, and we will provide further updates shortly.

2. 19. März 2026 um 17:13 UTCmonitoring

   A fix for this issue has been deployed, and we are currently monitoring the results.

3. 19. März 2026 um 18:38 UTCresolved

   The recent sign-up issue has been resolved. All services are now operating normally.

1. 11. März 2026 um 18:19 UTCinvestigating

   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.

2. 11. März 2026 um 20:36 UTCmonitoring

   We have resolved the issues and are monitoring.

3. 12. März 2026 um 09:23 UTCresolved

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

1. 26. Februar 2026 um 12:50 UTCidentified

   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.

2. 26. Februar 2026 um 16:27 UTCmonitoring

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

3. 26. Februar 2026 um 18:22 UTCresolved

   This incident has been resolved.

1. 10. Februar 2026 um 15:44 UTCinvestigating

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

2. 10. Februar 2026 um 17:55 UTCmonitoring

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

3. 11. Februar 2026 um 07:04 UTCresolved

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

1. 10. Februar 2026 um 08:21 UTCidentified

   Started around 04:30 UTC, search API functionality may be non-functional and newly uploaded assets may not be visible in the Media Library.

2. 10. Februar 2026 um 12:02 UTCresolved

   This incident has been resolved.

1. 8. Januar 2026 um 15:47 UTCinvestigating

   Starting 2:45 PM UTC, we are seeing degraded performance when accessing the Media Library via the console and the widget. We are currently investigating the issue.

2. 8. Januar 2026 um 15:56 UTCmonitoring

   Our team identified the cause of the issue and reverted to a known working version. We expect the Media Library's functionality to be fully restored, and we are continually monitoring the status.

3. 8. Januar 2026 um 17:05 UTCresolved

   This incident has been resolved.

1. 4. Januar 2026 um 17:51 UTCinvestigating

   We’re currently experiencing an issue affecting a subset of PDF uploads and deliveries. Some PDF processing operations may fail under specific conditions such as q_auto.

2. 4. Januar 2026 um 19:03 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4. Januar 2026 um 20:38 UTCmonitoring

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

4. 5. Januar 2026 um 07:52 UTCresolved

   A fix has been implemented and this issue has been resolved

1. 4. Januar 2026 um 08:06 UTCmonitoring

   During the weekend, an issue affected Creative Approval workflows, causing them to be unavailable. The issue is now resolved.

2. 4. Januar 2026 um 08:42 UTCresolved

   During the weekend, an issue affected Creative Approval workflows, causing them to be unavailable. The issue is now resolved.

1. 21. Dezember 2025 um 10:50 UTCmonitoring

   At approximately 9:20 AM until 10:20 AM UTC, some users may have experienced outages in the following areas: - Billing dashboard (whole billing submenu) - Plan Upgrade / Downgrade - Signing up for a paid plan Issues were acknowledged quickly, and the system has returned to normal. Cloudinary support is continuing to monitor. Please open a support ticket if you experience any issues or have any questions.

2. 21. Dezember 2025 um 14:43 UTCresolved

   This incident has been resolved.

1. 15. Dezember 2025 um 15:10 UTCidentified

   We are currently working to resolve a reported issue when using both Strict Transformations and the Auto-Upload feature. Until we resolve the issue, you may see "Transformation ... is not allowed" errors on requests that should trigger an auto upload from a remote URL or bucket. Until we resolve the issue, you can work around the issue by temporarily disabling Strict Transformations or using another method to allow the transformation to proceed such as signing the URL or adding an Strict Referral Domain: https://cloudinary.com/documentation/control_access_to_media#strict_transformations

2. 15. Dezember 2025 um 16:51 UTCidentified

   We are working on deploying a fix for this issue; we'll provide a further update after the deployment is complete

3. 15. Dezember 2025 um 17:42 UTCmonitoring

   A fix has been deployed and affected requests should now be working as expected. We'll resolve the incident after some further monitoring.

4. 15. Dezember 2025 um 19:32 UTCresolved

   This incident has been resolved.

1. 10. Dezember 2025 um 12:30 UTCidentified

   Following Yesterday's deployment, we have identified an error in the login flow via the Media Library Widget. Our development team is currently working on a fix.

2. 10. Dezember 2025 um 12:50 UTCmonitoring

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

3. 10. Dezember 2025 um 13:18 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. Dezember 2025 um 13:18 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 09:16 UTCinvestigating

   We are currently investigating an incident where Cloudinary's support site is not accessible. Affected users may be unable to view existing tickets or submit new requests through the portal. Our support portal is powered by a third-party vendor, and the outage does not affect any Cloudinary services. Existing tickets and data are not affected and remain safe.

2. 5. Dezember 2025 um 09:24 UTCidentified

   Cloudinary Support site is now back online and fully accessible. Our team will continue to closely monitor the service to ensure it remains stable.

3. 5. Dezember 2025 um 09:24 UTCmonitoring

   Cloudinary Support site is now back online and fully accessible. Our team will continue to closely monitor the service to ensure it remains stable.

4. 5. Dezember 2025 um 14:04 UTCresolved

   This incident has been resolved.