Webflow 中断历史

1. 2026年9月28日 UTC 10:30investigating

   我们正调查影响某些顾客的出版时间增加。 有些出版物也可能被卡住或返回出错。 我们的小组正在进行调查,一旦我们掌握了更多信息,我们将分享另一个最新情况.

2. 2026年9月28日 UTC 12:32investigating

   我们的团队正在继续调查影响一些客户的出版时间的增加。 我们正在努力了解原因, 我们一旦掌握更多信息.

3. 2026年9月28日 UTC 14:16monitoring

   也不再有积极的影响。 我们的小组继续密切监测局势.

4. 2026年9月28日 UTC 15:04resolved

   我们确认影响出版时间的问题已经解决, 我们感谢你在我们团队努力解决这一问题期间的耐心.

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

1. 2026年9月22日 UTC 13:01investigating

   我们正在调查一些报告, 我们的小组正在进行调查,一旦我们掌握了更多信息,我们将分享另一个最新情况。 同时,仍然可以通过站点设置中的表格标签、MCP和表格提交API端点来审查表格提交.

2. 2026年9月22日 UTC 14:30identified

   我们已确认, 这种行为是由于一个上游供应商的问题引起的。 并尽快恢复发送表格通知电子邮件。 表格本身没有受到影响。 同时,仍可通过网站设置中的表格标签、使用MCP和表格提交API来审查表格提交。 我们赞赏你的持续耐心,并将在获得新信息后立即提供另一个最新情况.

3. 2026年9月22日 UTC 16:03monitoring

   不再有积极的客户影响,现在正在按预期发送表格提交通知电子邮件。 在此事件中,一些客户的通知电子邮件发送受到影响。 继续在现场设置中如期收到和保存提交的表格,网页浏览发送没有受到影响。 我们的小组继续密切监测局势。 我们赞赏你在处理这个问题期间的耐心.

4. 2026年9月22日 UTC 17:05resolved

   这一事件现在已经得到解决。 表格提交通知在协调世界时9月21日00:46至协调世界时9月22日15:33之间受到影响。 提交新的表格现在如所预期地触发通知电子邮件。 在此期间,继续如预期地收到和节省提交表格,网上分发未受影响。 在受影响时间段内未发送的通知电子邮件不会追溯发送。 受影响的客户可通过下列方式从这一时限内审查提交材料: - 站点设置中的窗体标签 - 数据窗体MCP工具 - 提交表格的API终点 我们赞赏你耐心地与我们的上游提供者合作解决这一问题.

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

1. 2026年9月17日 UTC 09:30investigating

   某些客户无法授权MCP在客户工作空间内使用。 受影响的地点可能显得灰了,在批准过程中无法选择。 我们的小组正在积极调查这一问题,并将在我们得到更多信息后立即分享另一个最新情况。 谢谢你的耐心.

2. 2026年9月17日 UTC 09:44identified

   我们查明了影响客户工作空间内某些网站的MCP授权的问题的原因。 我们的团队正在积极努力执行一个解决方案.

3. 2026年9月17日 UTC 10:00monitoring

   一项固定措施已经实施,客户现在应当能够按预期为客户工作空间内的站点授权MCP.

4. 2026年9月17日 UTC 10:12resolved

   这一事件已经得到解决。 感谢您在我们研究这个问题期间的耐心.

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

1. 2026年9月15日 UTC 09:06investigating

   我们正调查关于500个错误的报告, 我们的小组正在积极调查,一旦我们掌握了更多信息,将再次通报最新情况.

2. 2026年9月15日 UTC 10:08investigating

   我们继续调查500个错误的报告, 影响是断断续续的,我们的小组正在继续作为紧急事项进行调查。 我们赞赏你的耐心和理解,并将在下个小时内再次介绍最新情况.

3. 2026年9月15日 UTC 10:34identified

   我们查明了影响一些主办地点的断断续续的500个错误的原因,并正在积极努力解决这一问题。 我们赞赏你的持续耐心,并将在获得新信息后立即提供另一个最新情况.

4. 2026年9月15日 UTC 11:18monitoring

   我们不再看到客户对此问题的影响, 有了新的信息,我们将分享另一个最新情况,并真诚感谢你的耐心.

