Histórico de interrupções do Webflow

1. 25 Eost 2026 da 22:00 UTCinvestigating

   Continuamos a investigar relatórios de 503 erros que afetam alguns sites hospedados, Webflow.com e Servidor MCP. Nossa equipe está investigando ativamente e compartilhará outra atualização assim que tivermos mais informações.

2. 25 Eost 2026 da 22:09 UTCmonitoring

   Estamos vendo os serviços retornarem aos níveis de desempenho esperados e não estamos mais vendo o impacto ativo do cliente relacionado a este problema. A nossa equipa continua a acompanhar de perto a situação.

3. 25 Eost 2026 da 23:57 UTCmonitoring

   Alguns sites hospedados, Webflow.com e MCP Server experimentaram erros 503. Não estamos mais vendo o impacto do cliente relacionado a este problema, e o incidente agora está resolvido. Agradecemos a sua paciência enquanto trabalhávamos para resolver esta questão.

4. 25 Eost 2026 da 23:58 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 01: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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Gouere 2026 da 01:18 UTCinvestigating

   Estamos a investigar relatórios que não estão a ser entregues como esperado. Nossa equipe está ativamente investigando o problema e trabalhando para identificar a causa raiz. Por favor, note que submissões de formulários e notificações de e-mails de formulários continuam sendo recebidas e podem ser revisadas na guia Formulários dentro das configurações do Site. Vamos partilhar outra actualização assim que tivermos mais informações.

2. 28 Gouere 2026 da 01:48 UTCidentified

   Identificámos o problema que afectava os Webhooks de saída. Webhooks configurados pelo cliente estão falhando e não estão sendo entregues como esperado. Nossa equipe de engenharia está trabalhando ativamente para restaurar a entrega do Webhook. Formulários e emails de notificação de formulários estão funcionando normalmente e não são afetados por este problema. Agradecemos a sua paciência e compartilharemos outra atualização assim que mais informações estiverem disponíveis.

3. 28 Gouere 2026 da 02:13 UTCresolved

   Entre 3:00 PM PT e 6:35 PM PT, webhooks de saída configurados pelo cliente não estavam sendo entregues como esperado. Este problema foi resolvido agora, e entrega webhook saída está funcionando normalmente. Quaisquer submissões de formulários recebidas durante este tempo ainda foram processadas com sucesso e permanecem disponíveis na aba Formulários dentro das configurações do Site.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Gouere 2026 da 05:14 UTCinvestigating

   Estamos investigando relatórios de erros intermitentes que afetam sites hospedados. Embora tenhamos observado anteriormente um período de recuperação, continuamos a ver o impacto do cliente e estamos ativamente investigando o problema. Nossa equipe de engenharia está trabalhando com urgência para identificar a causa raiz e restaurar o desempenho esperado. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

2. 19 Gouere 2026 da 06:10 UTCmonitoring

   Não estamos mais vendo o impacto do cliente relacionado a este problema, e sites hospedados estão atuando como esperado. Nossa equipe tem implementado mitigação e continua acompanhando de perto a situação. Vamos continuar a observar o desempenho do serviço e fornecer outra atualização se houver alguma mudança significativa. Agradecemos a sua paciência enquanto trabalhávamos para investigar este incidente.

3. 19 Gouere 2026 da 14:00 UTCresolved

   Após um período de monitoramento, podemos confirmar que nossa mitigação foi bem sucedida e o desempenho do local retornou aos níveis esperados. Este incidente está agora resolvido. Algumas páginas hospedadas com conteúdo CMS podem ter experimentado erros intermitentes de 5xx durante as seguintes janelas cada uma com duração de alguns minutos (UTC): - 01:27-01:31 - 01:39–01:41 - 01:51–01:53 - 04:47-04:50 - 05:02–05:03 Agradecemos sua paciência enquanto trabalhamos para investigar e resolver o problema.

Traduzido automaticamente da atualização oficial do incidente.

1. 15 Gouere 2026 da 00:21 UTCinvestigating

   Estamos investigando relatórios de que alguns clientes são incapazes de fazer login no Webflow. Nossa equipe está ativamente investigando o problema e trabalhando para identificar a causa raiz. Vamos compartilhar outra atualização assim que tivermos mais informações. Obrigado pela vossa paciência.

2. 15 Gouere 2026 da 00:23 UTCinvestigating

   Continuamos a investigar esta questão.

3. 15 Gouere 2026 da 00:39 UTCmonitoring

   Implementamos uma mitigação e já não vemos o impacto do cliente relacionado a esta questão. Continuamos a acompanhar de perto a situação e forneceremos outra atualização assim que tivermos mais informações. Obrigado pela vossa paciência.

