Peak time problems

[#1]

So I'm seeing a lot of rubber-banding in my online games and steam games freeze up online and steam will crash too.
I thought it could be my setup but after resetting the router and reinstalling steam + games I still have the same problem. but when I play say past midnight I don't get this problem. I didn't get disconnected once last night gone 12 so why is this only happening in peak hours?

[#2]

"kick for ping above 400ms"
I'm not seeing anything like this in a ping test to bbci or tbb.

[#3]

Come on, its all working fine gone midnight. Whats going on! 

[#4]

Not sure, that seems very odd indeed. You're definitely on the correct profile, not sure if you've done one before but would you be able to do a wireshark capture of this happening so we can look into it for you? Apologies if you've already seen it but if not there's instructions on how to use wireshark here: http://community.plus.net/library/faults/using-wireshark-for-data-capture/

[#5]

I can do that!
What about this weekend!?! If its like this all weekend I'm really not going to be happy. Is there anything you can do to try and prevent this?

[#6]

If we knew what it was we'd be able to do something about it, but unfortunately we don't - that's why we've asked for the wireshark as that'll give us more information about what's going on.
Certainly hope it's not like that all weekend though.

[#7]

Do you know the IP of the server you  was in, ? if so you could also ping it or use a free program that will do this for you as well as save to results , win mtr
http://winmtr.net/

[#8]

Blim:  Your profile speed is current set pretty much at the top we can set it (77000).  How about I lower it by 10Mbps (to 67000) just in case there is something funny going on with profiles to make sure you aren't pushing anything on your line?
Obviously you'll lose some headline speed, but might be worth a test?

[#9]

I'm not sure that's really all that productive. I found this problem to be when less than 2% of my connection's advertised speed was in use.
Last night I was getting latency around 30-70ms to bbci then I changed gateway and things went back to normal. To get a better understanding I don't see this type of latency when I'm upload or downloading full speed at a different time of day (0:00 to 18:00).
How about we go off the information at hand rather than just throwing random ideas in, in hope you might get lucky. I'm a paying customer I hope you know, not some beta tester trying to get free early access.

[#10]

Ah, if only trials were free!

[#11]

I'm suggesting it because we can't see anything wrong with your line at all, or the gateways you are connected. 

[#12]

If you are only seeing the increased latency over the link to the gaming server you join, then it would appear to be isolated to that  so the routing and peering between your router and the router of the host server , or even the hosts internet connection to you can play apart , Best thing is to run win mtr or ping plotter so it is pinging the host server both when the latency is normal and when the latency is high, then we should be able to see where the issue lies , my guess is a peering link is responsible, this is backed up with the swapping of gateways curing it,  as i have noticed  changes in latency and the way some transatlantic peering links are routed differ between some gateways, certainly if Level3 peering

[#13]

I saw the same thing on other PN users TBB ping graphs. If it was the server then others would have the same problem. I couldn't even join a game at one point.
One other person is reporting problems connecting to a GW2 US server, so I thought its might be related as it was steam losing connection.
Edit: It was a UK War of The Roses server, not sure if that uses level3 links?

[#14]

I found this server list which is  a multi-play server list,  http://www.game-monitor.com/GameSearch/waroftheroses2/War_of_the_Roses.html without monitoring the ip of the server that you are having problems with during peak times ,it's impossible to say for sure that this is 100% a plusnet issue,  it may or may not be linked to the hump effect on the tbb graphs,  ping plotter may show this better  it (the pro) version produces a graph  like tbb , just configure it target the ip and ping every second  this will show if the latency rises  or not, or if it has a lot of jitter  or not,  the rubber banding effect is usually down to a sudden change in latency ,such as a spike , you can have a reasonable game if the latency is at a consistent level, even if it is a little on the high side, obviously there are limits as to how high the ping is,

[#15]

Its started happening again but this time at 2am.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Users\blim>ping -t 85.236.101.33
Pinging 85.236.101.33 with 32 bytes of data:
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Reply from 85.236.101.33: bytes=32 time=10ms TTL=121
Ping statistics for 85.236.101.33:
   Packets: Sent = 34, Received = 34, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 10ms, Maximum = 10ms, Average = 10ms
Control-C
^C
C:\Users\blim>tracert 85.236.101.33
Tracing route to blade36-101-33.multiplay.co.uk [85.236.101.33]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2    11 ms    10 ms    10 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
 3    10 ms    10 ms    10 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.17
8]
 4    20 ms     9 ms     9 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
 5    10 ms     9 ms    10 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
 6   131 ms   203 ms    20 ms  195.66.236.224
 7    10 ms    10 ms    10 ms  blade36-101-33.multiplay.co.uk [85.236.101.33]
Trace complete.
C:\Users\blim>tracert 85.236.101.33
Tracing route to blade36-101-33.multiplay.co.uk [85.236.101.33]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2    10 ms    10 ms    10 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
 3    10 ms    10 ms    10 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.17
8]
 4    10 ms     9 ms     9 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
 5    11 ms     9 ms    10 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
 6    10 ms    10 ms    10 ms  195.66.236.224
 7    10 ms    10 ms    10 ms  blade36-101-33.multiplay.co.uk [85.236.101.33]
Trace complete.
C:\Users\blim>tracert 85.236.101.33
Tracing route to blade36-101-33.multiplay.co.uk [85.236.101.33]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2    10 ms    10 ms    10 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
 3    10 ms    10 ms     9 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.17
8]
 4     9 ms     9 ms     9 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
 5    12 ms    10 ms    10 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
 6    10 ms    10 ms    10 ms  195.66.236.224
 7    10 ms    10 ms    10 ms  blade36-101-33.multiplay.co.uk [85.236.101.33]
Trace complete.
C:\Users\blim>

Server list:
http://www.gameserverdirectory.com/search.php?q=&players=Y&game=war-of-the-roses-kingmaker&bots=&cou...