5. 2026年9月15日 UTC 12:51resolved

   UTC凌晨8:29-9:40左右,一些托管站点在以下短时期内间歇出500个出错: 世界协调时08:29 - 08:35 协调世界时08:42-08:52 协调世界时08:58-09:04 世界协调时09:32–09:40 这主要影响到最近出版的网址。 此事现已解决。 我们真诚赞赏你耐心地对待我们团队的工作.

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

1. 2026年9月14日 UTC 14:31investigating

   我们正在调查关于一些客户的出版尝试失败的报告。 一些客户在进行新采购或更新计划时也可能遇到问题。 这个问题似乎与上游供应商有关,我们的小组正在积极调查。 我们一旦掌握更多信息.

2. 2026年9月14日 UTC 14:44investigating

   一个上游提供者对影响多种网络流量服务的问题采取了补救措施。 一些客户在出版、分析和优化等服务方面可能继续遇到问题。 我们继续和上游供应商合作, 我们一旦掌握更多信息.

3. 2026年9月14日 UTC 15:02monitoring

   我们的上游供应商已经实施了一个固定方案, 我们的小组正在继续密切监测局势,并将在获得新信息后提供最新情况.

4. 2026年9月14日 UTC 15:19resolved

   在持续监测之后,我们确认影响多种网络流量服务的问题已经解决。 这一事件现已了结. 我们赞赏你耐心地与我们的上游提供者合作解决这一问题.

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

1. 2026年8月25日 UTC 22:00investigating

   我们继续调查503个错误的报告, 我们的小组正在积极调查,一旦我们掌握了更多信息,将再次通报最新情况.

2. 2026年8月25日 UTC 22:09monitoring

   我们正看到服务恢复到预期的绩效水平, 我们的小组继续密切监测局势.

3. 2026年8月25日 UTC 23:57monitoring

   一些主机网站Webflow.com和MCP Server经历了503个错误. 此事现已解决。 我们赞赏你耐心地努力解决这一问题.

4. 2026年8月25日 UTC 23:58resolved

   这一事件已经得到解决.

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

1. 2026年8月12日 UTC 16:36investigating

   We’re investigating reports that some customers may intermittently experience issues creating new sites or loading the Webflow Canvas. Our team is actively investigating and will share another update as soon as we have more information.

2. 2026年8月12日 UTC 19:04investigating

   We’re continuing to investigate an issue that may intermittently prevent some customers from creating or duplicating sites, creating or viewing page branches, previewing site backups, or loading the Webflow Canvas. Our team is working to resolve these issues and will share additional information as it becomes available.

3. 2026年8月12日 UTC 20:24identified

   Our team has identified the cause and is working on a resolution. In the meantime, customers may intermittently encounter errors when creating or duplicating sites, creating or viewing page branches, previewing site backups, or loading the Webflow Canvas. We’ll provide further updates as work continues.

4. 2026年8月12日 UTC 22:05monitoring

   We're no longer seeing customer impact related to this issue. Our team is continuing to monitor the situation closely and will provide another update as soon as possible.

5. 2026年8月13日 UTC 01:18resolved

   Some customers intermittently experienced issues creating or duplicating sites, creating or viewing page branches, previewing site backups, or loading the Webflow Canvas between 13:40 and 20:45 UTC today. We’re no longer seeing customer impact related to this issue, and this incident is now resolved. We appreciate your patience while we worked to resolve this issue.

1. 2026年8月5日 UTC 15:27investigating

   We're investigating reports of some customers being unable to open the management experience for Optimize on non-Webflow sites. Our team is actively investigating and we'll share another update as soon as we have more information. Live optimizations are not affected and continue to run.

2. 2026年8月5日 UTC 15:45monitoring

   We've identified the cause of this issue and applied a fix. The Optimize dashboard for non-Webflow sites should now be loading normally. We're continuing to monitor to confirm the issue is fully resolved.

3. 2026年8月5日 UTC 15:59resolved

   This issue has been resolved. The Optimize management experience for non-Webflow sites is loading normally. Live optimizations running on customer sites were not affected at any point. Thank you for your patience.

1. 2026年7月28日 UTC 01:18investigating

   我们正在调查有报道说, 外出网络呼号没有像预期的那样交付。 我们的小组正在积极调查这一问题并努力查明根源。 请注意,继续收到表格和表格电子邮件通知,可在网站设置内的表格标签中加以审查。 我们一收到更多信息 就会再分享最新消息.

