What do you consider acceptable ping RTTs?

admin — Thu, 25 Sep 2008 15:28:34 +0000

My new cable connection with Cox really sucks compared to the old ISP I used to have ( ) even though they were rated as the same speed 12/1. When my new connection starts dogging I’ll start seeing times in the 150’s-200’s, and then it will improve, but I almost never see any times less than 60ms, and I used to be able to get 30’s and 40’s.

What is worth getting on the phone and bitching about?
seriously

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:UsersChris>ping stanford.edu

Pinging stanford.edu [171.67.20.37] with 32 bytes of data:
Reply from 171.67.20.37: bytes=32 time=1083ms TTL=53
Reply from 171.67.20.37: bytes=32 time=910ms TTL=53
Reply from 171.67.20.37: bytes=32 time=796ms TTL=53
Reply from 171.67.20.37: bytes=32 time=944ms TTL=53

Ping statistics for 171.67.20.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 796ms, Maximum = 1083ms, Average = 933ms

C:UsersChris>ping google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=1108ms TTL=246
Reply from 72.14.207.99: bytes=32 time=1080ms TTL=246
Reply from 72.14.207.99: bytes=32 time=1131ms TTL=246
Reply from 72.14.207.99: bytes=32 time=637ms TTL=246

Ping statistics for 72.14.207.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 637ms, Maximum = 1131ms, Average = 989ms

C:UsersChris>ping speedtest.grandecom.com

Pinging speedtest.grandecom.net [66.90.138.147] with 32 bytes of data:
Reply from 66.90.138.147: bytes=32 time=624ms TTL=54
Reply from 66.90.138.147: bytes=32 time=581ms TTL=54
Reply from 66.90.138.147: bytes=32 time=525ms TTL=54
Reply from 66.90.138.147: bytes=32 time=511ms TTL=54

Ping statistics for 66.90.138.147:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 511ms, Maximum = 624ms, Average = 560ms

C:UsersChris>ping ou.edu

Pinging ou.edu [129.15.0.230] with 32 bytes of data:
Reply from 129.15.0.230: bytes=32 time=459ms TTL=113
Reply from 129.15.0.230: bytes=32 time=502ms TTL=113
Reply from 129.15.0.230: bytes=32 time=371ms TTL=113
Reply from 129.15.0.230: bytes=32 time=470ms TTL=113

Ping statistics for 129.15.0.230:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 371ms, Maximum = 502ms, Average = 450ms

C:UsersChris>ping 147.26.203.42

Pinging 147.26.203.42 with 32 bytes of data:
Reply from 147.26.203.42: bytes=32 time=604ms TTL=115
Reply from 147.26.203.42: bytes=32 time=456ms TTL=115
Reply from 147.26.203.42: bytes=32 time=513ms TTL=115
Reply from 147.26.203.42: bytes=32 time=575ms TTL=115

Ping statistics for 147.26.203.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 456ms, Maximum = 604ms, Average = 537ms

C:UsersChris>ping techreport.com

Pinging techreport.com [69.65.116.162] with 32 bytes of data:
Reply from 69.65.116.162: bytes=32 time=451ms TTL=51
Reply from 69.65.116.162: bytes=32 time=461ms TTL=51
Reply from 69.65.116.162: bytes=32 time=369ms TTL=51
Reply from 69.65.116.162: bytes=32 time=327ms TTL=51

Ping statistics for 69.65.116.162:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 327ms, Maximum = 461ms, Average = 402ms

C:UsersChris>ping google.com

Pinging google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=111ms TTL=247
Reply from 64.233.167.99: bytes=32 time=88ms TTL=247
Reply from 64.233.167.99: bytes=32 time=400ms TTL=247
Reply from 64.233.167.99: bytes=32 time=271ms TTL=247

Ping statistics for 64.233.167.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 88ms, Maximum = 400ms, Average = 217ms

C:UsersChris>ping cox.com

Pinging cox.com [24.248.75.200] with 32 bytes of data:
Reply from 70.166.160.10: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 70.166.160.10: Destination net unreachable.

Ping statistics for 24.248.75.200:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

C:UsersChris>ping cox.net

Pinging cox.net [68.1.17.9] with 32 bytes of data:
Reply from 68.1.17.9: bytes=32 time=232ms TTL=122
Reply from 68.1.17.9: bytes=32 time=102ms TTL=122
Reply from 68.1.17.9: bytes=32 time=33ms TTL=122
Reply from 68.1.17.9: bytes=32 time=444ms TTL=122

Ping statistics for 68.1.17.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 444ms, Average = 202ms

C:UsersChris>

I have no answer to your acceptability question but find it somewhat humorous (and pretty ridiculous) that out of all that you get 50% packet loss when pinging your ISP but 0% from all other sources.

I have Cox as well and its decent, much better than the SBC DSL my parents have. Not sure on my plan rating but it was the middle plan of the 3 offered. I don’t know my ping times but my actual download speed is around 1300kbps and my upload is around 100kbps. That is more of a sustained peak speed, both normally operate 20% slower.
That’s fucked up dude. A better test would be tracert so you can see where the bottleneck is, but my connection to the corporate office in Atlanta (from here in Vancouver) is around 100ms – it’s something like 20 hops though. Something that is <10 hops is around 30ms.

where does he say that? I don’t see anything about packet loss. edit- never mind, didn’t realize that code box was so large. although given the different ip address cox.com is probably hosted somewhere else (still at cox but a different location) although that’s still ridiculous to get packet loss when he is most likely being routed through his ISP’s own routing.

those ping times are ridiculous though, you can call and complain and they might do something. when I was on DSL I called support about my ping being consistently around ~100 as opposed to the regular 30-50, it took them awhile but eventually they moved my connection to another card or something but whatever they did it fixed it. it was a very customer oriented ISP though so i don’t know if every ISP would be as generous.

this was back in my quake 3 days where ping was king

anyways, as the other guy said, you should definitely do a tracert to see where the latency spike first hits.

What is worth getting on the phone and bitching about?

are these spikes during “peak usage times” or just randomly? if randomly and long enough, you could probably bitch about them not providing the service you are paying for (and have some speed tests to back it up)..

if during peak use, they’ll probably just retort that that’s normal for peak usage hours and to suck it up.
I currently have the same issue with my DSL…except the problem only appears during peak usage times:

Good luck explaining the problem to the CSRs…as long as your speed tests are ok, you’re fucked. You can’t explain to them that latency is just as important as download/upload speed as most of them do not even know what latency is.
Are you using torrents currently? For cable to fairly local servers you should be consistently pinging under 50ms (may rise a little during peak times depending how overloaded the ISP is). Does your ISP have local game servers? Ping those and report back.

No related posts.

Vex Star » Atlanta

What do you consider acceptable ping RTTs?