Webflow outage history

We’re continuing to investigate reports of 503 errors affecting some hosted sites, Webflow.com, and MCP Server. Our team is actively investigating and will share another update as soon as we have more information.

We’re seeing services return to expected performance levels and are no longer seeing active customer impact related to this issue. Our team is continuing to monitor the situation closely.

Some hosted sites, Webflow.com, and MCP Server experienced 503 errors. We’re no longer seeing customer impact related to this issue, and the incident is now resolved. We appreciate your patience while we worked to resolve this issue.

This incident has been resolved.

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.

We're investigating reports that outbound webhooks are not being delivered as expected. Our team is actively investigating the issue and working to identify the root cause. Please note that Form submissions and Form email notifications continue to be received and can be reviewed in the Forms tab within Site settings. We'll share another update as soon as we have more information.

We have identified the issue affecting outgoing Webhooks. Customer-configured Webhooks are currently failing and are not being delivered as expected. Our engineering team is actively working to restore Webhook delivery. Forms and form notification emails are operating normally and are not impacted by this issue. We appreciate your patience and will share another update as soon as more information is available.

Between 3:00 PM PT and 6:35 PM PT, customer-configured outbound webhooks were not being delivered as expected. This issue has now been resolved, and outbound webhook delivery is operating normally. Any form submissions received during this time were still successfully processed and remain available in the Forms tab within Site settings.

We’re investigating reports of intermittent errors affecting hosted sites. While we previously observed a period of recovery, we’re continuing to see customer impact and are actively investigating the issue. Our engineering team is working with urgency to identify the root cause and restore expected performance. We’ll share another update as soon as more information becomes available.

We’re no longer seeing customer impact related to this issue, and hosted sites are performing as expected. Our team has implemented mitigations and is continuing to monitor the situation closely. We’ll continue to observe service performance and provide another update if there are any significant changes. We appreciate your patience while we worked to investigate this incident.

After a period of monitoring, we can confirm our mitigation was successful and site performance has returned to expected levels. This incident is now resolved. Some hosted pages with CMS content may have experienced intermittent 5xx errors during the following windows each lasting a few minutes (UTC): - 01:27–01:31 - 01:39–01:41 - 01:51–01:53 - 04:47–04:50 - 05:02–05:03 We appreciate your patience while we worked to investigate and resolve the issue.

We’re investigating reports that some customers are unable to log in to Webflow. Our team is actively investigating the issue and working to identify the root cause. We’ll share another update as soon as we have more information. Thank you for your patience.

We are continuing to investigate this issue.

We’ve implemented a mitigation and are no longer seeing customer impact related to this issue. We’re continuing to monitor the situation closely and will provide another update as soon as we have more information. Thank you for your patience.

This incident is now resolved. Some customers experienced issues logging in to Webflow between 23:30 UTC on July 14 and 00:30 UTC on July 15. We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve this.

We're reopening the previous incident as the recommended mitigation only temporarily addresses the issue, and some users may see Webflow MCP tools fail to load in Claude Desktop and claude.ai. The Webflow MCP server is operating normally and works with all other agents including Claude Code. The issue occurs when using Claude Desktop and claude.ai. When a session is refreshed in Claude Desktop or claude.ai, the complete tool list does not always reload. We're working with Anthropic to identify a durable fix. In the meantime, this workaround restores the full tool list for your current session: 1. Go to Settings 2. Select Connectors 3. Click the Webflow connector 4. Open the three-dot menu 5. Select Refresh tool list Please note this is a temporary workaround, not a fix. The tool list will stay restored only for your current session. Restarting or refreshing the browser or desktop app can cause the problem to return, and you'll need to repeat the steps above. We'll post another update as soon as we have one. Thanks for your patience.

