Good pings gone bad!

[#1]

Hi guys, any support on this would be greatly appreciated so here goes.
On plusnet pro gaming package.
2.5 weeks ago best pings ever on an isp. (New flat)
20-40 for first person shooters and 30-80 for wow.
Then I went over agreed usage and had a day of gimped bb. Restrictions have come off and things just haven't been the same.
Now I'm lucky if I get 80 ping in fps and in wow I get sometimes close to 300 ping.
If I /cmd in ms dos and do ping www.google.com its alwalys in the 80s and 90s.
Plusnet have confirmed wireshark captures indicate traffic is prioritised correctly and no restrictions are on the line.
I have tried everything. Now they are sugesting that turning interleaving off will fix it.
I am convinced it is something at their side but all I get is shrugs.
Any support or tips are most welcome cheers

[#2]

There are some network issues which may be the cause. Check out the Service Status.

[#3]

hiya,
cheers for the advise.  Although I am not 100% sure about what you mean by service status.
I have phoned plusnet quite a few times now and they are trying things but Its been over 2 weeks now.
The really frustrating thing is tryig to work out the why
below are some tracert's of google
******************************************
C:\Users\Jan>tracert www.google.com ; ---------from the below you can see i never get low latency anymore.
Nothing has changed in the flat but where i used to get 20ms i now get 80-150.
Tracing route to www-tmmdi.l.google.com [66.102.9.147]
over a maximum of 30 hops:
  1    21 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2  103 ms    92 ms    93 ms  lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
  3    70 ms    81 ms    76 ms  gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
  4    88 ms    72 ms    71 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5    72 ms    69 ms    71 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    70 ms    77 ms    71 ms  195.66.224.125
  7    76 ms    84 ms    74 ms  64.233.175.27
  8    91 ms    86 ms    88 ms  209.85.250.216
  9    98 ms    85 ms  103 ms  64.233.174.187
10    87 ms    99 ms  100 ms  64.233.174.14
11  107 ms    86 ms    84 ms  lm-in-f147.1e100.net [66.102.9.147]
Trace complete.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Jan>tracert www.google.com
Tracing route to www-tmmdi.l.google.com [66.102.9.147]
over a maximum of 30 hops:
  1    22 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    75 ms    74 ms  109 ms  lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
  3    71 ms    72 ms    98 ms  gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
  4    70 ms    72 ms    74 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  195 ms    83 ms  104 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    80 ms    72 ms    83 ms  195.66.224.125
  7    77 ms    78 ms    74 ms  64.233.175.27
  8    82 ms    88 ms    96 ms  209.85.250.216
  9    85 ms    89 ms    89 ms  64.233.174.187
10    93 ms    98 ms    89 ms  64.233.174.14
11    93 ms    87 ms    83 ms  lm-in-f147.1e100.net [66.102.9.147]
Trace complete.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Jan>tracert www.google.com
Tracing route to www-tmmdi.l.google.com [66.102.9.147]
over a maximum of 30 hops:
  1    22 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    75 ms    74 ms  109 ms  lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
  3    71 ms    72 ms    98 ms  gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
  4    70 ms    72 ms    74 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  195 ms    83 ms  104 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    80 ms    72 ms    83 ms  195.66.224.125
  7    77 ms    78 ms    74 ms  64.233.175.27
  8    82 ms    88 ms    96 ms  209.85.250.216
  9    85 ms    89 ms    89 ms  64.233.174.187
10    93 ms    98 ms    89 ms  64.233.174.14
11    93 ms    87 ms    83 ms  lm-in-f147.1e100.net [66.102.9.147]
Trace complete.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Jan>tracert www.google.com
Tracing route to www-tmmdi.l.google.com [66.102.9.147]
over a maximum of 30 hops:
  1    22 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    75 ms    74 ms  109 ms  lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
  3    71 ms    72 ms    98 ms  gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
  4    70 ms    72 ms    74 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  195 ms    83 ms  104 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    80 ms    72 ms    83 ms  195.66.224.125
  7    77 ms    78 ms    74 ms  64.233.175.27
  8    82 ms    88 ms    96 ms  209.85.250.216
  9    85 ms    89 ms    89 ms  64.233.174.187
10    93 ms    98 ms    89 ms  64.233.174.14
11    93 ms    87 ms    83 ms  lm-in-f147.1e100.net [66.102.9.147]
Trace complete.

[#4]

A warm welcome to the forum by the way clingy

[#5]

service status is to let you know about problems, like this recent one http://usertools.plus.net/status/archive/1258384040.htm

[#6]

whats the status of your exchange here (if your on the 21cn (adsl2+) network this link is of no use as there is no way of finding this info out yet for 21cn)  http://www.nildram.net/support/tools/congestion_checker/
what your error rates like on your line (hec,crc es) if you dont know how to find these stats check here http://www.kitz.co.uk/adsl/frogstats.php
am a little puzzled why its raised from stable 20ms to what appears to be a stable-ish 70ms if it was exchange congestion i would expect it to be more wild than that and you would actualy see 20ms now and then, it also appears to be to high to be interleaving as well esp as you say it was 20ms i would assume interleaving would be about 50ms
have you tested a diffrent router and do you get the same pings to diffrent gateways other than pcl-ag01
if i havent made it clear am only looking to hop2 on the tracerts (pn gateway) as this where the latency is happening some where between your equipment and the pn gateway

[#7]

hi everyone,
thanks so far for all the feedback.
in response to ASBO DOG.

Results for exchange: Aberdeen Denburn
Congestion
Congestion status on this exchange is green GREEN.
Your telephone line is on an un-congested exchange.
Major Service Outages
There are no Major Service Outages on your line at this present time

as for the next question you asked (and link) here are the router stats.
does the below look normal?
Link Information

Uptime: 6 days, 0:01:46
DSL Type: G.992.1 annex A
Bandwidth (Up/Down) [kbps/kbps]: 448 / 5,600
Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00
Output Power (Up/Down) [dBm]: 11.5 / 19.5
Line Attenuation (Up/Down) [dB]: 18.5 / 14.0
SN Margin (Up/Down) [dB]: 25.0 / 15.5
Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 0 / 0
FEC Errors (Up/Down): 0 / 63
CRC Errors (Up/Down): 0 / 0
HEC Errors (Up/Down): 0 / 0

[#8]

yes they look very excellent for 6days uptime.
all thoe having fec errors points to you being on interleaved and not fastpath and the SNR at 15 on the downstream points to  having or had a ropey connection and hence the DLM upped your target noise margin but that shouldnt effect latency, with 14db atten you should maxing that connection out but your noise margin is holding you back
is it possable to test a diffrent router to rule that out as being the problem?
what router are you running? or should i say which model thomson router are you runing as the tracerts give that away with its quirk of reporting a high ping
below my error rates on adsl2 on 50db atten fastpath line, i get between 16-19ms to bbc.co.uk (the upstream errors are bogus by the way)

[#9]

Hi,
I'm just using the free thomson one I received a year ago from PN. I think its called a TG585V7.
I haven't really got a great deal of understanding as to how the sn and upstream/down stream stuff works.
I think I will play test another router just to rule it out though.
Thanks for the help so far, will try another one out this evening and post my results later today.

[#10]

cheers its allways helpful to rule the hardware out as well, and to be honest i dont think the 585v7's are the most reliable router on the market.

[#11]

Hiya asbo dog.
Yeah it was just a free one.
A friend is bringing his one round later to test.
I should ptobably buy a new one anyway cause the user interface on the thomson is fiddly at the best of times.
Any that you would recomend for £50-60?

[#12]

am a netgear gear fanboy. curently use the dg834 v4 as the broadcom chip in them seem to like my long line and i find the web interface settings to be more than enough.
the thomson 585v7 i dont like due to lack of settings ect not had it on longer enought to see how it copes sync wise, also i had a belkin enhanced wireless one and that was pants again on the settings i took that back after a day and swapped it for my 2nd dg834 v4.
currently synced at 20 days solid

[#13]

Hi clingy,
I've checked your line and it's saying interleaving is on at the moment - removing this will certainly drop the ping, though if you notice the connection dropping at all then probably better to keep it on as it does improve stability.
If your line is stable of course then there shouldn't be any problems. Let me know if you want it removing and I'll get the order placed for you.

[#14]

Hi guys,
A friend brought round a bt hub lol so need to try again as it wouldn't connect.
Asbo dog, I will try another router hopefully by Friday at the latest and post my results so if you don't mind having a look at my post on fri that would be great.
Hi orbrey.
I think there is already a pending action to remove it. But if there isn't that would be cool if you could turn it off. Is it likely to cause drop outs? I was wondering if plusnet have put me on a slower package because I went over my usage. But when I phoned support they said there are no restrictions. Its all a bit ofa mystery cause was a good line

[#15]

Hi clingy,
Looks like we've got an order in progress to move you over to 21CN, as per the ticket on your account , so hopefully this should improve things for you.