Historial de interrupciones de Webflow

1. 25 de agosto de 2026 a las 22:00 UTCinvestigating

   Continuamos investigando informes de 503 errores que afectan a algunos sitios anfitriones, Webflow.com y MCP Server. Nuestro equipo está investigando activamente y compartirá otra actualización tan pronto como tengamos más información.

2. 25 de agosto de 2026 a las 22:09 UTCmonitoring

   Estamos viendo que los servicios vuelven a los niveles de rendimiento esperados y ya no están viendo el impacto activo del cliente relacionado con este problema. Nuestro equipo sigue vigilando de cerca la situación.

3. 25 de agosto de 2026 a las 23:57 UTCmonitoring

   Algunos sitios anfitriones, Webflow.com y MCP Server experimentaron errores de 503. Ya no estamos viendo el impacto del cliente relacionado con este problema, y el incidente está resuelto. Apreciamos su paciencia mientras trabajamos para resolver este problema.

4. 25 de agosto de 2026 a las 23:58 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de agosto de 2026 a las 16:36 UTCinvestigating

   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. 12 de agosto de 2026 a las 19:04 UTCinvestigating

   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. 12 de agosto de 2026 a las 20:24 UTCidentified

   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. 12 de agosto de 2026 a las 22:05 UTCmonitoring

   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. 13 de agosto de 2026 a las 1:18 UTCresolved

   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. 5 de agosto de 2026 a las 15:27 UTCinvestigating

   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. 5 de agosto de 2026 a las 15:45 UTCmonitoring

   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. 5 de agosto de 2026 a las 15:59 UTCresolved

   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. 28 de julio de 2026 a las 1:18 UTCinvestigating

   Estamos investigando los informes de que no se están entregando como se espera. Nuestro equipo está investigando activamente la cuestión y trabajando para identificar la causa raíz. Tenga en cuenta que las presentaciones de formularios y las notificaciones de formulario de correo electrónico siguen siendo recibidas y pueden ser revisadas en la pestaña Formularios dentro de la configuración del sitio. Compartiremos otra actualización tan pronto como tengamos más información.

2. 28 de julio de 2026 a las 1:48 UTCidentified

   Hemos identificado el problema que afecta a Webhooks salientes. Webhooks configurados por el cliente están fallando y no están siendo entregados como se espera. Nuestro equipo de ingeniería está trabajando activamente para restaurar la entrega de Webhook. Los correos electrónicos de notificación de formularios y formularios funcionan normalmente y no son impactados por este problema. Apreciamos su paciencia y compartiremos otra actualización tan pronto como esté disponible más información.

3. 28 de julio de 2026 a las 2:13 UTCresolved

   Entre las 3:00 PM PT y las 6:35 PM PT, los webhooks configurados por el cliente no estaban siendo entregados como se esperaba. Este problema ya se ha resuelto, y la entrega de webhook fuera de línea está funcionando normalmente. Cualquier solicitud de formulario recibida durante este tiempo se procesaba con éxito y seguía disponible en la pestaña Formularios dentro de la configuración del Sitio.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de julio de 2026 a las 5:14 UTCinvestigating

   Estamos investigando informes de errores intermitentes que afectan a sitios anfitriones. Mientras observamos previamente un período de recuperación, continuamos viendo el impacto del cliente y estamos investigando activamente el problema. Nuestro equipo de ingeniería está trabajando con urgencia para identificar la causa raíz y restaurar el rendimiento esperado. Compartiremos otra actualización tan pronto como se disponga de más información.

2. 19 de julio de 2026 a las 6:10 UTCmonitoring

   Ya no estamos viendo el impacto del cliente relacionado con este problema, y los sitios alojados están realizando como se espera. Nuestro equipo ha aplicado medidas de mitigación y sigue vigilando de cerca la situación. Seguiremos observando el rendimiento del servicio y proporcionaremos otra actualización si hay cambios significativos. Apreciamos su paciencia mientras trabajamos para investigar este incidente.

