Webflow driftsforstyrrelser

Earlier today, a small number of hosted sites experienced intermittent 500 errors. We identified the cause of the issue and implemented mitigation measures. We’re no longer seeing active customer impact related to this issue, and affected sites have returned to normal operation. Our team is continuing to monitor the situation closely and will provide further updates as needed. Thank you for your patience.

A small number of hosted sites experienced intermittent 500 errors between 20:04 UTC and 20:27 UTC. We identified the cause of the issue and implemented mitigation measures. We’re no longer seeing customer impact related to this issue, and affected sites have returned to normal operation. This incident is now resolved. Thank you for your patience while we worked to address this issue.

An issue was identified that impacted access to Webflow services for some customers between 22:45 and 23:20 UTC. Our Engineering team has since mitigated the issue and restored affected services to expected performance levels. We appreciate your patience while we worked to restore service.

We’re no longer seeing customer impact related to this issue, and access to Webflow services has returned to normal. Some customers experienced issues accessing Webflow between 15:15 UTC and 15:37 UTC. This incident is now resolved. We appreciate your patience while our team worked to restore normal functionality. Affected Components: Dashboard → Operational Webflow Canvas → Operational Webflow.com → Operational

We’re investigating reports that some customers are unable to publish. Our team is actively working to identify the cause and will share another update as soon as we have more information.

We’re continuing to investigate publishing issues impacting some customers. Our engineering team is actively working to identify the root cause and evaluate mitigation steps to restore normal publishing functionality. We’ll provide another update within the next hour or sooner if additional information becomes available.

We’ve identified the cause of the publishing issues impacting some customers. We’re beginning to see recovery in the publishing functionality while mitigation work continues. Our team is actively monitoring progress and will share another update as more information becomes available.

We implemented a fix for the publishing issues impacting some customers and are now seeing publishing functionality operating as expected. Our team is continuing to monitor the platform closely and will provide further updates if needed.

Publishing functionality has remained stable following the mitigation work completed earlier, and we’re no longer seeing customer impact related to this issue. Some customers experienced issues publishing between 12:50 UTC and 16:18 UTC on May 18, 2026. This incident is now resolved. We appreciate your patience while our team worked to restore normal functionality.

We are currently investigating reports of 5xx errors affecting some hosted sites, as well as issues loading the Dashboard. Our team is actively investigating the root cause and working to restore normal service as quickly as possible. We will share another update as soon as possible.

We are continuing to investigate an issue causing 5xx errors on some hosted sites and preventing the Dashboard, Webflow Canvas, and Webflow.com from loading as expected. We are actively working to identify the root cause and restore normal service as quickly as possible. If you are able to access the Dashboard or interact with sites via our public API, we recommend refraining from republishing sites at this time while we work to resolve the issue. We will share another update as soon as more information becomes available.

We are continuing to investigate an issue causing 5xx errors on some hosted sites and preventing the Dashboard, Webflow Canvas, and Webflow.com from loading as expected as a matter of urgency. We have also identified that the public API and form submissions are impacted. We sincerely appreciate your patience and understanding as we work to resolve this incident.

We are continuing to investigate an issue impacting the following services: Hosted Sites, Dashboard, Webflow Canvas, Form submissions, Public API, and Webflow.com. Our team is making progress and remains fully engaged in resolving this issue as quickly as possible. Current efforts include: - Implementing mitigation actions aimed at reducing number of impacted sites - Working closely with our upstream cloud provider to investigate and identify further possible mitigation actions If you are able to access the Dashboard or interact with sites via the API, we recommend refraining from republishing sites at this time while we continue to stabilize our services. We understand the disruption this is causing and truly appreciate your continued patience. We will share another update as soon as more information becomes available.

We have made significant progress in mitigating the issue impacting hosted sites, the Dashboard, Webflow Canvas, Webflow.com, Form submissions and the Public API. As a result, service has now been restored for the majority of customers. Our entire team remains fully engaged and is focused on resolving the issue for all remaining customers. We will continue to share updates as this work progresses. We appreciate your continued patience and understanding as we work toward full resolution.

