Ping problems - whats going on? Seriously getting annoyed.

[#1]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Users\Leights>ping -t 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=37ms TTL=120
Reply from 212.58.224.138: bytes=32 time=34ms TTL=120
Reply from 212.58.224.138: bytes=32 time=38ms TTL=120
Reply from 212.58.224.138: bytes=32 time=35ms TTL=120
Reply from 212.58.224.138: bytes=32 time=41ms TTL=120
Reply from 212.58.224.138: bytes=32 time=35ms TTL=120
Reply from 212.58.224.138: bytes=32 time=35ms TTL=120
Reply from 212.58.224.138: bytes=32 time=35ms TTL=120
Reply from 212.58.224.138: bytes=32 time=34ms TTL=120
Reply from 212.58.224.138: bytes=32 time=36ms TTL=120
Reply from 212.58.224.138: bytes=32 time=34ms TTL=120
Reply from 212.58.224.138: bytes=32 time=36ms TTL=120
Reply from 212.58.224.138: bytes=32 time=37ms TTL=120
Ping statistics for 212.58.224.138:
    Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 41ms, Average = 35ms
Control-C
^C
C:\Users\Leights>
Not too bad, but nowhere as low as yours!
I am hoping ping will help.
I am sick to death of not being able to connect to MW2 and then being laggy as hell!

[#2]

I am on the Gaming Pacakage with + ProMax upgrade (increase upload speed/better contention ratio)
With Interleaving off and I live about 100m from the exchange.
Before having Interleaving on though I was getting pings around your level. Have you checked if its on/off yet? As when mine got turned off I didn't get any notice or anything..

[#3]

Thanks for the reply.
I am on PN unlimited, cannot remeber the package name but never any probs until recently!
I have requested interleaving off but I am still waiting for a reply from PN
 
System Up Time 62:07:28
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 19619147 26791300 0 12696 18659 62:05:52
LAN 10M/100M 26279135 19500315 0 18908 14621 62:07:20
WLAN 11M/54M 383970 199167 0 2010 103 62:07:12

ADSL Link Downstream Upstream
Connection Speed 2368 kbps 448 kbps
Line Attenuation 51.0 db 31.0 db
Noise Margin 6.2 db 22.0 db

Whilst you are looking, does ther noise margin look ok?

Cheers

[#4]

Im not entirely sure mate, the Lower the Line attenuation the better.. Yours is sky high! Mines only at 8db.
The higher the noise margin the better.. yours is 1db higher than mine.
Have to wait for one of the gurus to answer them properly sorry.

[#5]

Sorry just noticed your sync rate at 2386kbps.. Thats low. Have you tried rebooting router see if it helps? You've been online for nearly 3 days.

[#6]

 
System Up Time 00:03:37
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 1134 1246 0 3475 8186 00:01:56
LAN 10M/100M 1467 1616 0 5103 2543 00:03:29
WLAN 11M/54M 44 35 0 31 18 00:03:21

ADSL Link Downstream Upstream
Connection Speed 2336 kbps 448 kbps
Line Attenuation 51.0 db 31.0 db
Noise Margin 6.3 db 22.0 db


I have just rebooted and left it 10 mins, still get the same line attenuation 51 db!!
Not sure twhat that means but sounds bad....anyone got any ideas how to improve it!!!!!!

[#7]

Pings are awful for me still....
C:\Users\Matt>ping -t 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=45ms TTL=121
Reply from 212.58.224.138: bytes=32 time=54ms TTL=121
Reply from 212.58.224.138: bytes=32 time=52ms TTL=121
Reply from 212.58.224.138: bytes=32 time=57ms TTL=121
Reply from 212.58.224.138: bytes=32 time=143ms TTL=121
Reply from 212.58.224.138: bytes=32 time=95ms TTL=121
Reply from 212.58.224.138: bytes=32 time=49ms TTL=121
Reply from 212.58.224.138: bytes=32 time=42ms TTL=121
Reply from 212.58.224.138: bytes=32 time=66ms TTL=121
Reply from 212.58.224.138: bytes=32 time=41ms TTL=121
Reply from 212.58.224.138: bytes=32 time=82ms TTL=121
Reply from 212.58.224.138: bytes=32 time=89ms TTL=121
Reply from 212.58.224.138: bytes=32 time=64ms TTL=121
Ping statistics for 212.58.224.138:
   Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 41ms, Maximum = 95ms, Average = 57ms
I'm on plusnet pro and adsl max premium.
Is having stable pings during peak time too much to ask?  

[#8]

You think those are bad? Check this out:
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=362ms TTL=120
Reply from 212.58.224.138: bytes=32 time=212ms TTL=120
Reply from 212.58.224.138: bytes=32 time=200ms TTL=120
Reply from 212.58.224.138: bytes=32 time=267ms TTL=120
Reply from 212.58.224.138: bytes=32 time=302ms TTL=120
Reply from 212.58.224.138: bytes=32 time=244ms TTL=120
Reply from 212.58.224.138: bytes=32 time=249ms TTL=120
Reply from 212.58.224.138: bytes=32 time=304ms TTL=120
Reply from 212.58.224.138: bytes=32 time=302ms TTL=120
Reply from 212.58.224.138: bytes=32 time=484ms TTL=120
Ping statistics for 212.58.224.138:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 200ms, Maximum = 484ms, Average = 292ms
I just did that about 30 seconds ago. I just stopped playing MW2 myself because it was unplayable. I wish this was only at peak time but I see it even after midnight on a Sunday night (early hours of Monday).

[#9]

C:\Users\Ade>ping -t 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=21ms TTL=120
Reply from 212.58.224.138: bytes=32 time=19ms TTL=120
Reply from 212.58.224.138: bytes=32 time=21ms TTL=120
Reply from 212.58.224.138: bytes=32 time=19ms TTL=120
Reply from 212.58.224.138: bytes=32 time=22ms TTL=120
Reply from 212.58.224.138: bytes=32 time=19ms TTL=120
Reply from 212.58.224.138: bytes=32 time=30ms TTL=120
Reply from 212.58.224.138: bytes=32 time=23ms TTL=120
Reply from 212.58.224.138: bytes=32 time=20ms TTL=120
Reply from 212.58.224.138: bytes=32 time=23ms TTL=120
Reply from 212.58.224.138: bytes=32 time=37ms TTL=120
Ping statistics for 212.58.224.138:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 37ms, Average = 23ms
Control-C
^C
C:\Users\Ade>
Mine is fine mate, what gateway you on?

[#10]

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
  1    3 ms    1 ms    1 ms  www.routerlogin.com [192.168.0.1]
  2    21 ms    19 ms    20 ms  lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
  3    22 ms    19 ms    20 ms  gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
  4    20 ms    19 ms    19 ms  te2-1.pcl-gw02.plus.net [212.159.1.114]
  5    19 ms    19 ms    20 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  6    23 ms    22 ms    19 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7    21 ms    22 ms    31 ms  212.58.238.133
  8    19 ms    20 ms    20 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Trace complete.

[#11]

I rebooted the router since my post earlier, but this is what I get now:
traceroute to bbc.co.uk (212.58.224.138), 64 hops max, 40 byte packets
1  router (192.168.1.1)  1.242 ms  1.189 ms  0.978 ms
2  lo0-plusnet.pcl-ag01.plus.net (195.166.128.27)  15.040 ms  17.138 ms  13.919 ms
3  gi1-2-803.pcl-gw1.plus.net (84.92.5.57)  16.951 ms  14.695 ms  14.888 ms
4  te2-1.pcl-gw02.plus.net (212.159.1.114)  209.280 ms  174.660 ms  200.785 ms
5  te2-2.thn-gw2.plus.net (212.159.0.190)  14.824 ms  14.349 ms  15.040 ms
6  rt0.thdo.bbc.co.uk (212.58.239.25)  14.619 ms  14.324 ms  13.944 ms
7  212.58.238.133 (212.58.238.133)  17.677 ms  14.133 ms  16.025 ms
Nice.  

[#12]

Everyone reporting ping problems, still now, you should check your own router because I had the same problem, I had a topic of my own like 10 pages long.. me whining at plusnet and bt, they did everything they could.. still no fix, until one day I pinged my own router and saw the problem the high latency was starting from my router!
type this, and dont do it only 4 times because it can easily just be fine for only 4 hops. do it 50 or 100 etc
/ping 192.168.1.254 -n 100
should be like 1ms if your wired, if you see any high, you need a new router!

[#13]

OK.
--- router ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.884/1.378/2.373/0.232 ms
It's not my router.
I was with Orange a few months ago and never had latency inconsistency like this, and none of my equipment has changed. I thought their service was pretty shoddy at the time though, and that was why I left. If I knew then what I knew now I would've stayed put (and been grateful!).
How much longer can this possibly go on for? It's a waste of time even trying to play an FPS game online competitively. I can't believe my gaming habits are being decided for me by my ISP. 

[#14]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Neil Rescorla>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=221ms TTL=119
Reply from 212.58.224.138: bytes=32 time=181ms TTL=119
Reply from 212.58.224.138: bytes=32 time=202ms TTL=119
Reply from 212.58.224.138: bytes=32 time=208ms TTL=119
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 181ms, Maximum = 221ms, Average = 203ms

I hope not to confuse anyone but this is my ping times at the current time with VIRGIN MEDIA I'm scheduled for switchover to plusnet this week sometime and cant wait. Modern Warfare is unplayable during peak times as you can see! And after seeing some other people complaining about PN pings they are nothing compared to virgins rubbish, even now with one of the PN servers are down!

[#15]

Hi, i made the original post.
The ping problems have come back again.  Peak times are unplayable for me, really annoyed. 
What can i do?