2. 2026年7月28日 UTC 01:48identified

   我们已经确定了影响即将离任的Webhooks的问题。 客户配置的Webhooks目前失败,没有按预期交付。 我们的工程组正在积极努力恢复Webhook的交付. 表格和表格通知电子邮件正常运行,不受这一问题的影响。 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.

3. 2026年7月28日 UTC 02:13resolved

   3:00 PT至6:35 PM PT, 客户配置出站的网络呼声并未如预期的那样交付. 这个问题现已解决,出站的网络浏览服务正在正常运行。 在此期间收到的任何表格呈件仍然得到成功的处理,并保留在网站设置内的表格标签中.

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

1. 2026年7月19日 UTC 05:14investigating

   我们正调查关于间歇性出错的报告, 并正在积极调查此事。 我们的工程小组正在紧急开展工作,以查明根源并恢复预期业绩。 一旦获得更多信息,我们将分享另一个最新情况.

2. 2026年7月19日 UTC 06:10monitoring

   我们不再看到客户对此问题的影响, 我们的小组已实施缓解措施并正在继续密切监测局势。 我们将继续观察服务业绩, 我们感谢你在调查这起事件时的耐心.

3. 2026年7月19日 UTC 14:00resolved

   经过一段时间的监测,我们可以确认我们的减缓工作取得了成功,现场业绩已恢复到预期水平。 这一事件现已得到解决。 一些带有CMS内容的主机页面在以下窗口中可能出现间歇性5xx出错,每个窗口持续几分钟(UTC): 1. - 01:27 - 01:31 (英语). - 01:39-01:41 (英语). - 01:51-01:53 - 04:47 - 04:50 - (英语). - 05:02 - 05:03 (英语). 我们赞赏你在努力调查和解决问题时的耐心.

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

1. 2026年7月15日 UTC 00:21investigating

   有些顾客无法登录Webflow。 我们的小组正在积极调查这一问题并努力查明根源。 我们一旦掌握更多信息, 谢谢你的耐心.

2. 2026年7月15日 UTC 00:23investigating

   我们正在继续调查这一问题.

3. 2026年7月15日 UTC 00:39monitoring

   我们已实施缓解措施, 我们继续密切监测情况, 谢谢你的耐心.

4. 2026年7月15日 UTC 02:46resolved

   这一事件现已得到解决。 一些顾客在协调世界时7月14日23:30至协调世界时7月15日00:30之间经历了向Webflow的伐木问题. 我们不再看到客户对此问题的影响。 谢谢你在我们努力解决这个问题期间的耐心.

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

1. 2026年7月9日 UTC 21:49monitoring

   我们重开之前的事件,因为推荐的缓解只暂时解决了这个问题,一些用户可能看到Webflow MCP工具无法在克洛德桌面和claude.ai中加载. Webflow MCP服务器正常运行,与包括克洛德代码在内的其他所有代理合作. 这个问题发生在使用克洛德桌面和claude.ai时. 当一个会话在克洛德桌面或claude.ai中被刷新时,完整的工具列表并不总是重新装入. 我们正在和Anthropic合作 找出一个持久的解决方案。 同时,这项工作恢复了您本届会议的全部工具列表: 1. 转到设置 2. 选择连接器 3. 点击网络流量连接器 4. 打开三点菜单 5. 选择刷新工具列表 请注意,这是临时工作,不是固定的。 工具列表将只恢复您的当前会话 。 重启或刷新浏览器或桌面应用会导致问题回落,需要重复以上步骤. 我们一有消息就发布 谢谢你的耐心.

2. 2026年7月10日 UTC 19:31monitoring

   我们正在继续与Anthropic合作,以实施更持久的解决方案。 Webflow MCP服务器正常运行,并与所有其他代理商合作. 这个问题会影响到克洛德桌面,claude.ai,并可能根据配置影响克洛德代码. 作为一个工作,我们建议使用通过命令线配置的克洛德代码. 它直接连接到Webflow MCP服务器而不是通过克洛德连接器,因此它不受当前会话刷新行为的影响. 设置指令可在此查阅:https://developers.webflow.com/mcp/install/claude-code 我们赞赏你继续耐心和理解,并将在获得新信息后立即提供另一个最新情况.

3. 2026年7月16日 UTC 02:17monitoring

   更改已部署到 Webflow MCP 服务器,该服务器应恢复克洛德桌面应用程序和claude.ai中的完整工具列表. 所有Webflow MCP工具现在都应在克洛德连接器中提供. 如果您仍然无法访问完整的工具列表, 请尝试重新启动 Claude 桌面或在浏览器中刷新 claude.ai 。 我们将继续监测局势,同时确认在各届会议上所作的决定。 谢谢你的耐心 在我们努力解决这个问题时.