3. 19 de julio de 2026 a las 14:00 UTCresolved

   Después de un período de monitoreo, podemos confirmar que nuestra mitigación fue exitosa y el rendimiento del sitio ha retornado a niveles esperados. Este incidente ya está resuelto. Algunas páginas anfitrionas con contenido de CMS pueden haber experimentado errores intermitentes de 5xx durante las siguientes ventanas cada unos minutos (UTC): - 01:27–01:31 - 01:39-01:41 - 01:51–01:53 - 04:47-04:50 - 05:02-05:03 Apreciamos su paciencia mientras trabajamos para investigar y resolver el problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 15 de julio de 2026 a las 0:21 UTCinvestigating

   Estamos investigando informes de que algunos clientes no pueden acceder a Webflow. Nuestro equipo está investigando activamente la cuestión y trabajando para identificar la causa raíz. Compartiremos otra actualización tan pronto como tengamos más información. Gracias por su paciencia.

2. 15 de julio de 2026 a las 0:23 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 15 de julio de 2026 a las 0:39 UTCmonitoring

   Hemos implementado una mitigación y ya no estamos viendo el impacto del cliente relacionado con este problema. Continuamos monitoreando la situación de cerca y proporcionaremos otra actualización tan pronto como tengamos más información. Gracias por su paciencia.

4. 15 de julio de 2026 a las 2:46 UTCresolved

   Este incidente ya está resuelto. Algunos clientes experimentaron problemas iniciando sesión en Webflow entre las 23:30 UTC los días 14 y 00:30 UTC el 15 de julio. Ya no estamos viendo el impacto del cliente relacionado con este problema. Gracias por su paciencia mientras trabajamos para resolver esto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 9 de julio de 2026 a las 21:49 UTCmonitoring

   Estamos reabrindo el incidente anterior ya que la mitigación recomendada sólo aborda temporalmente el problema, y algunos usuarios pueden ver que las herramientas de Webflow MCP no se cargan en Claude Desktop y claude.ai. El servidor Webflow MCP funciona normalmente y trabaja con todos los demás agentes incluyendo el Código Claude. El problema ocurre cuando se utiliza Claude Desktop y claude.ai. Cuando una sesión se refresca en Claude Desktop o claude.ai, la lista completa de herramientas no siempre se recarga. Trabajamos con Antrópico para identificar una solución duradera. Mientras tanto, esta solución restaura la lista completa de herramientas para su actual sesión: 1. Ir a Ajustes 2. Select Connectors 3. Haga clic en el conector Webflow 4. Abra el menú de tres puntos 5. Seleccione la lista de herramientas Refresh Tenga en cuenta que esto es una solución temporal, no una solución. La lista de herramientas se mantendrá restaurada sólo para su actual sesión. Reiniciar o refrescar el navegador o la aplicación de escritorio puede causar que el problema vuelva, y necesitará repetir los pasos anteriores. Publicaremos otra actualización tan pronto como tengamos una. Gracias por su paciencia.

2. 10 de julio de 2026 a las 19:31 UTCmonitoring

   Continuamos trabajando con Antrópico para implementar una solución más duradera. El servidor Webflow MCP funciona normalmente y funciona con todos los demás agentes. Este problema afecta a Claude escritorio, claude.ai y puede afectar a Claude Code dependiendo de la configuración. Como solución de trabajo, recomendamos utilizar Claude Code configurado a través de la línea de comandos. Se conecta directamente al servidor Webflow MCP en lugar de a través de Claude Connectors, por lo que no se ve afectado por el comportamiento actual de actualización de sesión. Las instrucciones de configuración están disponibles aquí: https://developers.webflow.com/mcp/installing/claude-code Apreciamos su paciencia y comprensión continuas, y compartiremos otra actualización tan pronto como se disponga de nueva información.

3. 16 de julio de 2026 a las 2:17 UTCmonitoring

   Los cambios se han implementado en el servidor MCP de flujo Web que debe restaurar la lista completa de herramientas en la aplicación Claude Desktop y claude.ai. Todas las herramientas de Webflow MCP ahora deben estar disponibles en el conector Claude. Si todavía no puedes acceder a la lista completa de herramientas, por favor, intenta reiniciar el escritorio de Claude o refrescante claude.ai en el navegador. Seguiremos monitoreando la situación mientras confirmamos las existencias fijadas en las sesiones. Gracias por su paciencia mientras trabajamos a través de este tema.

