| Improve Qwest 40/20 Ping Times? I switched from Comcast to Qwest's 40/20 service recently. Pleased with the bandwidth speeds but unhappy with the latency on the connection. About the best ping I can get is 40-50ms. Compared to the 10 or 15ms I got with Comcast's service it feels mega slow.
Any thoughts on how I can improve my Qwest ping times better?
PING 174.30.214.210 (174.30.214.210) 56(84) bytes of data.
64 bytes from 174.30.214.210: icmp_seq=1 ttl=52 time=49.3 ms
64 bytes from 174.30.214.210: icmp_seq=2 ttl=52 time=49.8 ms
64 bytes from 174.30.214.210: icmp_seq=3 ttl=52 time=49.3 ms
64 bytes from 174.30.214.210: icmp_seq=4 ttl=52 time=49.6 ms
64 bytes from 174.30.214.210: icmp_seq=5 ttl=52 time=49.6 ms
--- 174.30.214.210 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4013ms
rtt min/avg/max/mdev = 49.322/49.569/49.890/0.351 ms
traceroute to 174.30.214.210 (174.30.214.210), 30 hops max, 40 byte packets
1 21.9.344a.static.theplanet.com (74.52.9.33) 1.259 ms 1.596 ms 1.830 ms
2 po201.dsr01.dllstx2.networklayer.com (70.87.254.137) 0.441 ms 0.442 ms 0.547 ms
3 te3-2.dsr01.dllstx3.networklayer.com (70.87.253.129) 0.537 ms te4-3.dsr01.dllstx3.networklayer.com (70.87.255.113) 0.652 ms te4-1.dsr01.dllstx3.networklayer.com (70.87.255.105) 0.747 ms
4 e8-3.ibr03.dllstx3.networklayer.com (70.87.253.85) 0.480 ms 0.475 ms 0.589 ms
5 xe-3-0-0.er1.dfw2.us.above.net (64.125.199.93) 0.455 ms 0.553 ms 209.66.99.89.available.above.net (209.66.99.89) 0.542 ms
6 xe-5-3-0.er2.dfw2.us.above.net (64.125.29.122) 0.542 ms 0.440 ms 0.549 ms
7 dap-brdr-03.inet.qwest.net (63.146.27.121) 0.564 ms 0.559 ms 0.549 ms
8 * * *
9 mpls-dsl-gw46-110.mpls.qwest.net (75.168.229.110) 27.664 ms 27.650 ms 27.261 ms
10 174-30-214-210.mpls.qwest.net (174.30.214.210) 50.096 ms 49.433 ms 49.684 ms |
|
Bink
join:2006-05-14
Denver, CO
kudos:4 | Have you tried prayer? |
|
| reply to SpenceW
50ms is fine for anything your doing on the web including gaming. With a 10ms time, that server must be on comcasts network. There is no way of improving your latency. |
|
| I routinely got 10-15ms to Google.com from Comcast. And players on the servers I've hosted generally pinged 15-20ms faster versus Qwest.
So, there's nothing I can do? |
|
| Because you have vdsl there is nothing that can be done, now if you had adsl this would be a different story. |
|
|
|
| Ugh. Ok, thanks for the help. Probably going back to CC. |
|
| said by SpenceW :Ugh. Ok, thanks for the help. Probably going back to CC.
Over unnoticeable ping differences? I mean in gaming your not going to notice a 10ms ping over a 50ms ping. |
|
| My pings did the same when I switched. My gaming has actually gotten better. I think the pings might be higher but they are more consistent. Comcast pings would be good then spike then good etc...40ms time inst going to be noticeable. |
|
| For my own gaming I've noticed the range of servers under 90ms (personal preference) is less than what I had on Comcast.
For the servers I host, most folks are unhappy because I've just added another 30-40ms to their ping times. Since many players are connecting from the EU, this means their pings are now north of 160ms.
Bummer. |
|
| reply to SpenceW
You can not host games server on Qwest. I'm not saying that it's against the TOS what i'm saying it it's unfeasible. Now I do know that Comcast has a statement in the TOS about not running servers of any type on their network. |
|
| Um I host halo and bf2 unranked servers all the time. |
|
| reply to SpenceW
I can't believe the OP was complaining about a 40-50ms ping time.
I'm with Comcast -- considering moving to Qwest -- and have a 143ms time to that site. My google ping is 65ms. It's at least 12ms to get to ABQ and I think about every route goes through there from Las Cruces. Pretty much any site (including gamings sites) will have a 50-70ms response at best.
Unfortunately, I don't think there will be any significant difference with Qwest -- it's just my physical location. OP must be at a good spot. |
|