4. 2026年7月16日 UTC 15:22monitoring

   我们正在继续监测任何其他问题.

5. 2026年7月16日 UTC 16:16resolved

   影响克劳德桌面应用程序和claude.ai中某些Webflow MCP服务器工具可用性的问题现已解决. 所有Webflow MCP工具现在都应在克洛德连接器中提供. 如果您以前经历过丢失的工具, 重新启动 Claude 桌面或刷新 claude.ai 可能有助于确保显示最新的工具列表 。 我们不再看到客户对此问题的影响。 谢谢你在我们努力解决问题时的耐心.

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

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

   我们正在调查Webflow MCP服务器中缺少以下工具的报告:data cms tool,data pages tool,data scripts tool,data element tool,和data 可变 tool. 同时,我们建议通过Webflow Canvas手动进行相应的行动。 我们对此造成的任何不便表示歉意,并将尽快分享另一个最新情况.

2. 2026年7月8日 UTC 13:50investigating

   我们发现这个问题正在影响克洛德桌面应用,一些MCP服务器工具可能无法使用. 作为工作,客户可以通过克洛德CLI继续使用Webflow MCP服务器,同时我们努力解决这个问题. 我们的团队正在积极调查,一旦掌握更多信息,我们将分享另一个最新情况. 谢谢你的耐心.

3. 2026年7月8日 UTC 15:28monitoring

   Webflow MCP服务器目前按预期运行. 然而,一些使用克勞德應用程式的客户可能没有看到所有可用的Webflow MCP服务器工具. 如果您正在经历这个问题,您可以通过以下步骤刷新工具列表: 1. 转到设置。 2. 选择连接器。 3. 点击Web流量连接器。 4. 点击三点菜单。 5. 选择刷新工具列表。 我们正在继续密切监测局势。 谢谢你的耐心 在我们努力解决这个问题时.

4. 2026年7月8日 UTC 18:34resolved

   Webflow MCP 服务器正在按预期运行,这一事件现已解决. 如果 Claude 应用程序中还缺少任何工具, 请遵循这些步骤刷新工具列表 : 1. 转到设置。 2. 选择连接器。 3. 点击Web流量连接器。 4. 点击三点菜单。 5. 选择刷新工具列表。 谢谢你的耐心 在我们努力解决这个问题时.

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

1. 2026年7月8日 UTC 09:52resolved

   在协调世界时7月6日20:22至协调世界时7月8日08:40之间,一些主机站点上少数响应性图像变体在一些请求中还原出403个错误. 这个问题仅限于极少数响应性图像变体,并不影响所有图像或所有托管站点。 如果您的站点受到这个问题的影响, 您可以通过重置您的站点来恢复访问受影响的图像变体 。 我们对该问题造成的任何不便表示诚挚的歉意,并感谢你在我们努力解决这一问题期间的耐心和理解.

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

1. 2026年7月2日 UTC 02:38investigating

   我们正调查关于一些主机站点加载速度比预期慢的报告, 目前我们正与上游供应商调查一个问题, 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.

2. 2026年7月2日 UTC 02:48identified

   这个问题与上游供应商有关。 少数客户在主机站点的加载时间可能继续较慢,或SSL证书提供速度也较慢. 我们的小组正在积极监测局势,并与我们的上游提供者合作。 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.

3. 2026年7月2日 UTC 04:12monitoring

   我们的上游供应商实施了一个固定,我们看到主机站点加载时间和SSL证书提供恢复到预期的性能水平。 我们继续密切监测情况.

4. 2026年7月2日 UTC 10:59resolved

   在协调世界时约00:00至协调世界时04:05之间,一些托管站点的加载时间较慢,由于上游供应商存在问题,SSL证书的提供时间比预期的要长. 我们不再看到 客户的影响与此问题有关。 经过我们上游供应商的确认和我们小组的核实,这一事件现已得到解决。 谢谢你的耐心 在我们的上游供应商努力解决这个问题期间.

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