We have made further progress in mitigating this issue, and at this time only a small number of sites remain impacted. Sites that remain impacted by this issue may experience the following: - CMS items not loading as expected or appearing as missing inside the CMS Data Manager - Issues working on CMS pages and/or pages with Collection Lists in the Webflow Canvas - Hosted site pages failing to load with 5xx errors - Errors when publishing As we continue working toward full resolution with the active and urgent support of our upstream provider, we have temporarily disabled backup creation and corresponding restore actions out of an abundance of caution for all customers. Existing backup versions already created remain stable and unaffected. Our team remains actively focused on resolving the issue for all impacted sites and restoring full functionality. We will continue to share updates as progress is made.We appreciate your continued patience.

We are continuing to work urgently with our upstream storage provider to identify the best path forward to restore full service on the subset of sites that remain impacted by this issue. We recognize the impact this issue is having for the remaining customers impacted and our entire team remains focused on resolving this incident as soon as possible.

We are continuing to investigate this issue.

We are continuing to work with an upstream provider to restore full service for the small number of sites that remain impacted by this issue. At this time, our team is actively monitoring progress and awaiting further updates. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. We recommend refraining from restoring sites while we continue to stabilize services. We will continue to share updates as progress is made.

We have identified the underlying issue and are preparing to implement changes with an upstream provider to help restore service for the small number of sites that remain impacted by this issue. At this time, our team is monitoring progress closely as this work moves forward. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

We are continuing to implement changes in coordination with an upstream provider to restore service for the small number of sites that remain impacted by this issue. Our team remains actively engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

We are continuing to implement changes in coordination with an upstream provider and are making progress toward restoring service for the small number of sites that remain impacted by this issue. Our team remains fully engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

We are continuing to implement changes in coordination with an upstream provider as we work through the remaining steps required to restore service for the small number of sites still impacted by this issue. Our team remains fully engaged and is monitoring progress closely as this work continues. We understand the continued impact this may have and appreciate your patience while we work toward full resolution. For impacted sites, we recommend refraining from restoring or publishing sites while we continue to stabilize services. We will continue to share updates as progress is made.

We’re continuing to work closely with an upstream provider to implement additional changes aimed at resolving this issue. While we’ve seen improvement, a small number of sites may still experience intermittent errors or difficulty accessing Webflow services. Our team remains actively engaged and is monitoring progress as these changes are rolled out. We understand the ongoing impact and appreciate your continued patience while we work toward full resolution. For impacted sites, we still recommend holding off on restoring or publishing until services are fully stabilized. We’ll share another update as soon as more information becomes available.

A fix has been implemented in coordination with an upstream provider, and we’re no longer seeing customer impact related to this issue. If you continue to experience issues, we recommend clearing your browser cache and retrying. We’ll continue to monitor closely to ensure services remain stable. Thank you for your patience while we worked to resolve this.

We’re continuing to monitor the situation following the fix implemented in coordination with an upstream provider. At this time, we’re seeing stable performance and are not observing further customer impact. Our team remains actively engaged and is watching closely to ensure services continue operating as expected. If you continue to experience issues, we recommend retrying your request or clearing your browser cache. We’ll share another update as soon as we have additional information. Thank you again for your patience while we worked through this.

This incident that started at 14:15 UTC on April 14th is now resolved. By 16:21 UTC on April 14th, the issue was mitigated for the overwhelming majority of customers (~96%). For a full timeline, details on root cause and action items, you can refer to the following blog post prepared by our CTO, Allan Leinwand: webflow.com/blog/april-14-webflow-incident-report We know this incident caused serious disruption, and sincerely appreciate your patience while we worked to resolve it.

We are currently investigating reports that Webflow is unavailable for some customers. Our team is actively working to identify the cause and restore access as quickly as possible. We will share another update as soon as we have more information.

