Webflow Status

Resolved: 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.

Monitoring: 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.

Investigating: 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.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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.

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

Investigating: 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.

Resolved: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Investigating: 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.