Is Webflow down?

We’re investigating increased publishing times affecting some customers. Some publishes may also get stuck or return an error. Our team is investigating and will share another update as soon as we have more information.

Our team is continuing to investigate increased publishing times affecting some customers. We’re working to understand the cause and are exploring potential mitigations. We’ll share another update as soon as we have more information.

We’ve deployed changes to address the increased publishing times affecting some customers and are no longer seeing active impact. Our team is continuing to monitor the situation closely.

Following continued monitoring, we’ve confirmed that the issue affecting publishing times has been resolved and there is no current customer impact. We appreciate your patience while our team worked to resolve this issue.

We’re investigating reports that form submission notification emails are not being delivered as expected for some customers. Our team is investigating and will share another update as soon as we have more information. In the meantime, Form submissions can still be reviewed via the Forms tab in Site settings, the MCP and Form Submissions API endpoints.

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 delivery of form notification emails as soon as possible. Form submissions themselves are not impacted. In the meantime, Form submissions can still be reviewed via the Forms tab in Site settings, by using the MCP and Form Submissions API. We appreciate your continued patience and will share another update as soon as new information is available.

There is no longer active customer impact, and form submission notification emails are now being delivered as expected. During this incident, notification email delivery was impacted for some customers. Form submissions continued to be received and saved in Site settings as expected, and webhook delivery was unaffected. Our team is continuing to monitor the situation closely. We appreciate your patience while we worked through this issue.

This incident is now resolved. Form submission notification emails were impacted between 00:46 UTC on September 21 and 15:33 UTC on September 22. New form submissions are now triggering notification emails as expected. During this time, form submissions continued to be received and saved as expected, and webhook delivery was unaffected. Notification emails that were not delivered during the affected timeframe will not be delivered retroactively. Affected customers can review submissions from this timeframe via: - the Forms tab in Site settings - the data_forms MCP tool - the Form Submissions API endpoints We appreciate your patience while we worked with our upstream provider to resolve this issue.

We’re investigating reports that some customers are unable to authorize MCP for sites within client Workspaces. Affected sites may appear greyed out and cannot be selected during the authorization process. Our team is actively investigating the issue and will share another update as soon as we have more information. Thank you for your patience.

We have identified the cause of an issue affecting MCP authorization for some sites within Client Workspaces. Our team is actively working to implement a fix.

A fix has been implemented and customers should now be able to authorize MCP for sites within client Workspaces as expected.

This incident has been resolved. Thank you for your patience while we worked on this issue.

We’re investigating reports of 500 errors affecting some hosted sites. Our team is actively investigating and will share another update as soon as we have more information.

We’re continuing to investigate reports of 500 errors affecting some hosted sites. The impact is intermittent, and our team is continuing to investigate as a matter of urgency. We appreciate your patience and understanding, and will share another update within the next hour.

We have identified the cause of the intermittent 500 errors affecting some hosted sites and are actively working to resolve the issue. We appreciate your continued patience and will share another update as soon as new information is available.

We’re no longer seeing customer impact related to this issue but are continuing to monitor the situation closely. We will share another update when new information is available, and sincerely appreciate your patience.

Between approximately 08:29 - 9:40am UTC, some hosted sites experienced intermittent 500 errors over the following short periods: 08:29–08:35 UTC 08:42–08:52 UTC 08:58–09:04 UTC 09:32–09:40 UTC This predominantly impacted sites that were recently published. We’re no longer seeing customer impact related to this issue, and the incident is now resolved. We sincerely appreciate your patience while our team worked through this issue.

We’re investigating reports of publishing attempts failing for some customers. Some customers may also experience issues when making new purchases or upgrading their plans. The issue appears to be related to an upstream provider, and our team is actively investigating. We’ll share another update as soon as we have more information.

An upstream provider has implemented a fix for an issue affecting multiple Webflow services. Some customers may continue to experience issues with services including Publishing, Analyze, and Optimize. We’re continuing to work with our upstream provider and are closely monitoring recovery across affected services. We’ll share another update as soon as we have more information.

Our upstream provider has implemented a fix, and we’re seeing improvements across the affected Webflow services. Our team is continuing to monitor the situation closely and will provide updates when new information is available.

Following continued monitoring, we’ve confirmed that the issue affecting multiple Webflow services has been resolved. This incident is now closed. We appreciate your patience while we worked with our upstream provider to resolve this issue.