You call this a wake-up call, but the alarm’s been sounding for over a year.
Be open and honest: “Some form submissions may have been impacted” that you have on your status.webflow.com is a corporate euphemism. If the form infrastructure failed during that window, those submissions are gone. Webflow has no retry queue, no redundancy, and no fallback unless users duct-tape external tools like Zapier. That’s not enterprise-grade, that’s a liability with a GUI.
There’s still no mention of user compensation, failover protocols, or a proper postmortem. That silence signals Webflow is betting most users won’t demand accountability.
And while you frame this as a matter of communication, the real issue is deeper: no real-time error logs, no access transparency, no sandbox continuity, and no offline mode. If we were mid-CMS import or on deadline liked my team has been working on, we are stranded, locked in and locked out.
Fixes are table stakes. What’s missing is hardened infrastructure and the operational maturity to match the brand’s ambition.
I think one thing that could be returned as way of apology once all this is over, is to return the ability to download our websites so we have the choice to host elsewhere. All my websites have been offline for more than 9 hours.
You know what’s even more frustrating? I reported this issue with the form two days ago, a full 48 hours, and it wasn’t acknowledged as a real problem until today.
We are managing over 50+ clients on webflow and we advocate webflow HARD. So this has been a let down.
I understand that bugs happen. That’s part of working in tech. But what really bothers me is that my reports were ignored for so long, while Webflow continues to act like this has only been an issue for a few hours. It hasn’t. It’s been 48 hours. Not 24. Not just half a day. A full 48.
I really hope they fix these reliability issues going forward. This kind of delay isn’t acceptable when real businesses rely on the platform.
Finally able to log in and access editor - but scared to make changes. Will we lose work?
Upstream DB issues? Sounds risky…
Update - We’re continuing to work on resolving the issues affecting the Dashboard, Webflow application, and form submission functionality. As part of this ongoing work, new user signups remain temporarily disabled.
We’ve been continuing investigation with our upstream database provider to identify potential root causes. As a result, we’ve identified additional paths of investigation.
Another update will be provided in the next hour. Thank you for your continued patience and understanding.
Jul 29, 2025 - 20:28 UTC
I was able to login earlier this morning as well and got one update in. The site continued to let me work on the site until I got notifications that it’s not saved. Hours of work gone.
Same here. I can only agree with the open letter and am extremely frustrated by the lack of real-time (and honest) status updates.
If I would simply know that webflow has a major outage at the moment I can decide to do something else but have been spending pointless hours retrying edits, publishing and trying to fix issues on side that are clearly with webflow.
Y’all, I’m relatively new to Webflow and wondering if I made a mistake investing time and money in it?? I have an important meeting with clients tomorrow morning and have been trying to update two posts for TWO DAYS! Does this happen often? Should I jump ship?
Is there a reason that there has not been an email sent directly to all of your users, Webflow?
It’d be much better to get ahead of this communication if this is going to take much longer to fix.
As a design studio that recommends Webflow in large part due to the reliability/hands off maintenance, I would MUCH prefer my clients receive communication (ideally way earlier but better late than never) directly from Webflow vs panic emailing my studio OR having to email them and break the news their edits/pages aren’t being made today, when I can do absolutely nothing about this.
Looks promising, and actually the fact you don’t have to pay for a workspace and then for websites is so convenient. And the fact you can use the editor for free and then self host the website is top notch.
This is just the start. We’re taking all of this feedback seriously and are committed to doing better - not just in reliability, but in how we communicate and show up when it matters most
Thanks for getting back to us again. I appreciate you acknowledging the situation, but I want to be clear: what we’re looking for isn’t just reassurance or promises that things will change—we need to see actual, concrete improvements.
Right now, the support failures and platform instability are putting us in a really tough spot with our own clients. We’re having to explain to them why their edits aren’t going live, and we have no answers from Webflow ourselves. It’s not a great look for anyone.
If Webflow is serious about turning this around, we need to see real steps taken—like direct communication to all users when there are major issues, faster response times from support, and a clear plan for how these failures will be prevented in the future. “We hear you” only goes so far; what we need now is action.
If you’re open to suggestions, there are many good ones in this thread, but the bottom line is that we need to see meaningful change, not just words.
I couldn’t have said it better. Webflow, it’s time to get back to basics.
Forget the shiny new features for a moment — just make the core experience (building, publishing) rock-solid and reliable.
No fluff. Just function.
If there’s one good thing about this outage, it’s that it brought back the oldies of our community. Never seen so many blue badges in one thread
Let’s hope this is a turning point. Thanks for working hard & fixing the performance issues for now @webflow - I believe in you guys in seeing this as a final warning to reprioritise your roadmap
