Update: The more I think about this, the more mad I get. We depend on our websites and this is just unacceptable. I have about 7 clients that I switched to WF, if any of their sites go down, it’s not WF getting the heat, it’s me.
The entire morning my site was publishing fine, to staging. Then about an hour ago, it just timed out, bad gateway, something about a Cloudflare timeout. So I updated my DNS setting, that needed to be updated by Nov. 3rd, so it shouldn’t be causing an issue now.
Now when I hit publish it does nothing at all, it’s just spins in WF publishing.
Is it me or does this platform have a lot of issues compared to years ago?
October 20, an issue with an upstream provider caused disruption to Webflow functionality. Some users were unable to publish sites, access the Dashboard or perform actions within Webflow such as restoring backups or exporting code. From 09:40 UTC, we began to see significant recovery and customers should be able to access and use Webflow again as expected. We’ll continue to monitor the situation.
Super frustrating all around.
This might give more context, I’m not sure how widely reported this outage is in the media unless you know about it. Chaos!
Thank you, Mark. I appreciate you taking the time to keep me in the loop. It is very frustrating. I have a lot that needs to be finished today, and this is not helping at all.
I went back through my logs, and it looks like WF has been having some sort of issue every month since July. I really hope that they get back to being as powerful, while being dependable, like they used to be. It’s not good to have a powerful tool if you can’t depend on it.
And I totally appreciate the pain of having to call your own customers to explain… they usually don’t care about all the AWS stuff. Hopefully in this case, it might at least alleviate some of your pain if you can share the links.
I really hope that they get back to being as powerful, while being dependable, like they used to be.
I agree. I promise that the internal efforts are not small.