1. 2026年6月11日 UTC 20:44monitoring

   Earlier today, a small number of hosted sites experienced intermittent 500 errors. We identified the cause of the issue and implemented mitigation measures. We’re no longer seeing active customer impact related to this issue, and affected sites have returned to normal operation. Our team is continuing to monitor the situation closely and will provide further updates as needed. Thank you for your patience.

2. 2026年6月11日 UTC 22:20resolved

   A small number of hosted sites experienced intermittent 500 errors between 20:04 UTC and 20:27 UTC. We identified the cause of the issue and implemented mitigation measures. We’re no longer seeing customer impact related to this issue, and affected sites have returned to normal operation. This incident is now resolved. Thank you for your patience while we worked to address this issue.

1. 2026年6月5日 UTC 23:42resolved

   An issue was identified that impacted access to Webflow services for some customers between 22:45 and 23:20 UTC. Our Engineering team has since mitigated the issue and restored affected services to expected performance levels. We appreciate your patience while we worked to restore service.

1. 2026年5月20日 UTC 17:29resolved

   We’re no longer seeing customer impact related to this issue, and access to Webflow services has returned to normal. Some customers experienced issues accessing Webflow between 15:15 UTC and 15:37 UTC. This incident is now resolved. We appreciate your patience while our team worked to restore normal functionality. Affected Components: Dashboard → Operational Webflow Canvas → Operational Webflow.com → Operational

1. 2026年5月18日 UTC 12:52investigating

   We’re investigating reports that some customers are unable to publish. Our team is actively working to identify the cause and will share another update as soon as we have more information.

2. 2026年5月18日 UTC 14:00investigating

   We’re continuing to investigate publishing issues impacting some customers. Our engineering team is actively working to identify the root cause and evaluate mitigation steps to restore normal publishing functionality. We’ll provide another update within the next hour or sooner if additional information becomes available.

3. 2026年5月18日 UTC 14:14identified

   We’ve identified the cause of the publishing issues impacting some customers. We’re beginning to see recovery in the publishing functionality while mitigation work continues. Our team is actively monitoring progress and will share another update as more information becomes available.

4. 2026年5月18日 UTC 15:51monitoring

   We implemented a fix for the publishing issues impacting some customers and are now seeing publishing functionality operating as expected. Our team is continuing to monitor the platform closely and will provide further updates if needed.

5. 2026年5月18日 UTC 16:47resolved

   Publishing functionality has remained stable following the mitigation work completed earlier, and we’re no longer seeing customer impact related to this issue. Some customers experienced issues publishing between 12:50 UTC and 16:18 UTC on May 18, 2026. This incident is now resolved. We appreciate your patience while our team worked to restore normal functionality.

1. 2026年4月14日 UTC 14:15investigating

   We are currently investigating reports of 5xx errors affecting some hosted sites, as well as issues loading the Dashboard. Our team is actively investigating the root cause and working to restore normal service as quickly as possible. We will share another update as soon as possible.

2. 2026年4月14日 UTC 14:47investigating

   We are continuing to investigate an issue causing 5xx errors on some hosted sites and preventing the Dashboard, Webflow Canvas, and Webflow.com from loading as expected. We are actively working to identify the root cause and restore normal service as quickly as possible. If you are able to access the Dashboard or interact with sites via our public API, we recommend refraining from republishing sites at this time while we work to resolve the issue. We will share another update as soon as more information becomes available.

3. 2026年4月14日 UTC 15:16investigating

   We are continuing to investigate an issue causing 5xx errors on some hosted sites and preventing the Dashboard, Webflow Canvas, and Webflow.com from loading as expected as a matter of urgency. We have also identified that the public API and form submissions are impacted. We sincerely appreciate your patience and understanding as we work to resolve this incident.

4. 2026年4月14日 UTC 16:32investigating

   We are continuing to investigate an issue impacting the following services: Hosted Sites, Dashboard, Webflow Canvas, Form submissions, Public API, and Webflow.com. Our team is making progress and remains fully engaged in resolving this issue as quickly as possible. Current efforts include: - Implementing mitigation actions aimed at reducing number of impacted sites - Working closely with our upstream cloud provider to investigate and identify further possible mitigation actions If you are able to access the Dashboard or interact with sites via the API, we recommend refraining from republishing sites at this time while we continue to stabilize our services. We understand the disruption this is causing and truly appreciate your continued patience. We will share another update as soon as more information becomes available.

