Firstly, I want to say that I love Webflow. On balance, it’s provided a reliable platform that’s helped us build a solid agency business over the past 7 years.
I also think the direction and pace of development over the past 9 months, especially around long-requested features, has been really encouraging.
That said, the recent outages raise serious concerns. Whichever way you slice it, this kind of extended downtime suggests a lack of adequate failovers or redundancy infrastructure. For businesses like mine that rely on Webflow daily, the cost of this kind of disruption is significant. At this level, it’s simply not acceptable.
What makes it worse is the lack of timely, transparent communication. Updates (especially on the status page) often downplay the severity of the issues, leaving users in the dark during critical moments.
Two areas I believe Webflow needs to urgently address:
Clearer, faster, and more transparent communication during outages, especially via the status page and support channels.
Robust redundancy systems to ensure that major platform failures don’t completely disable core services for extended periods.
We want to continue building on Webflow, but reliability and communication need to match the ambitions of the platform.
I couldn’t say it better.
It’s crazy, after days of horrible service right now i can’t get in the dashboard and trying to login for support results in error 504.
Now tell me how in the hell I am supposed to let them know I’ve basically lost a work day and nothing is working.
Crazy pretending to charge every damn perk but not giving an adeguate way of contacting support.
Also, they should ditch the AI crap and focus on letting us work flawlessly. It looks the same model as Adobe, forgetting the pros to make the next toy to sell to the wide audience.
I’m leaving the office now — no point in hitting F5 on the keybord any longer. I really hope the good people at Webflow come up with a fix by tomorrow morning, or I’ll have some very hard explaining to do on Friday.
Fully agreed! When it says partial outage and ‘some’ users, but everyone I work with has the same issue in multiple countries, better communication can help to manage expetations. They seem to been downplaying the matter…
I finally accessed my dashboard, and all my 10 sites are missing. Thankfully, these aren’t all client sites except one; they were projects I built for my course certification. It seems that they are all gone. Please refer to the screenshot.
Hello @Veronica-Webflow how am I suppose to alert support if i get error 504 even trying to login for support?
Also, i love the platform but you know we work with clients, which give us deadlines that usually cost us money if not respected. How do we seek compensation for this terrible, terrible experience?
Because it’s not just the subscription cost, we are professionals, we don’t use Webflow to play around with AI.
We need a CLEAR roadmap on how and when we will be able to work again. We know you are working on it, so that’s not a plausible answer.
Please, give us a date, we cant conduct business like this.
Hopefully not. Happens to me too, but when i reload and it doesnt show error 504, sometimes i can see my websites. Can’t acces them or work on them, though.
@Mark_Web_Dev Shouldn’t be too concerned. This has been “normal” for a long time now. Usually you just have to reload the Designer 1-2 times, but as the situation is now, reloading will probably not work. We just have to wait.
I’ve passed along this feedback to our team so we can provide more clarity on our status page as we continue to investigate. Thank you for flagging this
8+ hours down in the UK. This is a major outage and should have been restored hours ago.
Users who could not work today should be compensated for being unable to do their tasks!
Like others have said, fix the platform before new features no one asked for.
Ditch the AI. Why is everyone rushing to have AI in their app.
Just allow us to design and code. Or have a toggle to allow the user to turn on AI or not.
It’s being shoved down our throats.
But yes Webslow by all means remove Logic, remove user accounts but continue to allow e-commerce sites that are half baked, allow AI so users can generate a section rather than designing it….
Webflow please listen to us- we use your products, we find the ways to extend it beyond its limitations, yet without us there would be no Webflow. So just remember your humble origins before you start a new round of funding for the next billion dollar idea.
Bottom line is: although the new features are valuable and make our jobs easier, we can run our businesses without them, but we can’t work when the platform is completely crashed.
How can we explain to a client that a simple update that shouldn’t take longer than a minute to be implemented might take a couple days now?
Yesterday was a nightmare, but I managed to get something done, today I not able to login into the platform.
Couldn’t agree more with your initial post and your approach… Not much else to say aside from thanking you for the your clear care for the community AND our businesses.
If @Webflow doesn’t already have a “Head of Stability”, it should be you, @J8kes. If they do, that person needs to take a seriously look at the community because this has gone on too long.
Dear webflow-team, please take a close look on the deeper topics addressed here. This thread here goes beyond the performance issues of the designer in every day use. It’s a sequence of misjudged prioritisation in the past years. It’s a change in webflow’s core values that so many of us see going in the wrong direction. Transparency, Freedom, Collaboration, Community - please start listening again to the feedback of the people who made webflow grow in the first place and not your big enterprise clients..
How much more down time can we expect. This is so frustrating! Webflow- your reputation has taken a serious hit in my books!
This is actually unacceptable- what are you doing!?
I asked Claude to decode the current status update to see if there’s something actually valuable hidden in the PR speak, but alas, Claude’s analysis comes to the same conclusion as I did:
Looking at this Webflow status page, the latest update (from today at 17:08 UTC) is basically corporate speak for “we’re still working on it but don’t really know what’s wrong yet.”
Here’s what they’re actually saying:
The real situation: Webflow has been having major issues for almost 2 days straight (since July 28th) with their Dashboard, main app, and form submissions being broken or slow for users.
What “ongoing adjustments to our infrastructure” probably means: They’re frantically trying different fixes, restarting servers, and throwing more resources at the problem because they still haven’t found the root cause.
“Analyzing system patterns and optimizing backend processes where resource contention is highest” translates to: “We think too many people are trying to use our stuff at once and our servers can’t handle it, so we’re trying to figure out which parts are choking.”
“Implementing protective measures to safeguard platform integrity” likely means: “We’re putting up guardrails so the whole thing doesn’t completely crash while we figure this out.”
The fact that they keep saying they’re “investigating” and “working to identify the root cause” after nearly 48 hours suggests this is a pretty gnarly technical problem that they’re struggling to pin down. It’s not just a simple server restart situation.
TLDR: They’re still broken, still don’t know exactly why, and are basically buying time while they frantically debug in production.
Add me to the disappointment train - I agree with everything you’ve listed. I was deep in flow a few hours ago working on a client site that’s due tomorrow, and I’m not sure if my 3+ hour streak has saved entirely or if I’m going to be able to deliver on time tomorrow.
It’s a shame because I love Webflow, but I’ve already started weighing up my options with Webstudio . Can’t have all your eggs in one basket, it seems…
Thanks for sharing this, Jake, and to everyone who’s weighed in here.
We’ve heard this feedback across the community, and we know how frustrating it’s been. The recent availability and uptime issues have caused real disruption, and it’s not the experience we want anyone building on Webflow to have.
Our team is actively working on both short- and long-term fixes, and we’ll be sharing updates shortly on what we’re doing and how we’re moving forward. In the meantime, you can follow ongoing updates at status.webflow.com.
I know words aren’t enough here. We’re focused on resolving these issues fully and delivering the experience you deserve.
This sucks, in my opinion, Webflow’s main problem come from incorporating Analyze and Optimize, like why do they have to be native on all plans as an add on? Why can’t it work as a separate tool, like Google analytics. Webflow is trying to become a data company rather than what it originally was, a web building platform. And now they are paying the price for it, I should say, we are paying the price for it.
. Can’t have all your eggs in one basket, it seems…