Split from: Broadband Speed Issues - 03/10/09

[#1]

Ah nice 
To the point my connection should be fine now, or are there still some errors or what? I guess it will ofcourse take time to get a real verdict, whether or not I encouter any lag spikes or not. But what do you reckon

[#2]

No errors.  Interleaving looks like it's done its job.

[#3]

Alright :<
Its a good thing I know, I am happy. Does this mean Interleaving needs to remain enabled on my line then, and I will never be able to have it switched off again? Only reason I care is because when I play on some EU servers, not in UK, especially public ones anyway. Alot of them tend to have maximum ping caps on them, and in the past when I had interleaving enabled my ping was exceeding these caps and I was getting automatically kicked.
Obviously for UK servers I would prefer to have a higher ping, if it meant not having those dreadful lag spikes

[#4]

I think that the lack of interleaving was actually making your ping times worse, not better.
It should stay on.

[#5]

Ok then, it shall stay on.
Thanks for everything then James, suppose I will play the waiting game now and see how it performs etc.

[#6]

James
Unfortunately for me.. turning interleaving on has seemed to made things worse.
Just playing a game then, my ping was shooting rocket high all of a sudden. I had to tell the other people I was playing with that I will BRB, I closed the game and performed a speedtest, noticing my speed had dropped again.
I restarted the router, reconnecting, and did the speedtest again. It was back at 5meg again which is good. I figured it was fine, so I went back into the game and my ping was back low and normal so I continued.
It didnt take any longer than 5 minutes for the ping to shoot back up, I performed another speedtest and again it has dropped.
Just performed some more /pings and /tracerts to BBC, 1 minute ago and this is the results:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Administrator>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=83ms TTL=121
Reply from 212.58.224.138: bytes=32 time=81ms TTL=121
Reply from 212.58.224.138: bytes=32 time=52ms TTL=121
Reply from 212.58.224.138: bytes=32 time=321ms TTL=121
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 321ms, Average = 134ms
C:\Users\Administrator>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=487ms TTL=121
Reply from 212.58.224.138: bytes=32 time=373ms TTL=121
Reply from 212.58.224.138: bytes=32 time=218ms TTL=121
Reply from 212.58.224.138: bytes=32 time=172ms TTL=121
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 172ms, Maximum = 487ms, Average = 312ms
C:\Users\Administrator>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=265ms TTL=121
Reply from 212.58.224.138: bytes=32 time=113ms TTL=121
Reply from 212.58.224.138: bytes=32 time=54ms TTL=121
Reply from 212.58.224.138: bytes=32 time=50ms TTL=121
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 265ms, Average = 120ms
C:\Users\Administrator>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  home [192.168.1.254]
  2  109 ms    78 ms    51 ms  lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
  3    59 ms    59 ms  381 ms  ge0-0-0-403.pte-gw2.plus.net [84.92.4.2]
  4    80 ms    64 ms    66 ms  vl23.thn-gw2.plus.net [212.159.4.20]
  5    53 ms  409 ms    56 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  6    57 ms    52 ms    76 ms  212.58.238.149
  7    49 ms    54 ms  374 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Trace complete.
C:\Users\Administrator>

Bleh Gutted mode now
I'll update the ticket also to let him know

[#7]

Can you please reboot your router and try again?

[#8]

ok

[#9]

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Administrator>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=60ms TTL=121
Reply from 212.58.224.138: bytes=32 time=48ms TTL=121
Reply from 212.58.224.138: bytes=32 time=293ms TTL=121
Reply from 212.58.224.138: bytes=32 time=162ms TTL=121
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 293ms, Average = 140ms
C:\Users\Administrator>

Same

[#10]

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Administrator>ping plus.net
Pinging plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=62ms TTL=249
Reply from 212.159.9.2: bytes=32 time=54ms TTL=249
Reply from 212.159.9.2: bytes=32 time=53ms TTL=249
Reply from 212.159.9.2: bytes=32 time=370ms TTL=249
Ping statistics for 212.159.9.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 370ms, Average = 134ms
C:\Users\Administrator>ping plus.net
Pinging plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=363ms TTL=249
Reply from 212.159.9.2: bytes=32 time=276ms TTL=249
Reply from 212.159.9.2: bytes=32 time=130ms TTL=249
Reply from 212.159.9.2: bytes=32 time=81ms TTL=249
Ping statistics for 212.159.9.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 81ms, Maximum = 363ms, Average = 212ms
C:\Users\Administrator>ping plus.net
Pinging plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=53ms TTL=249
Reply from 212.159.9.2: bytes=32 time=401ms TTL=249
Reply from 212.159.9.2: bytes=32 time=238ms TTL=249
Reply from 212.159.9.2: bytes=32 time=92ms TTL=249
Ping statistics for 212.159.9.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 401ms, Average = 196ms
C:\Users\Administrator>

[#11]

It's started already
Today, Microsoft are doing their biggest ever update.  There's 13 (I think) patches that have been released all at the same time for practically everyone with a Windows based operating system.  It's going to put a massive burden on our network and I'm afraid that tonight isn't going to be the best time to test things.
Bob's posting a service status announcement later on this afternoon.

[#12]

Will that deffinately be the reason for my connection going nuts though? Or could this just be the same old problem repeating itself

[#13]

Well anyway I can understand if my connection speed went slower with these updates but surely it should still be stable. I cant understand why these updates would cause my connection to go mental and give me insane lag spikes all the time in games, and even on those ping response times to BBC's website and your own, my computer is certainly not downloading any of them yet either (Infact it cant even find any updates atm)

[#14]

icmp pings should stay stable with the tuesday update as there classed as titnanium and the updates should not have a effect on them.
looking at the packet drop graphs up till this point there looking better than this time yestarday

[#15]

Quote from: Jameseh

It's started already Today, Microsoft are doing their biggest ever update.  There's 13 (I think) patches that have been released all at the same time for practically everyone with a Windows based operating system.  It's going to put a massive burden on our network and I'm afraid that tonight isn't going to be the best time to test things. Bob's posting a service status announcement later on this afternoon.

If that was affecting things surely we should be seeing increased drops on the lower priority traffic on the performance graphs - there's nothing I can see yet. This is the LIVE graph:
Broadband Traffic packets dropped (last 1hr)

I've just done a check for updates (on XP) and it's not picking any up yet.