Cloudinary 中断历史

1. 2026年10月24日 UTC 07:03resolved

   2026年10月23日,鲁比项目发布了其正则表达式引擎(CVE-2026-89078,CVE-2026-93577,CVE-2026-97229,CVE-2026-110264)中漏洞的安全修复. Cloudinary将其核心平台升级,包括上传,变换,以及交付API和Console,同日被补丁的Ruby版本. 我们的审查没有发现任何剥削证据,对客户或客户数据也没有影响。 您无需为云层平台采取行动。 客户在自己的应用中使用Ruby,包括使用Cloudinary Ruby SDK,应当将环境中的Ruby更新为补丁发布(3.3.13,3.4.12,4.0.9或后期).

自动翻译自官方事件更新。

1. 2026年10月21日 UTC 18:22resolved

   Regarding the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 Cloudinary’s core platform, including its upload, transformation, and delivery APIs and Console, does not use PHP and is not affected by these vulnerabilities. Please note that customers who use the Cloudinary PHP SDK in their own applications should update PHP in their respective environments

1. 2026年10月16日 UTC 20:06investigating

   我们正在调查一个影响云端网络UI的问题。 有些用户可能无法登录或使用Console与Media库. 我们的工程组正在积极研究。 使用API证书的图像和视频发送,上传和API请求不受影响. 一旦掌握更多信息,我们将发布另一份最新情况.

2. 2026年10月16日 UTC 21:08monitoring

   已经针对影响UI和操纵台的问题实施了一个固定方案。 我们现在正在监测该制度,以确保稳定。 仍然看到错误的用户应当刷新页面并再次登录.

3. 2026年10月16日 UTC 21:53resolved

   这一事件已经得到解决。 包括登录在内的UI和控制台正常运行. 我们为不方便而道歉.

自动翻译自官方事件更新。

1. 2026年10月5日 UTC 12:20resolved

   在协调世界时2026年10月5日约11:29至12:02之间,云端控制台Dashboard上的用法报告无法提供. 这一问题已得到解决,使用报告功能已完全恢复.

自动翻译自官方事件更新。

1. 2026年9月28日 UTC 09:58identified

   目前我们正在调查欧盟地区影响上传(eager transformation),转型和交付的错误率上升. 发行时间为协调世界时6:15左右. 一旦获得更多信息,我们将提供最新资料.

2. 2026年9月28日 UTC 10:08monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年9月28日 UTC 14:33resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 17:04investigating

   Since approximately 12:30 UTC, some users may experience issues where assets not appearing when browsing folders in the Media Library. Affected assets remain available and may still be accessible through search. Our team is investigating the issue and working to restore normal folder visibility. We will provide another update as soon as more information is available.

2. 2026年8月13日 UTC 19:10identified

   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. 2026年8月13日 UTC 20:11monitoring

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

4. 2026年8月14日 UTC 17:45resolved

   This incident has been resolved.

1. 2026年7月29日 UTC 13:35investigating

   自UTC约13:50起,用户无法安装加载. 安装尝试失败,可能显示“安装失败”信息。 我们的小组正在调查这一问题并努力恢复安装功能。 一旦获得更多信息,我们将提供另一个最新情况.

2. 2026年7月29日 UTC 14:00monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月29日 UTC 14:58resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月20日 UTC 23:09investigating

   我们正在调查一个影响 连接云层MCP连接器的问题。 用户可能会收到502 Bad Gateway错误.

2. 2026年7月21日 UTC 08:33monitoring

   已经发布了一项解决与我们的多氯联苯连接器连接失败的固定办法,我们正在积极监测以确保持续稳定.

3. 2026年7月21日 UTC 11:25resolved

   最近影响"云相"MCP连接器的问题已成功解决. 我们可以确认所有服务现已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 10:17resolved

   由于安全参数的变化,一些客户试图通过Cloudinary Figma插件(https://www.figma.com/community/plugin/1451492041396730459/cloudinary)登录到Cloudinary时遭遇失败

自动翻译自官方事件更新。

1. 2026年7月12日 UTC 10:20monitoring

   影响请求的问题包括g auto转换,导致误差率从协调世界时7月12日星期日约09:00起上升。 这个问题已经解决,我们正在继续监测.

2. 2026年7月12日 UTC 12:44resolved

   此事已决. 服务已经恢复正常,所有先前受影响的URL现在都正常运行.

自动翻译自官方事件更新。

1. 2026年6月16日 UTC 15:19investigating

   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. 2026年6月16日 UTC 17:45monitoring

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

3. 2026年6月17日 UTC 06:36resolved

   This incident has been resolved.

1. 2026年6月7日 UTC 13:30investigating

   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. 2026年6月7日 UTC 13:54monitoring

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

3. 2026年6月8日 UTC 06:31resolved

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

1. 2026年3月24日 UTC 16:51investigating

   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. 2026年3月24日 UTC 18:18monitoring

   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. 2026年3月24日 UTC 19:35resolved

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

1. 2026年3月19日 UTC 16:48investigating

   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. 2026年3月19日 UTC 17:13monitoring

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

3. 2026年3月19日 UTC 18:38resolved

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

1. 2026年3月11日 UTC 18:19investigating

   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. 2026年3月11日 UTC 20:36monitoring

   We have resolved the issues and are monitoring.

3. 2026年3月12日 UTC 09:23resolved

   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. 2026年2月26日 UTC 12:50identified

   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. 2026年2月26日 UTC 16:27monitoring

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

3. 2026年2月26日 UTC 18:22resolved

   This incident has been resolved.

1. 2026年2月10日 UTC 15:44investigating

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

2. 2026年2月10日 UTC 17:55monitoring

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

3. 2026年2月11日 UTC 07:04resolved

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

1. 2026年2月10日 UTC 08:21identified

   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. 2026年2月10日 UTC 12:02resolved

   This incident has been resolved.

1. 2026年1月8日 UTC 15:47investigating

   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. 2026年1月8日 UTC 15:56monitoring

   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. 2026年1月8日 UTC 17:05resolved

   This incident has been resolved.

1. 2026年1月4日 UTC 17:51investigating

   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. 2026年1月4日 UTC 19:03identified

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

3. 2026年1月4日 UTC 20:38monitoring

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

4. 2026年1月5日 UTC 07:52resolved

   A fix has been implemented and this issue has been resolved