4. 15 Gouere 2026 da 02:46 UTCresolved

   Este incidente está agora resolvido. Alguns clientes tiveram problemas ao entrar no Webflow entre 23:30 UTC em 14 de julho e 00:30 UTC em 15 de julho. Não estamos mais vendo o impacto do cliente relacionado a este problema. Obrigado pela vossa paciência enquanto trabalhávamos para resolver isto.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 21:49 UTCmonitoring

   Estamos reabrindo o incidente anterior, pois a mitigação recomendada apenas aborda temporariamente o problema, e alguns usuários podem ver que as ferramentas Webflow MCP não conseguem carregar em Claude Desktop e claude.ai. O servidor Webflow MCP está operando normalmente e trabalha com todos os outros agentes, incluindo Claude Code. O problema ocorre ao usar Claude Desktop e claude.ai. Quando uma sessão é atualizada em Claude Desktop ou claude.ai, a lista completa de ferramentas nem sempre recarrega. Estamos a trabalhar com o Anthropic para identificar uma solução duradoura. Entretanto, esta solução restaura a lista completa de ferramentas para a sua sessão atual: 1. Vá para Configurações 2. Selecione os conectores 3. Clique no conector Webflow 4. Abra o menu de três pontos 5. Selecione a lista de ferramentas Atualizar Por favor, note que esta é uma solução temporária, não uma solução. A lista de ferramentas permanecerá restaurada apenas para sua sessão atual. Reiniciar ou refrescar o navegador ou aplicativo de desktop pode fazer com que o problema retorne, e você precisará repetir os passos acima. Publicaremos outra atualização assim que tivermos uma. Obrigado pela paciência.

2. 10 Gouere 2026 da 19:31 UTCmonitoring

   Continuamos a trabalhar com o Anthropic para implementar uma solução mais durável. O servidor Webflow MCP está operando normalmente e trabalha com todos os outros agentes. Esta questão impacta Claude desktop, claude.ai e pode impactar Claude Code dependendo da configuração. Como uma solução alternativa, recomendamos usar o Claude Code configurado através da linha de comando. Ele se conecta diretamente ao servidor Webflow MCP ao invés de através de Claude Connectors, então ele não é afetado pelo comportamento atual de atualização de sessão. As instruções de configuração estão disponíveis aqui: https://developers.webflow.com/mcp/installing/claude-code Agradecemos sua paciência e compreensão contínuas, e compartilharemos outra atualização assim que novas informações estiverem disponíveis.

3. 16 Gouere 2026 da 02:17 UTCmonitoring

   Mudanças foram implantadas no Webflow MCP Server que deve restaurar a lista completa de ferramentas no aplicativo Claude Desktop e claude.ai. Todas as ferramentas Webflow MCP devem agora estar disponíveis no conector Claude. Se você ainda não conseguir acessar a lista de ferramentas completa, tente reiniciar Claude desktop ou refrescante claude.ai no navegador. Continuaremos a monitorar a situação enquanto confirmamos que a correção se mantém durante as sessões. Obrigado pela vossa paciência enquanto trabalhávamos nesta questão.

4. 16 Gouere 2026 da 15:22 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

5. 16 Gouere 2026 da 16:16 UTCresolved

   O problema que afeta a disponibilidade de algumas ferramentas Webflow MCP Server no aplicativo Claude Desktop e claude.ai já foi resolvido. Todas as ferramentas Webflow MCP devem agora estar disponíveis no conector Claude. Se você já experimentou ferramentas faltando, reiniciar Claude Desktop ou refrescante claude.ai pode ajudar a garantir que a lista de ferramentas mais recente seja exibida. Não estamos mais vendo o impacto do cliente relacionado a este problema. Obrigado pela sua paciência enquanto trabalhávamos para resolvê-la.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 13:04 UTCinvestigating

   Estamos investigando relatórios de que o seguinte ferramental está faltando no servidor Webflow MCP: data cms tool, data pages tool, data scripts tool, data element tool e data variable tool. Entretanto, recomendamos realizar as ações equivalentes manualmente através da Webflow Canvas. Pedimos desculpas por qualquer inconveniente que isso esteja causando, e compartilharemos outra atualização o mais rápido possível.