We are continuing to work with Anthropic to implement a more durable fix. The Webflow MCP server is operating normally and works with all other agents. This issue impacts Claude desktop, claude.ai and may impact Claude Code depending on the configuration. As a workaround, we recommend using Claude Code configured through the command line. It connects directly to the Webflow MCP server rather than through Claude Connectors, so it isn't affected by the current session refresh behavior. Setup instructions are available here: https://developers.webflow.com/mcp/installing/claude-code We appreciate your continued patience and understanding, and will share another update as soon as new information is available.

Changes have been deployed to the Webflow MCP Server that should restore the full tool list in the Claude Desktop app and claude.ai. All Webflow MCP tools should now be available in the Claude connector. If you are still unable to access the complete tool list, please try restarting Claude desktop or refreshing claude.ai in the browser. We will continue to monitor the situation while we confirm the fix holds across sessions. Thank you for your patience while we worked through this issue.

We are continuing to monitor for any further issues.

The issue affecting the availability of some Webflow MCP Server tools in the Claude Desktop app and claude.ai has now been resolved. All Webflow MCP tools should now be available in the Claude connector. If you previously experienced missing tools, restarting Claude Desktop or refreshing claude.ai may help ensure the latest tool list is displayed. We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve it.

We're investigating reports that the following tooling is missing from the Webflow MCP Server: data_cms_tool, data_pages_tool, data_scripts_tool, data_element_tool, and data_variable_tool. In the meantime, we recommend performing the equivalent actions manually via the Webflow Canvas. We apologize for any inconvenience this is causing, and will share another update as soon as possible.

We've identified that this issue is impacting the Claude Desktop app, where some MCP Server tools may be unavailable. As a workaround, customers can continue using the Webflow MCP Server through the Claude CLI while we work to resolve the issue. Our team is actively investigating and we'll share another update as soon as we have more information. Thank you for your patience.

The Webflow MCP Server is currently operating as expected. However, some customers using the Claude apps may not see all available Webflow MCP Server tools. If you're experiencing this issue, you can refresh the tool list by following these steps: 1. Go to Settings. 2. Select Connectors. 3. Click the Webflow connector. 4. Click the three-dot menu. 5. Select Refresh tool list. We are continuing to monitor the situation closely. Thank you for your patience while we worked through this issue.

The Webflow MCP Server is operating as expected, and this incident is now resolved. If any tools are still missing in the Claude apps, refresh the tool list by following these steps: 1. Go to Settings. 2. Select Connectors. 3. Click the Webflow connector. 4. Click the three-dot menu. 5. Select Refresh tool list. Thank you for your patience while we worked through this issue.

Between 20:22 UTC on July 6 and 08:40 UTC on July 8, a small number of responsive image variants on some hosted sites returned 403 errors on some requests. This issue was limited to a very small subset of responsive image variants and did not affect all images or all hosted sites. If your site was impacted by this issue, you can restore access to the affected image variants by republishing your site. We sincerely apologize for any inconvenience that this issue caused, and appreciate your patience and understanding while we worked to resolve it.

We’re investigating reports that some hosted sites are loading more slowly than expected, and that SSL certificates are taking longer than expected to provision for some customers. We’re currently investigating an issue with an upstream provider that may be contributing to this behavior and are working to restore expected performance. We appreciate your patience and will share another update as soon as more information is available.

The issue is related to an upstream provider. A small number of customers may continue to experience slower loading times on hosted sites or slower SSL certificate provisioning. Our team is actively monitoring the situation and working with our upstream provider. We appreciate your patience and will share another update as soon as more information is available.

Our upstream provider has implemented a fix, and we’re seeing hosted site loading times and SSL certificate provisioning return to expected performance levels. We’re continuing to monitor the situation closely and will share another update if needed.

Between approximately 00:00 UTC and 04:05 UTC, some hosted sites experienced slower loading times and SSL certificates took longer than expected to provision due to an issue with an upstream provider. We're no longer seeing customer impact related to this issue. Following confirmation from our upstream provider and verification by our team, this incident is now resolved. Thank you for your patience while our upstream provider worked to resolve this issue.

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.