Site Errors (Slow pages, slow posting, connection reset, uploads failing)

[#1]

didn't have that issue here.. wonder if it's one dodgy server.

[#2]

Wonder if it is related to the storage that will be worked on, on the 12^th 
http://community.plus.net/forum/index.php/topic,128901.msg1120375.html#msg1120375

[#3]

Shouldn't do, but you never know.
I do wonder if one of the servers isn't well. 

[#4]

It might need the Royal Tweetment

[#5]

Quote from: Kelly

I do wonder if one of the servers isn't well.

You mean after all this moaning you haven't looked  

Quote from: Kelly

This change is actually relating to the storage used by community so shouldn't improve anything on its performance (Unless the problem is that storage all the time and we haven't noticed but I we don't think that!)

That statement certainly seems to be true, as on this brief visit, there only seems to be a marginal improvement at this  particular moment  

[#6]

Probably spoke too soon -
Waitng for community.plus.net .....
...

[#7]

had a few instances today of it hanging on posting a quick reply.

[#8]

No problems for me so far today using both the PC and smartphone.

[#9]

Even with only 150 people on the forum (148 guests) and posting at this time of day, "Waiting for community.plus.net...." is an utter pain in the bum. Even for things like Previewing a post or marking something unread. Oh and even "Waiting for Webstats.plus.net..." has reared it's ugly head briefly  
What's more it's so inconsistent, the next moment it may be perfectly ok
2nd edit: The first was a two character typo and guess what....... "The connection was reset" 

[#10]

I had the same "Connecting to..." issue last night, around 1am.

[#11]

To experiment with finding a workaround, I've set SeaMonkey to use HTTP 1.0 and am using that to browse these forums. The idea being if the problem is due to the forum load balancers / servers not properly handling the kept-alive re-used TCP connections, then setting HTTP 1.0 would avoid that by closing the connection after each request is complete. Of course I don't want to do that for everything since it would be slower, hence using SeaMonkey for the forums and leaving Firefox unchanged for everything else.

[#12]

Quote from: AndyH

I had the same "Connecting to..." issue last night, around 1am.

that was most likely caused by

Quote from: Linn

There is planned maintenance which will affect access to our Community site early hours of July 12th. This is planned for between 12.00am - 8.00am. <snip>

[#13]

Quote from: Anotherone

Quote from: Kelly I do wonder if one of the servers isn't well.   You mean after all this moaning you haven't looked

They've been checked for issues and nothing spotted, but sometime might have been missed.

[#14]

Just had this message (for the first time ever)

An Error Has Occurred!
You already submitted this post! You might have accidently double clicked, or tried to refresh.

[#15]

Perhaps it was the quickest finger 1^st