My pings are horrible in games

[slightlyhuman]

I've always had cable modem and loved it. Right now where I'm living there is only DSL.

I'm on a 1.5MB/down and 512/up

When I first got this DSL service, my pings were sub 60 and was fine. I haven't been gaming since Febuary but I've been trying The Ship and CS:S and don't see not one server with a ping under 90. It's unbearable to play with over a 100 ping imo and I wonder what's wrong?

I do the speakeasy.net speedtest and here's what I get:

PICTURE HERE

1295(161kb) down
208(26.1KB) up

that's not fantastic in the least but surely it should be enough to ping in the 50s? If not then what transfer rate would I need to achieve to obtain lower pings?

For the record:

As of today, new install of xp pro
SP2
Hardwire into microsoft wireless router(mom is on wireless)

Even when I plug straight into the DSL modem, same thing.


Please help, if you need more info LMK

 

[nweaver]

bandwidthe (speed tests) have very little to do with latency (ping time). Improving one won't get the other. Sounds like you just have crappy DSL to me, I'm sure there are other who will be more helpfull, sorry.

 

[ms526]

What sort of attenuation/ output power does your router or modem report for your line?
It may be that your line is of poor quality.

 

[slightlyhuman]

Originally posted by: ms526
What sort of attenuation/ output power does your router or modem report for your line?
It may be that your line is of poor quality.

care to elaborate? don't really know what you're referring to..

 

[ms526]

Originally posted by: DP

Originally posted by: ms526
What sort of attenuation/ output power does your router or modem report for your line?
It may be that your line is of poor quality.

care to elaborate? don't really know what you're referring to..

In your modem or router settings, there should be a reading somewhere telling you your attenuation on the line. It'll be a number in Decibels. It's basically a measure of the quality of your line. Most routers report this, but there may be some that don't.

 

[Muscles]

Show us a traceroute. Bring up the command line (Start -> Run -> Type "cmd" -> Press enter)

At the command line type: tracert www.yahoo.com

Copy and paste the results here.

 

[Crassus]

MS562,
just for me to get educated - what do you make of the following:

Transceiver Revision: 1.0.9.0
Vendor ID Code: 4
Line Mode: G.DMT Mode
Data Path: Interleaved
Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 864 160
Margin (dB) 14.0 31.0
Line Attenuation (dB) 46.0 31.5
Transmit Power (dBm) 15.8 10.6

Thanks.

 

[ms526]

Originally posted by: Crassus
MS562,
just for me to get educated - what do you make of the following:

Transceiver Revision: 1.0.9.0
Vendor ID Code: 4
Line Mode: G.DMT Mode
Data Path: Interleaved
Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 864 160
Margin (dB) 14.0 31.0
Line Attenuation (dB) 46.0 31.5
Transmit Power (dBm) 15.8 10.6

Thanks.

From that, I gather that you have synched with the DSLAM at a data rate of 864kb/s downstream and 160kb/s upstream speed.

I can also see that you're using interleaved latency - usually enabled when the line is unstable - possibly due to your high level of attenuation at 46db. This could mean that you are either a long distance from the exchange or there is some poor quality cabling along the line somewhere.

 

[Crassus]

Thanks. How would you rate Line Attenuation good/fair/poor in terms of dB?

 

[ms526]

Originally posted by: Crassus
Thanks. How would you rate Line Attenuation good/fair/poor in terms of dB?

Well, the higher the level of attenuation, the poorer the signal is. As a comparison, my DSL has an attenuation rate of 27db, which is about average in my opinion. 46db is quite poor, I've heard that if it's much over 45db then technically you shouldn't qualify for DSL, though I've seen people with a little over 50db of attenuation and their connection still works ok.

 

[slightlyhuman]

tracert screenshot

sorry, don't know how to copy and paste using cmd prompt.


also, i looked everywhere in my router settings(microsoft mn-510) and didn't see the attenuation🙁

 

[spidey07]

Looks pretty normal. You just have latency of 90 ms.

You can try to call your provider, but 90 really isn't too bad for latency.

 

[iamaelephant]

100 ping in unbearable? 😕

 

[spidey07]

Originally posted by: iamaelephant
100 ping in unbearable? 😕

OP has no skills and blames his latency.

🙂

Anyting 110 or under you should own if gotz da skillz YO!

Thing is, aim where they will be. Not where they are.

 

[thescreensavers]

were u live?

 

[Muscles]

Originally posted by: spidey07
Looks pretty normal. You just have latency of 90 ms.

You can try to call your provider, but 90 really isn't too bad for latency.

This statement couldn't be further from the truth. Your traceroute tells me that you have a 90 ping just to your ISP so either you have one of the worst ISP's ever or you've got something going on internally. I don't care if you have DSL, Cable, or FIOS, you should ping around 10ms to your ISP (your first couple of hops). Even way back in the day when I had ISDN I was pinging much lower then 90. In fact, I was a good friend to the main system administrator at my ISP and we hosted Quake servers all the time. I pinged 30ms with ISDN.

My advice is to get a new DSL provider if you can. Heres a copy and paste of my traceroute to use as an example of what you *should* be getting. I have a 15mbps/2mbps connection but the speed of the line is completely irrelevant. All that matters in regards to latency is the quality of the line so your DSL should look similar.

Tracing route to www.yahoo.akadns.net [209.191.93.52]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 8 ms 10.98.32.1
3 12 ms 9 ms 9 ms 653215hfc254.tampabay.res.rr.com [65.32.15.254]

4 9 ms 9 ms 9 ms pos6-0-OC-192.tampflerl-rtr4.tampabay.rr.com [65
.32.8.137]
5 10 ms 13 ms 11 ms pop2-tby-P0-1.atdn.net [66.185.136.185]
6 10 ms 11 ms 11 ms bb2-tby-P0-1.atdn.net [66.185.136.178]
7 23 ms 24 ms 23 ms bb1-atm-P2-0.atdn.net [66.185.152.186]
8 22 ms 21 ms 26 ms pop1-atm-P4-0.atdn.net [66.185.150.1]
9 23 ms 24 ms 24 ms if-8-0.har1.A56-Atlanta.teleglobe.net [64.86.9.1
]
10 22 ms 23 ms 23 ms if-0-1.core1.A56-Atlanta.Teleglobe.net [64.86.8.
5]
11 39 ms 37 ms 38 ms ix-6-0.core1.DTX-Dallas.teleglobe.net [216.6.53.
6]
12 39 ms 39 ms 55 ms ge-0-1-0-p111.msr2.mud.yahoo.com [216.115.104.10
3]
13 39 ms 40 ms 39 ms te-9-1.bas-c2.mud.yahoo.com [68.142.193.11]
14 41 ms 39 ms 39 ms f1.www.vip.mud.yahoo.com [209.191.93.52]

Trace complete.