4. 16 de julio de 2026 a las 15:22 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. 16 de julio de 2026 a las 16:16 UTCresolved

   El problema que afecta a la disponibilidad de algunas herramientas de servidor MCP en la aplicación Claude Desktop y claude.ai se ha resuelto ahora. Todas las herramientas de Webflow MCP ahora deben estar disponibles en el conector Claude. Si usted experimentó anteriormente herramientas desaparecidas, reiniciar Claude Desktop o refrescante claude.ai puede ayudar a asegurar que se muestre la última lista de herramientas. Ya no estamos viendo el impacto del cliente relacionado con este problema. Gracias por su paciencia mientras trabajamos para resolverlo.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 13:04 UTCinvestigating

   Estamos investigando informes de que faltan las siguientes herramientas del servidor MCP de flujo Web: data cms tool, data pages tool, data scripts tool, data element tool y data variable tool. Mientras tanto, recomendamos realizar las acciones equivalentes manualmente a través del Webflow Canvas. Nos disculpamos por cualquier inconveniente que esto está causando, y compartiremos otra actualización lo antes posible.

2. 8 de julio de 2026 a las 13:50 UTCinvestigating

   Hemos identificado que este problema está afectando la aplicación Claude Desktop, donde algunas herramientas MCP Server pueden estar disponibles. Como solución de trabajo, los clientes pueden seguir utilizando el servidor MCP de Webflow a través de Claude CLI mientras trabajamos para resolver el problema. Nuestro equipo está investigando activamente y compartiremos otra actualización tan pronto como tengamos más información. Gracias por su paciencia.

3. 8 de julio de 2026 a las 15:28 UTCmonitoring

   El servidor MCP de flujo Web está funcionando como se espera. Sin embargo, algunos clientes que utilizan las aplicaciones de Claude pueden no ver todas las herramientas disponibles de Webflow MCP Server. Si está experimentando este problema, puede actualizar la lista de herramientas siguiendo estos pasos: 1. Ve a Ajustes. 2. Select Connectors. 3. Haga clic en el conector Webflow. 4. Haga clic en el menú de tres puntos. 5. Seleccione la lista de herramientas Refresh. Seguimos vigilando de cerca la situación. Gracias por su paciencia mientras trabajamos a través de este tema.

4. 8 de julio de 2026 a las 18:34 UTCresolved

   El servidor Webflow MCP está operando como se espera, y este incidente se resuelve ahora. Si todavía faltan herramientas en las aplicaciones de Claude, refresque la lista de herramientas siguiendo estos pasos: 1. Ve a Ajustes. 2. Select Connectors. 3. Haga clic en el conector Webflow. 4. Haga clic en el menú de tres puntos. 5. Seleccione la lista de herramientas Refresh. Gracias por su paciencia mientras trabajamos a través de este tema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 9:52 UTCresolved

   Entre 20:22 UTC los días 6 y 08:40 UTC el 8 de julio, un pequeño número de variantes de imagen sensibles en algunos sitios anfitriones devolvieron 403 errores en algunas solicitudes. Esta cuestión se limitó a un subconjunto muy pequeño de variantes de imagen sensibles y no afectó todas las imágenes o todos los sitios anfitriones. Si su sitio fue impactado por este problema, puede restaurar el acceso a las variantes de imagen afectadas por la remodelación de su sitio. Sinceramente nos disculpamos por cualquier inconveniente que este asunto causó, y apreciamos su paciencia y comprensión mientras trabajamos para resolverlo.

Traducido automáticamente desde la actualización oficial del incidente.

1. 2 de julio de 2026 a las 2:38 UTCinvestigating

   Estamos investigando informes de que algunos sitios anfitriones están cargando más lentamente de lo esperado, y que los certificados SSL están tomando más tiempo de lo esperado para proporcionar a algunos clientes. Actualmente estamos investigando un problema con un proveedor que puede contribuir a este comportamiento y estamos trabajando para restaurar el rendimiento esperado. Apreciamos su paciencia y compartiremos otra actualización tan pronto como esté disponible más información.

2. 2 de julio de 2026 a las 2:48 UTCidentified

   El problema está relacionado con un proveedor de corriente. Un pequeño número de clientes pueden seguir experimentando tiempos de carga más lentos en los sitios anfitriones o un suministro de certificado SSL más lento. Nuestro equipo está monitoreando activamente la situación y trabajando con nuestro proveedor de asistencia. Apreciamos su paciencia y compartiremos otra actualización tan pronto como esté disponible más información.