5. 2026年4月14日 UTC 16:49investigating

   We have made significant progress in mitigating the issue impacting hosted sites, the Dashboard, Webflow Canvas, Webflow.com, Form submissions and the Public API. As a result, service has now been restored for the majority of customers. Our entire team remains fully engaged and is focused on resolving the issue for all remaining customers. We will continue to share updates as this work progresses. We appreciate your continued patience and understanding as we work toward full resolution.

6. 2026年4月14日 UTC 18:07investigating

   We have made further progress in mitigating this issue, and at this time only a small number of sites remain impacted. Sites that remain impacted by this issue may experience the following: - CMS items not loading as expected or appearing as missing inside the CMS Data Manager - Issues working on CMS pages and/or pages with Collection Lists in the Webflow Canvas - Hosted site pages failing to load with 5xx errors - Errors when publishing As we continue working toward full resolution with the active and urgent support of our upstream provider, we have temporarily disabled backup creation and corresponding restore actions out of an abundance of caution for all customers. Existing backup versions already created remain stable and unaffected. Our team remains actively focused on resolving the issue for all impacted sites and restoring full functionality. We will continue to share updates as progress is made.We appreciate your continued patience.

7. 2026年4月14日 UTC 19:29investigating

   We are continuing to work urgently with our upstream storage provider to identify the best path forward to restore full service on the subset of sites that remain impacted by this issue. We recognize the impact this issue is having for the remaining customers impacted and our entire team remains focused on resolving this incident as soon as possible.

8. 2026年4月14日 UTC 20:01investigating

   We are continuing to investigate this issue.

9. 2026年4月14日 UTC 21:13investigating

   We are continuing to work with an upstream provider to restore full service for the small number of sites that remain impacted by this issue. At this time, our team is actively monitoring progress and awaiting further updates. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. We recommend refraining from restoring sites while we continue to stabilize services. We will continue to share updates as progress is made.

10. 2026年4月14日 UTC 22:23identified

    We have identified the underlying issue and are preparing to implement changes with an upstream provider to help restore service for the small number of sites that remain impacted by this issue. At this time, our team is monitoring progress closely as this work moves forward. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

11. 2026年4月14日 UTC 23:48identified

    We are continuing to implement changes in coordination with an upstream provider to restore service for the small number of sites that remain impacted by this issue. Our team remains actively engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

12. 2026年4月15日 UTC 01:19identified

    We are continuing to implement changes in coordination with an upstream provider and are making progress toward restoring service for the small number of sites that remain impacted by this issue. Our team remains fully engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

13. 2026年4月15日 UTC 02:40identified

    We are continuing to implement changes in coordination with an upstream provider as we work through the remaining steps required to restore service for the small number of sites still impacted by this issue. Our team remains fully engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

14. 2026年4月15日 UTC 03:48identified

    We’re continuing to work closely with an upstream provider to implement additional changes aimed at resolving this issue. While we’ve seen improvement, a small number of sites may still experience intermittent errors or difficulty accessing Webflow services. Our team remains actively engaged and is monitoring progress as these changes are rolled out. We understand the ongoing impact and appreciate your continued patience while we work toward full resolution. For impacted sites, we still recommend holding off on restoring or publishing until services are fully stabilized. We’ll share another update as soon as more information becomes available.

15. 2026年4月15日 UTC 04:08monitoring

    A fix has been implemented in coordination with an upstream provider, and we’re no longer seeing customer impact related to this issue. If you continue to experience issues, we recommend clearing your browser cache and retrying. We’ll continue to monitor closely to ensure services remain stable. Thank you for your patience while we worked to resolve this.

16. 2026年4月15日 UTC 05:23monitoring

    We’re continuing to monitor the situation following the fix implemented in coordination with an upstream provider. At this time, we’re seeing stable performance and are not observing further customer impact. Our team remains actively engaged and is watching closely to ensure services continue operating as expected. If you continue to experience issues, we recommend retrying your request or clearing your browser cache. We’ll share another update as soon as we have additional information. Thank you again for your patience while we worked through this.

17. 2026年4月15日 UTC 06:08resolved

    This incident that started at 14:15 UTC on April 14th is now resolved. By 16:21 UTC on April 14th, the issue was mitigated for the overwhelming majority of customers (~96%). For a full timeline, details on root cause and action items, you can refer to the following blog post prepared by our CTO, Allan Leinwand: webflow.com/blog/april-14-webflow-incident-report We know this incident caused serious disruption, and sincerely appreciate your patience while we worked to resolve it.