We’ve identified the cause of the issue impacting access to Webflow and are working to apply a fix. Our team is focused on restoring access, and we’ll continue to share updates as progress is made.

A fix has been implemented and Webflow is now accessible again. We are continuing to monitor closely to ensure stability and will share another update if anything changes.

Between 14:19 and 14:43 UTC, some customers experienced issues accessing Webflow. This has now been resolved, and services are operating normally. We appreciate your patience while we worked to restore service.

We’re investigating reports that CSS is not loading as expected for a very small number of sites. This may cause some pages to appear without styling for affected customers. Users with Per Page CSS enabled who published their site between 23:00–23:30 UTC may be affected. Some users have reported that disabling Per Page CSS and republishing their site temporarily restores expected behavior. Our team is actively investigating and working to identify the root cause. We’ll share another update as soon as we have more information.

A small number of hosted sites experienced an issue that affected how styles were published, which may have caused pages to appear without styling. We've identified and fixed this issue and all affected sites should be working as previously expected. We are further investigating to see if any additional action is needed.

We’re currently investigating reports that some customers are seeing a "Refresh required to continue" message when opening the Webflow Canvas, preventing them from editing sites as expected. Our team is actively working to identify the cause of this issue and will share an update as soon as more information becomes available.

We’ve identified the cause of an issue where some customers see a "Refresh required to continue" message when opening the Webflow Canvas, preventing editing as expected. As a temporary mitigation, our team is assisting impacted customers directly while we work toward a full resolution. We are also waiting for underlying systems to fully recover. We’ll continue to share updates as progress is made.

We’re no longer seeing customer impact related to this issue, and functionality has returned to normal. This incident is now resolved. We appreciate your patience while we worked to resolve this issue.

We’re investigating reports of authorization errors when accessing the Webflow Canvas using Client seats. Our team is actively investigating and will share another update as soon as we have another update to share.

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

A fix has been implemented for the issue impacting some customers with a Client seat role who were unable to access Webflow Canvas. We are seeing recovery and are continuing to monitor the situation closely to ensure stability.

We are continuing to monitor for any further issues.

This incident has been resolved.

We’re currently investigating reports that domains are not appearing as expected in the publishing modal for a small number customers. Our team is actively looking into the issue and will share another update as soon as we have more information. In the meantime, reloading your project may result in your domains displaying as expected inside the publishing modal.

We’ve identified the root cause of the issue impacting a small number of customers where custom domains may not appear as expected in the publishing modal. Our team is actively working on implementing a fix. In the meantime, reloading the project may still result in domains displaying as expected. We’ll share another update as soon as more information becomes available.

We’ve identified the root cause of this issue and are making progress toward a fix. Our team is actively working on implementing and validating the solution to ensure custom domains display as expected in the publishing modal. In the meantime, reloading the project may still help domains appear correctly for some customers. We’ll continue to share updates as progress is made.

A fix has been implemented for the issue where custom domains were not appearing as expected in the publishing modal for a small number of customers. We’re no longer seeing customer impact and are continuing to monitor the situation closely. Thank you for your patience while we worked through this.

A small number of customers experienced issues where custom domains were not appearing as expected in the publishing modal between Mar 30, 18:00 UTC and Mar 31, 18:30 UTC. A fix has been implemented, and we’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve this.

We’re investigating reports that some customers may see issues when publishing their sites. This can result in inconsistent publishing behavior, where an older version of a site is not always cleared as expected after a new publish. Our team is actively investigating and working with an upstream provider. We’ll share another update as soon as we have more information.

We’re currently awaiting a fix from an upstream provider. For some customers, waiting 10–15 minutes and then trying to publish again may help. We’ll share another update as soon as we have more information.

Some sites experienced inconsistent publishing results. During this time, an older version of a site was not always cleared as expected after a new publish. We’re no longer seeing customer impact related to this issue, and this incident is now resolved. Thank you for your patience while we worked through this.

