US Cable Support > Comcast HSI > [Praise] I cant believe how low my latency is on Comcast

[Praise] I cant believe how low my latency is on Comcast

Not bad.
Got a decent line to that test server.

Now mine has gone from an acceptable 16ms when I first got Comcast, to a test server ~100 miles away, to well over 30ms now.

can't say its getting better.. fast yes, better, no.
--
Webmaster - Steve
- - - - - - - - - - - -
»www.1-gb.net
»www.ppnstudio.com

reply to nine9s2
I normally see 11 MS pings.

reply to nine9s2
Guess it all depends on how close you are to the server.

reply to nine9s2

This is typical for me. Comcast rocks!
--
I know you think you understand what you thought I said, but I am not sure you realize what you heard is not what I meant. Nixon

reply to pokesph

reply to nine9s2
My ping to this server is always about 5ms.

My best ping result on speedtest.net is 12 ms to a server about 100 miles away.

reply to KevTech

Even the first hop to a router is 1ms, isnt it?

Yes, or generally less than 1 ms.

reply to nine9s2
This is typical for me-



San Jose is 150 miles southeast of me. Everything here goes to the main CMTS in Ukiah, and then south into the Bay area then east to Sacramento to get to the Comcast iBone.

Tracing route to any-fp3-real.wa1.b.yahoo.com [98.139.127.62]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms my.router [192.168.1.1]
2 21 ms 28 ms 21 ms 67.180.172.1
3 9 ms 9 ms 9 ms te-3-3-sr01.ukiah.ca.sfba.comcast.net [68.86.249
.25]
4 11 ms 11 ms 11 ms te-8-1-ur06.rohnertpr.ca.sfba.comcast.net [68.87
.226.229]
5 15 ms 14 ms 13 ms te-0-1-0-7-ar01.oakland.ca.sfba.comcast.net [68.
87.192.162]
6 18 ms 19 ms 19 ms pos-2-8-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.95.81]
7 18 ms 19 ms 23 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.181]
8 17 ms 17 ms 16 ms xe-10-3-0.edge1.SanJose1.Level3.net [4.71.118.5]

9 19 ms 18 ms 19 ms ae-33-80.car3.SanJose1.Level3.net [4.69.152.133]

10 21 ms 18 ms 21 ms YAHOO-INC.car3.SanJose1.Level3.net [4.71.112.14]

11 20 ms 18 ms 18 ms ae-0-d171.msr2.sp1.yahoo.com [216.115.107.83]
12 19 ms 21 ms 20 ms et-17-1.fab1-1-gdc.sp2.yahoo.com [67.195.128.65]

13 29 ms 19 ms 20 ms po-10.bas1-3-prd.sp2.yahoo.com [76.13.244.7]
14 64 ms 53 ms 47 ms ir2.fp.vip.sp2.yahoo.com [98.139.127.62]

Trace complete.

reply to nine9s2
Yeah, pretty low here as well. No zeros though .

reply to nine9s2
This thread makes me wonder why I still put up with Uverse and it's lack of reliability at home. albeit my latency is about as good as it gets for Uverse (average 24 MS pings).
Perhaps it's my dislike towards Comcast's general attitude in customer service, or maybe because I'm not familiar enough with them to know what strings to pull to get good service right away (I know AT&T very well and know exactly who to contact for good service)

that could be a double edged sword, I mean if you have Comcast and get great service you wouldn't need to contact them for customer support, where as with U Verse you have good customer support because you might be getting bad service.

reply to n_w95482
WOW, they must be offering the new Tiers here now (Netcool said it'd be soon, since we have the new provisioning now). I probably don't want to know what that costs though. lol Blast! 20/4 at 72 bucks a month is enough.

reply to Mike Wolf

reply to nine9s2

For me it wouldn't matter if a server was in Ukiah, 10 miles south or in SF, 120 miles south, the data has to go to Ukiah, then the Bay Area and then Sacramento to get to the backbone, so actually I'd end up getting better results to SF even though it's further away. As far as I know, Comcast does not have local peering here, so there is no way to contact a local server without going through all that and then back up.

Ping is an extremely poor metric to gauge the quality of a connection, without a baseline. While a lower ping is better, it doesn't mean anything alone. As others have mentioned, it has a lot to do with the distance from the speedtest server. It's not like a magical number that rates the quality of your connection. But, it doesn't just deal with the geographical distance from a speedtest server, since it includes the number of hops for that test specifically. What I'm basically trying to say is that you can't judge a connection by ping alone. I have both Comcast and FiOS. My Comcast connection has a 12ms ping to the Philadelphia speedtest server, while my FiOS connection has a 25ms ping to the speedtest server. That doesn't mean Comcast is superior; it just means the route to the Comcast speedtest server is shorter because you are testing from within the same network. A route to a different server (like a website) may be completely different and yield equal or opposite results.

However, ping is important to know as a baseline. You want to know if it varies at all between tests to the same server (jitter), or if it varies depending on the time of day. This can help a great deal in troubleshooting. For example, if you notice your ping is normally 5ms but now it's 200ms, there may be a problem with either your connection or a bad route. Alone, ping means nothing.