3. 2 de julio de 2026 a las 4:12 UTCmonitoring

   Nuestro proveedor de corriente ha implementado una solución, y estamos viendo los tiempos de carga del sitio anfitriona y certificado SSL que proporciona el retorno a los niveles de rendimiento esperados. Continuamos monitoreando la situación de cerca y compartiremos otra actualización si es necesario.

4. 2 de julio de 2026 a las 10:59 UTCresolved

   Entre las 00:00 UTC y las 04:05 UTC, algunos sitios hospedados experimentaron tiempos de carga más lentos y los certificados SSL tardaron más de lo previsto debido a un problema con un proveedor de corriente avanzada. Ya no estamos viendo el impacto del cliente relacionado con este problema. Tras la confirmación de nuestro proveedor y verificación de corriente por nuestro equipo, este incidente se resuelve ahora. Gracias por su paciencia mientras nuestro proveedor de asistencia técnica trabajó para resolver este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de junio de 2026 a las 20:44 UTCmonitoring

   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. 11 de junio de 2026 a las 22:20 UTCresolved

   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. 5 de junio de 2026 a las 23:42 UTCresolved

   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. 20 de mayo de 2026 a las 17:29 UTCresolved

   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. 18 de mayo de 2026 a las 12:52 UTCinvestigating

   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. 18 de mayo de 2026 a las 14:00 UTCinvestigating

   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. 18 de mayo de 2026 a las 14:14 UTCidentified

   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. 18 de mayo de 2026 a las 15:51 UTCmonitoring

   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. 18 de mayo de 2026 a las 16:47 UTCresolved

   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. 14 de abril de 2026 a las 14:15 UTCinvestigating

   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. 14 de abril de 2026 a las 14:47 UTCinvestigating

   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. 14 de abril de 2026 a las 15:16 UTCinvestigating

   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. 14 de abril de 2026 a las 16:32 UTCinvestigating

   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. 14 de abril de 2026 a las 16:49 UTCinvestigating

   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. 14 de abril de 2026 a las 18:07 UTCinvestigating

   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. 14 de abril de 2026 a las 19:29 UTCinvestigating

   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. 14 de abril de 2026 a las 20:01 UTCinvestigating

   We are continuing to investigate this issue.

9. 14 de abril de 2026 a las 21:13 UTCinvestigating

   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. 14 de abril de 2026 a las 22:23 UTCidentified

    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. 14 de abril de 2026 a las 23:48 UTCidentified

    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. 15 de abril de 2026 a las 1:19 UTCidentified

    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. 15 de abril de 2026 a las 2:40 UTCidentified

    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. 15 de abril de 2026 a las 3:48 UTCidentified

    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. 15 de abril de 2026 a las 4:08 UTCmonitoring

    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. 15 de abril de 2026 a las 5:23 UTCmonitoring

    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. 15 de abril de 2026 a las 6:08 UTCresolved

    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.

1. 8 de abril de 2026 a las 14:36 UTCinvestigating

   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.

2. 8 de abril de 2026 a las 14:45 UTCidentified

   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.

3. 8 de abril de 2026 a las 14:51 UTCmonitoring

   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.

4. 8 de abril de 2026 a las 15:37 UTCresolved

   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.

1. 8 de abril de 2026 a las 3:10 UTCinvestigating

   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.

2. 8 de abril de 2026 a las 4:58 UTCresolved

   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.

1. 2 de abril de 2026 a las 5:30 UTCinvestigating

   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.

2. 2 de abril de 2026 a las 6:03 UTCmonitoring

   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.

3. 2 de abril de 2026 a las 7:55 UTCresolved

   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.

1. 1 de abril de 2026 a las 13:43 UTCinvestigating

   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.

2. 1 de abril de 2026 a las 13:59 UTCidentified

   We have identified the root cause of this behavior and are actively working to implement a fix as soon as possible.

3. 1 de abril de 2026 a las 14:13 UTCmonitoring

   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.

4. 1 de abril de 2026 a las 14:14 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1 de abril de 2026 a las 14:51 UTCresolved

   This incident has been resolved.

1. 31 de marzo de 2026 a las 15:33 UTCinvestigating

   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.

2. 31 de marzo de 2026 a las 16:55 UTCidentified

   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.

3. 31 de marzo de 2026 a las 18:14 UTCidentified

   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.

4. 31 de marzo de 2026 a las 18:39 UTCmonitoring

   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.

5. 31 de marzo de 2026 a las 19:02 UTCresolved

   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.