We’re investigating reports that customers are unable to load the Webflow Canvas. Our team is actively investigating and will share another update as soon as we have more information. We appreciate your patience while we work on this.

We are continuing to investigate this issue.

A fix has been implemented and the Webflow Canvas is loading again for customers. Our team is continuing to monitor the situation closely to ensure everything remains stable. Thank you for your patience while we worked to resolve this issue.

Customers were unable to load Webflow Canvas and the Dashboard between 19:28 and 20:20 UTC. The issue has now been resolved and services are operating normally. Thank you for your patience while we addressed this issue.

We’re currently investigating an issue where form submission notification emails are not being delivered as expected. Form submissions themselves are still being successfully collected and can be accessed in the Forms tab within Site settings. However, customers will not receive email notifications for new submissions at this time. Our Engineering team is actively investigating the issue and working to restore normal email delivery. We’ll share another update as soon as we have more information.

This incident is now resolved. Between 17:55 and 20:35 UTC (10:55 AM–1:35 PM PT), form submission notification emails were not sent as expected. During this time, form submissions were successfully collected and remain available in the Forms tab within Site settings. However, notification emails that were not sent during this window will not be delivered retroactively. A fix was deployed, and email delivery has been fully restored. We are no longer seeing customer impact related to this issue. We appreciate your patience while we worked to resolve this.

We’re investigating reports that some customers are unable to purchase Site or Workspace plans. Our team is actively working to identify the root cause and restore this functionality as quickly as possible. We’ll share another update as soon as we have more information. Thank you for your patience while we look into this.

We’ve identified that the root cause of these errors is due to issues with an upstream provider, and they are working urgently to restore their services as soon as possible. We are in close communication with them as this work continues, and will continue to share updates as more information becomes available. We appreciate your patience and understanding as we work to resolve this issue.

Our upstream provider is continuing to work on a fix for this issue. We remain in close communication with them and will continue to share updates as more information becomes available.

Our upstream provider has implemented a fix and we are now seeing recovery. As a result, all new plan purchases should now work as expected. We are continuing to closely monitor the situation.

Between 07:20 UTC and 12:40 UTC, some customers were unable to complete purchases for new plans due to an issue with one of our upstream providers. They have since identified the root cause and implemented a fix. As a result, new plan purchases are now working as expected again. We sincerely appreciate your patience and understanding as we worked to resolve this issue with the support of our upstream provider, and apologize for any inconvenience caused.

Between 7:25pm and 8:00pm UTC on February 26th, a very small number of hosted sites experienced an increase in unexpected 404 errors when accessing site pages. Upon being alerted to this issue, our team took action to minimize impact and restore full service to the small number of impacted sites a as soon as possible. We apologize for any inconvenience that this issue caused, and appreciate your patience and understanding while we worked to resolve it.

We’ve identified that form notification emails are not being delivered as expected for some customers, due to an issue with an upstream provider. Our team is actively working with the provider to resolve the issue and restore normal notification delivery as soon as possible. Form submissions themselves are not impacted and can still be reviewed via the Forms tab in site settings as expected. We’ll share another update as soon as more information becomes available.

Form notification email functionality is now restored and our upstream provider are now processing these emails as expected. We’re continuing to monitor to ensure full recovery and consistent delivery performance. Form submissions were not impacted during this incident and continued to be accessible via the Forms tab in site settings.

Form notification emails were not delivered as expected between 14:15 and 16:41 UTC due to an issue with an upstream provider. All queued emails from this period have since been successfully processed and delivered. Form submissions themselves were not impacted and remained accessible via the Forms tab in site settings throughout the incident. We’re no longer seeing any impact, and this incident is now resolved. Thank you for your patience while we worked to restore normal delivery.

We’re currently investigating reports that some customers are unable to complete payments with a “Failed to create subscription” error.  Our team is actively investigating the issue and working to identify the root cause and will share another update as soon as we have more information. We appreciate your patience while we work to resolve this.

