Webflow driftsforstyrrelser

1. 25. august 2026 kl. 22.00 UTCinvestigating

   Vi fortsætter med at undersøge rapporter om 503 fejl, der påvirker nogle hostede websteder, Webflow.com og MCP Server. Vores team er aktivt at undersøge og vil dele en anden opdatering, så snart vi har mere information.

2. 25. august 2026 kl. 22.09 UTCmonitoring

   Vi ser tjenester vende tilbage til forventede performance niveauer og er ikke længere ser aktiv kunde indvirkning relateret til dette problem. Vores hold fortsætter med at overvåge situationen nøje.

3. 25. august 2026 kl. 23.57 UTCmonitoring

   Nogle hostede websteder, Webflow.com, og MCP Server oplevet 503 fejl. Vi ser ikke længere kundens indvirkning relateret til dette problem, og hændelsen er nu løst. Vi sætter pris på Deres tålmodighed, mens vi arbejdede på at løse dette problem.

4. 25. august 2026 kl. 23.58 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. juli 2026 kl. 01.18 UTCinvestigating

   Vi efterforsker rapporter om, at udgående webkroge ikke leveres som forventet. Vores team undersøger sagen og arbejder på at identificere årsagen. Bemærk venligst, at formularindsendelser og e- mailmeddelelser fortsætter med at blive modtaget og kan gennemgås i fanebladet Formularer i Site-indstillinger. Vi deler en ny opdatering, så snart vi har flere oplysninger.

2. 28. juli 2026 kl. 01.48 UTCidentified

   Vi har identificeret problemet, der påvirker udgående Webkrogs. Customer- konfigureret Webkrogs er i øjeblikket svigtende og bliver ikke leveret som forventet. Vores ingeniør team arbejder aktivt på at genoprette Webhook levering. Formularer og formularer til anmeldelse af e-mails fungerer normalt og påvirkes ikke af dette nummer. Vi sætter pris på din tålmodighed og vil dele en anden opdatering, så snart mere information er tilgængelig.

3. 28. juli 2026 kl. 02.13 UTCresolved

   Mellem kl. 3: 00 PT og kl. 6: 35 PT blev kundekonfigurerede outbound webkroge ikke leveret som forventet. Dette problem er nu løst, og outbound webhook levering fungerer normalt. Eventuelle formularindlæg modtaget i løbet af denne periode blev stadig behandlet med succes og forbliver tilgængelige i fanen Forms i Site indstillinger.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. juli 2026 kl. 05.14 UTCinvestigating

   Vi undersøger rapporter om intermitterende fejl, der påvirker hostede sider. Mens vi tidligere observeret en periode med opsving, vi fortsætter med at se kundernes indvirkning og er aktivt undersøge problemet. Vores ingeniørhold arbejder med hast på at identificere den grundlæggende årsag og genoprette den forventede ydeevne. Vi vil dele en anden opdatering, så snart mere information bliver tilgængelig.

2. 19. juli 2026 kl. 06.10 UTCmonitoring

   Vi ser ikke længere kundens indvirkning relateret til dette problem, og hostede websteder udfører som forventet. Vores team har gennemført lempelser og følger fortsat situationen nøje. Vi vil fortsætte med at observere service ydeevne og give en anden opdatering, hvis der er nogen væsentlige ændringer. Vi sætter pris på din tålmodighed, mens vi arbejdede for at undersøge denne hændelse.

3. 19. juli 2026 kl. 14.00 UTCresolved

   Efter en periode med overvågning, kan vi bekræfte vores afbødning var en succes og site ydeevne er vendt tilbage til forventede niveauer. Denne hændelse er nu løst. Nogle hostede sider med CMS-indhold kan have oplevet periodiske 5xx fejl i de følgende vinduer hver vare et par minutter (UTC): - 01: 27- 01: 31 - 01: 39- 01: 41 - 01: 51- 01: 53 - 04: 47- 04: 50 - 05: 02 - 05: 03 Vi sætter pris på din tålmodighed, mens vi arbejdede på at undersøge og løse problemet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juli 2026 kl. 00.21 UTCinvestigating

   Vi efterforsker rapporter om, at nogle kunder ikke kan logge ind på Webflow. Vores team undersøger sagen og arbejder på at identificere årsagen. Vi deler en ny opdatering, så snart vi har flere oplysninger. Tak for din tålmodighed.

