60 Webflow incidents · 2025年2月 — official updates, affected components, duration and resolution details.
我们继续调查503个错误的报告, 我们的小组正在积极调查,一旦我们掌握了更多信息,将再次通报最新情况.
我们正看到服务恢复到预期的绩效水平, 我们的小组继续密切监测局势.
一些主机网站Webflow.com和MCP Server经历了503个错误. 此事现已解决。 我们赞赏你耐心地努力解决这一问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
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.
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.
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.
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.
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.
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.
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.
我们正在调查有报道说, 外出网络呼号没有像预期的那样交付。 我们的小组正在积极调查这一问题并努力查明根源。 请注意,继续收到表格和表格电子邮件通知,可在网站设置内的表格标签中加以审查。 我们一收到更多信息 就会再分享最新消息.
我们已经确定了影响即将离任的Webhooks的问题。 客户配置的Webhooks目前失败,没有按预期交付。 我们的工程组正在积极努力恢复Webhook的交付. 表格和表格通知电子邮件正常运行,不受这一问题的影响。 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.
3:00 PT至6:35 PM PT, 客户配置出站的网络呼声并未如预期的那样交付. 这个问题现已解决,出站的网络浏览服务正在正常运行。 在此期间收到的任何表格呈件仍然得到成功的处理,并保留在网站设置内的表格标签中.
自动翻译自官方事件更新。
我们正调查关于间歇性出错的报告, 并正在积极调查此事。 我们的工程小组正在紧急开展工作,以查明根源并恢复预期业绩。 一旦获得更多信息,我们将分享另一个最新情况.
我们不再看到客户对此问题的影响, 我们的小组已实施缓解措施并正在继续密切监测局势。 我们将继续观察服务业绩, 我们感谢你在调查这起事件时的耐心.
经过一段时间的监测,我们可以确认我们的减缓工作取得了成功,现场业绩已恢复到预期水平。 这一事件现已得到解决。 一些带有CMS内容的主机页面在以下窗口中可能出现间歇性5xx出错,每个窗口持续几分钟(UTC): 1. - 01:27 - 01:31 (英语). - 01:39-01:41 (英语). - 01:51-01:53 - 04:47 - 04:50 - (英语). - 05:02 - 05:03 (英语). 我们赞赏你在努力调查和解决问题时的耐心.
自动翻译自官方事件更新。
有些顾客无法登录Webflow。 我们的小组正在积极调查这一问题并努力查明根源。 我们一旦掌握更多信息, 谢谢你的耐心.
我们正在继续调查这一问题.
我们已实施缓解措施, 我们继续密切监测情况, 谢谢你的耐心.
这一事件现已得到解决。 一些顾客在协调世界时7月14日23:30至协调世界时7月15日00:30之间经历了向Webflow的伐木问题. 我们不再看到客户对此问题的影响。 谢谢你在我们努力解决这个问题期间的耐心.
自动翻译自官方事件更新。
我们重开之前的事件,因为推荐的缓解只暂时解决了这个问题,一些用户可能看到Webflow MCP工具无法在克洛德桌面和claude.ai中加载. Webflow MCP服务器正常运行,与包括克洛德代码在内的其他所有代理合作. 这个问题发生在使用克洛德桌面和claude.ai时. 当一个会话在克洛德桌面或claude.ai中被刷新时,完整的工具列表并不总是重新装入. 我们正在和Anthropic合作 找出一个持久的解决方案。 同时,这项工作恢复了您本届会议的全部工具列表: 1. 转到设置 2. 选择连接器 3. 点击网络流量连接器 4. 打开三点菜单 5. 选择刷新工具列表 请注意,这是临时工作,不是固定的。 工具列表将只恢复您的当前会话 。 重启或刷新浏览器或桌面应用会导致问题回落,需要重复以上步骤. 我们一有消息就发布 谢谢你的耐心.
我们正在继续与Anthropic合作,以实施更持久的解决方案。 Webflow MCP服务器正常运行,并与所有其他代理商合作. 这个问题会影响到克洛德桌面,claude.ai,并可能根据配置影响克洛德代码. 作为一个工作,我们建议使用通过命令线配置的克洛德代码. 它直接连接到Webflow MCP服务器而不是通过克洛德连接器,因此它不受当前会话刷新行为的影响. 设置指令可在此查阅:https://developers.webflow.com/mcp/install/claude-code 我们赞赏你继续耐心和理解,并将在获得新信息后立即提供另一个最新情况.
更改已部署到 Webflow MCP 服务器,该服务器应恢复克洛德桌面应用程序和claude.ai中的完整工具列表. 所有Webflow MCP工具现在都应在克洛德连接器中提供. 如果您仍然无法访问完整的工具列表, 请尝试重新启动 Claude 桌面或在浏览器中刷新 claude.ai 。 我们将继续监测局势,同时确认在各届会议上所作的决定。 谢谢你的耐心 在我们努力解决这个问题时.
我们正在继续监测任何其他问题.
影响克劳德桌面应用程序和claude.ai中某些Webflow MCP服务器工具可用性的问题现已解决. 所有Webflow MCP工具现在都应在克洛德连接器中提供. 如果您以前经历过丢失的工具, 重新启动 Claude 桌面或刷新 claude.ai 可能有助于确保显示最新的工具列表 。 我们不再看到客户对此问题的影响。 谢谢你在我们努力解决问题时的耐心.
自动翻译自官方事件更新。
我们正在调查Webflow MCP服务器中缺少以下工具的报告:data cms tool,data pages tool,data scripts tool,data element tool,和data 可变 tool. 同时,我们建议通过Webflow Canvas手动进行相应的行动。 我们对此造成的任何不便表示歉意,并将尽快分享另一个最新情况.
我们发现这个问题正在影响克洛德桌面应用,一些MCP服务器工具可能无法使用. 作为工作,客户可以通过克洛德CLI继续使用Webflow MCP服务器,同时我们努力解决这个问题. 我们的团队正在积极调查,一旦掌握更多信息,我们将分享另一个最新情况. 谢谢你的耐心.
Webflow MCP服务器目前按预期运行. 然而,一些使用克勞德應用程式的客户可能没有看到所有可用的Webflow MCP服务器工具. 如果您正在经历这个问题,您可以通过以下步骤刷新工具列表: 1. 转到设置。 2. 选择连接器。 3. 点击Web流量连接器。 4. 点击三点菜单。 5. 选择刷新工具列表。 我们正在继续密切监测局势。 谢谢你的耐心 在我们努力解决这个问题时.
Webflow MCP 服务器正在按预期运行,这一事件现已解决. 如果 Claude 应用程序中还缺少任何工具, 请遵循这些步骤刷新工具列表 : 1. 转到设置。 2. 选择连接器。 3. 点击Web流量连接器。 4. 点击三点菜单。 5. 选择刷新工具列表。 谢谢你的耐心 在我们努力解决这个问题时.
自动翻译自官方事件更新。
在协调世界时7月6日20:22至协调世界时7月8日08:40之间,一些主机站点上少数响应性图像变体在一些请求中还原出403个错误. 这个问题仅限于极少数响应性图像变体,并不影响所有图像或所有托管站点。 如果您的站点受到这个问题的影响, 您可以通过重置您的站点来恢复访问受影响的图像变体 。 我们对该问题造成的任何不便表示诚挚的歉意,并感谢你在我们努力解决这一问题期间的耐心和理解.
自动翻译自官方事件更新。
我们正调查关于一些主机站点加载速度比预期慢的报告, 目前我们正与上游供应商调查一个问题, 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.
这个问题与上游供应商有关。 少数客户在主机站点的加载时间可能继续较慢,或SSL证书提供速度也较慢. 我们的小组正在积极监测局势,并与我们的上游提供者合作。 我们赞赏你的耐心,并将在获得更多信息后立即分享另一个最新情况.
我们的上游供应商实施了一个固定,我们看到主机站点加载时间和SSL证书提供恢复到预期的性能水平。 我们继续密切监测情况.
在协调世界时约00:00至协调世界时04:05之间,一些托管站点的加载时间较慢,由于上游供应商存在问题,SSL证书的提供时间比预期的要长. 我们不再看到 客户的影响与此问题有关。 经过我们上游供应商的确认和我们小组的核实,这一事件现已得到解决。 谢谢你的耐心 在我们的上游供应商努力解决这个问题期间.
自动翻译自官方事件更新。
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
We are continuing to investigate this issue.
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.
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.
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.
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.
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.
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.
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.
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.
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.
We are currently investigating reports that Webflow is unavailable for some customers. Our team is actively working to identify the cause and restore access as quickly as possible. We will share another update as soon as we have more information.
We’ve identified the cause of the issue impacting access to Webflow and are working to apply a fix. Our team is focused on restoring access, and we’ll continue to share updates as progress is made.
A fix has been implemented and Webflow is now accessible again. We are continuing to monitor closely to ensure stability and will share another update if anything changes.
Between 14:19 and 14:43 UTC, some customers experienced issues accessing Webflow. This has now been resolved, and services are operating normally. We appreciate your patience while we worked to restore service.
We’re investigating reports that CSS is not loading as expected for a very small number of sites. This may cause some pages to appear without styling for affected customers. Users with Per Page CSS enabled who published their site between 23:00–23:30 UTC may be affected. Some users have reported that disabling Per Page CSS and republishing their site temporarily restores expected behavior. Our team is actively investigating and working to identify the root cause. We’ll share another update as soon as we have more information.
A small number of hosted sites experienced an issue that affected how styles were published, which may have caused pages to appear without styling. We've identified and fixed this issue and all affected sites should be working as previously expected. We are further investigating to see if any additional action is needed.
We’re currently investigating reports that some customers are seeing a "Refresh required to continue" message when opening the Webflow Canvas, preventing them from editing sites as expected. Our team is actively working to identify the cause of this issue and will share an update as soon as more information becomes available.
We’ve identified the cause of an issue where some customers see a "Refresh required to continue" message when opening the Webflow Canvas, preventing editing as expected. As a temporary mitigation, our team is assisting impacted customers directly while we work toward a full resolution. We are also waiting for underlying systems to fully recover. We’ll continue to share updates as progress is made.
We’re no longer seeing customer impact related to this issue, and functionality has returned to normal. This incident is now resolved. We appreciate your patience while we worked to resolve this issue.
We’re investigating reports of authorization errors when accessing the Webflow Canvas using Client seats. Our team is actively investigating and will share another update as soon as we have another update to share.
We have identified the root cause of this behavior and are actively working to implement a fix as soon as possible.
A fix has been implemented for the issue impacting some customers with a Client seat role who were unable to access Webflow Canvas. We are seeing recovery and are continuing to monitor the situation closely to ensure stability.
We are continuing to monitor for any further issues.
This incident has been resolved.
We’re currently investigating reports that domains are not appearing as expected in the publishing modal for a small number customers. Our team is actively looking into the issue and will share another update as soon as we have more information. In the meantime, reloading your project may result in your domains displaying as expected inside the publishing modal.
We’ve identified the root cause of the issue impacting a small number of customers where custom domains may not appear as expected in the publishing modal. Our team is actively working on implementing a fix. In the meantime, reloading the project may still result in domains displaying as expected. We’ll share another update as soon as more information becomes available.
We’ve identified the root cause of this issue and are making progress toward a fix. Our team is actively working on implementing and validating the solution to ensure custom domains display as expected in the publishing modal. In the meantime, reloading the project may still help domains appear correctly for some customers. We’ll continue to share updates as progress is made.
A fix has been implemented for the issue where custom domains were not appearing as expected in the publishing modal for a small number of customers. We’re no longer seeing customer impact and are continuing to monitor the situation closely. Thank you for your patience while we worked through this.
A small number of customers experienced issues where custom domains were not appearing as expected in the publishing modal between Mar 30, 18:00 UTC and Mar 31, 18:30 UTC. A fix has been implemented, and we’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve this.