We have identified that the issue is arising with an upstream provider, and are now seeing recovery. As a result, all new plan purchases should work as expected. We are continuing to closely monitor the situation.

Between 12:30 UTC and 13:45 UTC, some customers were unable to complete plan purchases due to an issue with an upstream provider. Our upstream provider has identified the root cause and confirmed recovery. As a result, new plan purchases are now working as expected. We sincerely appreciate your patience and understanding as we worked to resolve this issue.

We’re investigating reports that form notification emails are not being delivered as expected for some customers. Our team is actively investigating and will share another update as soon as we have more information. In the meantime, form submissions can be reviewed via the forms tab in site settings.

We’ve identified that this behaviour is arising due to an issue with an upstream provider. We’re actively working with them to resolve the issue and restore normal notification delivery as soon as possible. Form submissions themselves are not impacted, and can still be reviewed via the forms tab in site settings as expected.

With the support of our upstream provider, the required actions to resolve the issue have been identified and work is ongoing. We will share another update as soon as a new information is available, and sincerely appreciate your patience and understanding as we work to restore this functionality. In the meantime, Form submissions can be accessed via the Forms tab in Site Settings.

Work to restore full functionality to form submission notification emails is ongoing with the support of our upstream provider. In the meantime, form submissions can still be reviewed via the Forms tab in Site Settings. We sincerely appreciate your patience and understanding and will share another update as soon as new information is available.

Work to restore full functionality to form submission notification emails is still ongoing, and we’re continuing to work closely with our upstream provider to resolve the issue and restore normal notification delivery.In the meantime, form submissions can still be reviewed via the Forms tab in Site Settings. We sincerely appreciate your continued patience and will share another update as soon as more information becomes available.

Work to restore full functionality to form submission notification emails is still ongoing. At this time, we do not expect to share another update until tomorrow (Pacific time) unless we receive new information from our upstream provider. In the meantime, all form submissions continue to be successfully processed by Webflow and remain fully accessible via the Forms tab in Site Settings. Only notification emails are impacted. We recognize how disruptive this issue is for customers who rely on this functionality, and we remain engaged with our upstream provider to resolve the issue and restore normal notification delivery as soon as possible.

Form notification email functionality is now restored and our upstream provider are now processing these emails as expected. While there is no current customer-facing impact, we are continuing to actively monitor the situation to ensure stability and will share another update as soon as possible.

This incident has been resolved. Due to an issue with an upstream provider, Form submission notification emails were not processed as expected between 21:30 February 10th - 21:30 February 11th (UTC). Form submissions received during this time processed as expected, and remain available to review via the Forms tab in Site Settings. We sincerely apologize for any inconvenience this issue caused, and appreciate your understanding as we worked with our upstream provider to resolve this issue.

We’re investigating reports of intermittent 500 errors affecting a small number of hosted sites. Some visitors may see errors when loading pages, while other requests continue to work as expected. Our team is actively working to understand the cause and will share updates as we learn more.

We’re seeing signs of recovery and customer impact has been mitigated. Services are operating as expected at this time, and our team is continuing to monitor the situation closely to ensure stability. We’ll share another update if there are any changes. Thank you for your patience.

This incident has been resolved and services are operating normally. Some sites experienced intermittent errors between 14:32 and 15:01 (UTC). We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to address this.

We are currently investigating reports of issues accessing hosted sites and webflow.com due to an issue with an upstream provider. We are continuing to investigate and will share additional details as soon as they become available.

Our upstream provider has implemented a fix. As a result, we are seeing a return to expected performance levels across our impacted services and are continuing to monitor the situation closely.

Following continued monitoring and confirmation from our upstream provider, we’ve verified that performance across all impacted services has returned to normal. This incident is now resolved. Services were affected between 08:48 and 09:11 UTC. We appreciate your patience and understanding while we worked with our upstream provider to resolve this issue.