2. 15. juli 2026 kl. 00.23 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 15. juli 2026 kl. 00.39 UTCmonitoring

   Vi har implementeret en afbødning og er ikke længere ser kunde indvirkning relateret til dette spørgsmål. Vi fortsætter med at overvåge situationen nøje og vil give endnu en opdatering, så snart vi har mere information. Tak for din tålmodighed.

4. 15. juli 2026 kl. 02.46 UTCresolved

   Denne hændelse er nu løst. Nogle kunder oplevede problemer logge ind på Webflow mellem 23: 30 UTC den 14. juli og 00: 30 UTC den 15. juli. Vi ser ikke længere kundepåvirkning relateret til dette problem. Tak for Deres tålmodighed, mens vi arbejdede for at løse dette.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 21.49 UTCmonitoring

   Vi genåbner den tidligere hændelse som den anbefalede afbødning kun midlertidigt løse problemet, og nogle brugere kan se Webflow MCP værktøjer undlader at indlæse i Claude Desktop og claude.ai. Webflow MCP serveren fungerer normalt og arbejder med alle andre agenter, herunder Claude Code. Problemet opstår, når du bruger Claude Desktop og claude.ai. Når en session er genopfrisket i Claude Desktop eller claude.ai, den komplette værktøjsliste ikke altid genindlæses. Vi arbejder med Anthropic for at identificere en holdbar løsning. I mellemtiden genopretter dette workout den fulde værktøjsliste til din nuværende session: 1. Gå til Indstillinger 2. Vælg forbindelser 3. Klik på Webflow stik 4. Åbn menuen med tre prikker 5. Vælg Genopfrisk værktøjsliste Bemærk venligst, at dette er en midlertidig arbejdsgang, ikke et fix. Værktøjslisten vil forblive genoprettet kun for din nuværende session. Genstart eller forfriskning af browseren eller desktop app kan forårsage problemet til at vende tilbage, og du bliver nødt til at gentage trinene ovenfor. Vi sender en ny opdatering, så snart vi har en. Tak for din tålmodighed.

2. 10. juli 2026 kl. 19.31 UTCmonitoring

   Vi fortsætter med at arbejde med Anthropic for at gennemføre en mere holdbar fix. Webflow MCP serveren fungerer normalt og arbejder med alle andre agenter. Dette problem påvirker Claude desktop, claude.ai og kan påvirke Claude Code afhængigt af konfigurationen. Som en workout, anbefaler vi at bruge Claude Code konfigureret gennem kommandolinjen. Det forbinder direkte til Webflow MCP server snarere end gennem Claude Connectors, så det er ikke påvirket af den aktuelle session genopfriske adfærd. Opsætning instruktioner er tilgængelige her: https: / / developers.webflow.com / mcp / installation / claude- code Vi sætter pris på din fortsatte tålmodighed og forståelse, og vil dele en anden opdatering, så snart nye oplysninger er tilgængelige.

3. 16. juli 2026 kl. 02.17 UTCmonitoring

   Ændringer er blevet indsat på Webflow MCP Server, der bør gendanne den fulde værktøjsliste i Claude Desktop app og claude.ai. Alle Webflow MCP-værktøjer skal nu være tilgængelige i Claude-stikket. Hvis du stadig ikke kan få adgang til den komplette værktøjsliste, så prøv at genstarte Claude desktop eller forfriskende claude.ai i browseren. Vi vil fortsætte med at overvåge situationen, mens vi bekræfter fixet holder på tværs sessioner. Tak for Deres tålmodighed, mens vi gennemgik dette spørgsmål.

4. 16. juli 2026 kl. 15.22 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 16. juli 2026 kl. 16.16 UTCresolved

   Spørgsmålet, der påvirker tilgængeligheden af nogle Webflow MCP Server værktøjer i Claude Desktop app og claude.ai er nu blevet løst. Alle Webflow MCP-værktøjer skal nu være tilgængelige i Claude-stikket. Hvis du tidligere har oplevet manglende værktøjer, genstart Claude Desktop eller forfriskende claude.ai kan hjælpe med at sikre den nyeste værktøjsliste vises. Vi ser ikke længere kundepåvirkning relateret til dette problem. Tak for Deres tålmodighed, mens vi arbejdede på at løse det.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 13.04 UTCinvestigating

   Vi undersøger rapporter om, at følgende værktøjer mangler fra Webflow MCP Server: data _ cms _ tool, data _ siders _ tool, data _ scripts _ tool, data _ element _ tool, og data _ variable _ tool. I mellemtiden anbefaler vi at udføre tilsvarende handlinger manuelt via Webflow Canvas. Vi undskylder for enhver ulejlighed dette forårsager, og vil dele en anden opdatering så hurtigt som muligt.

