Error codes everywhere?

Wow. Just tried on my phone, and it worked! I now have to read a tiny font, but it's better than having to go incognito.

Yes, I was advised to "clear my cache" and it made no difference. Had to download the app. Which I hate..."

I might be tempting fate here, but I have had no problems or error messages for a day or two. I assume that MNHQ have managed to fix the problem?

This experience has got me more into Reddit though. It does have some interesting content but I still don't get exactly how it works and how to find stuff. It's vast and sprawling, and it's difficult to find messages again as they don't seem to be in date order.

I do prefer Mumsnet overall. The MN format is a lot more logical imo and easier to use (when it's working!).

This is all without me doing any 'cache clearing'. Glad I didn't now. Can anyone else confirm that it's back to normal for them?

I followed the instructions a screenshot posted the other day which so far has worked for me. The standard route to clearing history/cache etc hadn't.
If you click on the symbol shown in the photo, you can clear cookies and site data for MN from there.

Has mumsnet been back to say how they are addressing this? it is pretty frustrating!

Ditto.

Same problem. Only works in incognito mode. Error 400 message. Clearing cache hasn't helped.

Chrome is completely unusable for me too, I'm also having to use duck duck go - my usual login etc and no error codes at all.

Mumsnet have many issues and have done for months. Their answer is always to sort something out our end. This doesn't work!! I have repeatedly cleared things as this is mumsnet stock answer.

I have had it freezing on me for months and today at least 4 times!!! The only way it works for me is to close the tab and then open a new one. But even then I am often still having it freeze on me.

Mumsnet need to sort things out from their end. None of this happens on other sites and many people have said. But mumsnet will just sort it!

The site is unusable for me on a Chrome browser but absolutely fine on a Duckduckgo one.

Same here, having to repeatedly clear caches. The site is becoming unusable for me.

I have the same, cleared my cache for nothing!

Same issue and its so frustrating 😪 please sort

@LilyMumsnet Any update on this? I am still clearing my cache every couple of pages to be able to look at Mumsnet. It's not really worth it at this point...

I cleared my cache 5 minutes ago and it worked for approximately one minute before I got a bad request error again

More error codes today

Also now getting a 419 page expired error message when trying to log in incognito. Not a good sign!

Is there any update on this @LilyMumsnet. I've had to download the app which is awful. Problem is on my android phone. I might have to give up. There's clearly a problem and clearing the cache is not resolving it.

Many, many clearances today and have had to go incognito. Big issue @MNHQ

Clearing the cache works for me but only temporarily - I've done it a few times today and yesterday!

Exactly what I was going to say. I have the same problem. Obviously if it's suddenly happening to lots of us it MUST be Mumsnet, not a sudden rash of individuals with the same problem!

What I've been getting - on my phone only (not on the app, I don't have the app) I can open Mumsnet the first time, then get a 400 or a 404 when I try to open any page. Then I leave it for a couple of hours and I can open it again the first time and then the 400/404s start up again. I cleared my cache! No difference.

It was slightly different a couple of days ago but this is the pattern it's settled into. Perfectly fine on my laptop, which, again, seems to be the same for everyone who's complaining. So it's got to be Mumsnet, not us, surely?
Argh!

I access mumsnet via The FB link and have had errors since yesterday but have just uninstalled the fb app and reinstalled and it seems to be working properly now.

Same, I"ve cleared my cache about 5 times in the last hour. I can click on one link, but not the next before getting a 400 bad request. Only MN impacted too.

yup I cleared cache again and it's still there.