2. 8 Gouere 2026 da 13:50 UTCinvestigating

   Identificamos que este problema está impactando o aplicativo Claude Desktop, onde algumas ferramentas do Servidor MCP podem estar indisponíveis. Como solução alternativa, os clientes podem continuar usando o servidor Webflow MCP através do Claude CLI enquanto trabalhamos para resolver o problema. Nossa equipe está investigando ativamente e compartilharemos outra atualização assim que tivermos mais informações. Obrigado pela vossa paciência.

3. 8 Gouere 2026 da 15:28 UTCmonitoring

   O servidor Webflow MCP está operando como esperado. No entanto, alguns clientes usando os aplicativos Claude podem não ver todas as ferramentas disponíveis do Webflow MCP Server. Se você está experimentando este problema, você pode atualizar a lista de ferramentas seguindo estes passos: 1. Acesse Configurações. 2. Selecione os conectores. 3. Clique no conector Webflow. 4. Clique no menu de três pontos. 5. Selecione Atualizar lista de ferramentas. Continuamos a acompanhar de perto a situação. Obrigado pela vossa paciência enquanto trabalhávamos nesta questão.

4. 8 Gouere 2026 da 18:34 UTCresolved

   O Webflow MCP Server está operando como esperado, e este incidente agora está resolvido. Se alguma ferramenta ainda estiver faltando nos aplicativos Claude, atualize a lista de ferramentas seguindo estes passos: 1. Acesse Configurações. 2. Selecione os conectores. 3. Clique no conector Webflow. 4. Clique no menu de três pontos. 5. Selecione Atualizar lista de ferramentas. Obrigado pela vossa paciência enquanto trabalhávamos nesta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 09:52 UTCresolved

   Entre 20:22 UTC em 6 de julho e 08:40 UTC em 8 de julho, um pequeno número de variantes de imagem responsiva em alguns sites hospedados retornou 403 erros em alguns pedidos. Este problema foi limitado a um subconjunto muito pequeno de variantes de imagem responsivas e não afetou todas as imagens ou todos os sites hospedados. Se o seu site foi impactado por este problema, você pode restaurar o acesso às variantes de imagem afetadas, republicando o seu site. Pedimos sinceras desculpas por qualquer inconveniente que esta questão causou, e apreciamos sua paciência e compreensão enquanto trabalhamos para resolvê - la.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 02:38 UTCinvestigating

   Estamos investigando relatórios de que alguns sites hospedados estão carregando mais lentamente do que o esperado, e que os certificados SSL estão levando mais tempo do que o esperado para fornecer para alguns clientes. Atualmente estamos investigando um problema com um provedor upstream que pode estar contribuindo para esse comportamento e estão trabalhando para restaurar o desempenho esperado. Agradecemos a sua paciência e compartilharemos outra atualização assim que mais informações estiverem disponíveis.

2. 2 Gouere 2026 da 02:48 UTCidentified

   A questão está relacionada com um provedor a montante. Um pequeno número de clientes pode continuar a experimentar tempos de carregamento mais lentos em sites hospedados ou provisionamento de certificado SSL mais lento. Nossa equipe está monitorando a situação ativamente e trabalhando com nosso provedor a montante. Agradecemos a sua paciência e compartilharemos outra atualização assim que mais informações estiverem disponíveis.

3. 2 Gouere 2026 da 04:12 UTCmonitoring

   Nosso provedor upstream implementou uma correção, e estamos vendo os tempos de carregamento do site hospedado e o fornecimento de certificados SSL retornam aos níveis de desempenho esperados. Continuamos a acompanhar de perto a situação e compartilharemos outra atualização, se necessário.

4. 2 Gouere 2026 da 10:59 UTCresolved

   Entre aproximadamente 00:00 UTC e 04:05 UTC, alguns sites hospedados experimentaram tempos de carregamento mais lentos e certificados SSL levou mais tempo do que o esperado para fornecer devido a um problema com um provedor upstream. Já não vemos o impacto do cliente relacionado com este problema. Após confirmação do nosso fornecedor a montante e verificação por nossa equipe, este incidente está agora resolvido. Obrigado pela sua paciência, enquanto o nosso fornecedor a montante trabalhou para resolver este problema.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 20:01 UTCinvestigating

   We are continuing to investigate this issue.

9. 14 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 01: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 Ebrel 2026 da 02: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 Ebrel 2026 da 03: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 Ebrel 2026 da 04: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 Ebrel 2026 da 05: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 Ebrel 2026 da 06: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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 03: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 Ebrel 2026 da 04: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 Ebrel 2026 da 05: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 Ebrel 2026 da 06: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 Ebrel 2026 da 07: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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 14:14 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1 Ebrel 2026 da 14:51 UTCresolved

   This incident has been resolved.

1. 31 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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.