2. 8. juli 2026 kl. 13.50 UTCinvestigating

   Vi har identificeret, at dette problem er at påvirke Claude Desktop app, hvor nogle MCP Server værktøjer kan være utilgængelige. Som et workout, kan kunderne fortsætte med at bruge Webflow MCP Server gennem Claude CLI, mens vi arbejder på at løse problemet. Vores team undersøger sagen og vi deler en ny opdatering, så snart vi har mere information. Tak for din tålmodighed.

3. 8. juli 2026 kl. 15.28 UTCmonitoring

   Webflow MCP Server fungerer i øjeblikket som forventet. Men nogle kunder, der bruger Claude apps kan ikke se alle tilgængelige Webflow MCP Server værktøjer. Hvis du oplever dette problem, kan du opdatere værktøjslisten ved at følge disse trin: 1. Gå til Indstillinger. 2. Vælg forbindelser. 3. Klik på Webflow stik. 4. Klik på tre-dot menuen. 5. Vælg Genopfrisk værktøjsliste. Vi følger fortsat situationen nøje. Tak for Deres tålmodighed, mens vi gennemgik dette spørgsmål.

4. 8. juli 2026 kl. 18.34 UTCresolved

   Webflow MCP Server fungerer som forventet, og denne hændelse er nu løst. Hvis nogen værktøjer stadig mangler i Claude apps, genopfriske værktøjslisten ved at følge disse trin: 1. Gå til Indstillinger. 2. Vælg forbindelser. 3. Klik på Webflow stik. 4. Klik på tre-dot menuen. 5. Vælg Genopfrisk værktøjsliste. Tak for Deres tålmodighed, mens vi gennemgik dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 09.52 UTCresolved

   Mellem 20: 22 UTC den 6. juli og 08: 40 UTC den 8. juli, et lille antal lydhøre billedvarianter på nogle hostede sites returnerede 403 fejl på nogle anmodninger. Dette spørgsmål var begrænset til en meget lille delmængde af lydhør billedvarianter og påvirkede ikke alle billeder eller alle hostede sites. Hvis dit websted blev påvirket af dette problem, kan du gendanne adgang til de berørte billedvarianter ved at genpublicere dit websted. Vi undskylder oprigtigt for enhver ulejlighed, som dette spørgsmål forårsagede, og værdsætter din tålmodighed og forståelse, mens vi arbejdede for at løse det.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 02.38 UTCinvestigating

   Vi undersøger rapporter om, at nogle hostede websteder indlæses langsommere end forventet, og at SSL-certifikater tager længere tid end forventet at sørge for nogle kunder. Vi er i øjeblikket ved at undersøge et problem med en opstrømsleverandør, der kan bidrage til denne adfærd og arbejder på at genoprette forventede resultater. Vi sætter pris på din tålmodighed og vil dele en anden opdatering, så snart mere information er tilgængelig.

2. 2. juli 2026 kl. 02.48 UTCidentified

   Spørgsmålet er relateret til en opstrømsleverandør. Et lille antal kunder kan fortsætte med at opleve langsommere belastningstider på hostede steder eller langsommere SSL certifikat levering. Vores team overvåger situationen og samarbejder med vores opstrømsleverandør. Vi sætter pris på din tålmodighed og vil dele en anden opdatering, så snart mere information er tilgængelig.

3. 2. juli 2026 kl. 04.12 UTCmonitoring

   Vores opstrømsleverandør har implementeret en rettelse, og vi ser hostede site loading tider og SSL certifikat levering tilbage til forventede præstationsniveauer. Vi fortsætter med at overvåge situationen nøje og vil dele en anden opdatering, hvis det er nødvendigt.

4. 2. juli 2026 kl. 10.59 UTCresolved

   Mellem ca. 00: 00 UTC og 04: 05 UTC oplevede nogle steder langsommere lastningstider, og SSL-certifikater tog længere tid end forventet at levere på grund af et problem med en opstrømsleverandør. Vi ser ikke længere kundepåvirkning relateret til dette problem. Efter bekræftelse fra vores opstrømsleverandør og bekræftelse fra vores team, er denne hændelse nu løst. Tak for din tålmodighed, mens vores opstrømsleverandør arbejdede på at løse dette problem.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 20.01 UTCinvestigating

   We are continuing to investigate this issue.

9. 14. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 14.14 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 1. april 2026 kl. 14.51 UTCresolved

   This incident has been resolved.

1. 31. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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.