| Rune Central http://runequake.com/forums/ |
|
| Any Central-US Time Warner cable users having lag? http://runequake.com/forums/viewtopic.php?f=3&t=1630 |
Page 1 of 1 |
| Author: | Killa [ Wed Dec 05, 2012 10:41 pm ] |
| Post subject: | Any Central-US Time Warner cable users having lag? |
Its pretty much unplayable for me now just in the past two weeks. Not sure what happened. As posted in another thread.. my ping is jumping everywhere. It will go from 50-140ms. I can deal with high ping if it stayed in the same general range... but with the random spikes I'm literally jerking around everywhere. I'm literally back to being one of the worst Quake players again...aagh!! Anybody else seeing similar to the below from Time Warner? To note-- My ping was always around 40ms until two weeks ago. C:\quake\Quake I>ping quake.runecentral.com -t Pinging quake.runecentral.com [209.239.113.236] with 32 byte Reply from 209.239.113.236: bytes=32 time=88ms TTL=47 Reply from 209.239.113.236: bytes=32 time=97ms TTL=47 Reply from 209.239.113.236: bytes=32 time=104ms TTL=47 Reply from 209.239.113.236: bytes=32 time=100ms TTL=47 Reply from 209.239.113.236: bytes=32 time=116ms TTL=47 Reply from 209.239.113.236: bytes=32 time=100ms TTL=47 Reply from 209.239.113.236: bytes=32 time=117ms TTL=47 Reply from 209.239.113.236: bytes=32 time=118ms TTL=47 Reply from 209.239.113.236: bytes=32 time=117ms TTL=47 Reply from 209.239.113.236: bytes=32 time=111ms TTL=47 Reply from 209.239.113.236: bytes=32 time=130ms TTL=47 Reply from 209.239.113.236: bytes=32 time=119ms TTL=47 Reply from 209.239.113.236: bytes=32 time=134ms TTL=47 Reply from 209.239.113.236: bytes=32 time=144ms TTL=47 Reply from 209.239.113.236: bytes=32 time=135ms TTL=47 Reply from 209.239.113.236: bytes=32 time=116ms TTL=47 Reply from 209.239.113.236: bytes=32 time=139ms TTL=47 Reply from 209.239.113.236: bytes=32 time=138ms TTL=47 Reply from 209.239.113.236: bytes=32 time=129ms TTL=47 Reply from 209.239.113.236: bytes=32 time=145ms TTL=47 Reply from 209.239.113.236: bytes=32 time=127ms TTL=47 Reply from 209.239.113.236: bytes=32 time=136ms TTL=47 Reply from 209.239.113.236: bytes=32 time=135ms TTL=47 Reply from 209.239.113.236: bytes=32 time=143ms TTL=47 Reply from 209.239.113.236: bytes=32 time=121ms TTL=47 Reply from 209.239.113.236: bytes=32 time=143ms TTL=47 Reply from 209.239.113.236: bytes=32 time=123ms TTL=47 Reply from 209.239.113.236: bytes=32 time=130ms TTL=47 Reply from 209.239.113.236: bytes=32 time=102ms TTL=47 Reply from 209.239.113.236: bytes=32 time=102ms TTL=47 Ping statistics for 209.239.113.236: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 88ms, Maximum = 145ms, Average = 121ms Control-C ^C C:\quake\Quake I> |
|
| Author: | steve [ Sun Oct 27, 2013 11:50 am ] |
| Post subject: | Re: Any Central-US Time Warner cable users having lag? |
All of a sudden I'm having this problem.... I seem to have this problem for a few weeks, then it goes away, then it comes back again. I've rebooted my router and modem just to ensure it isn't that. I don't lag elsewhere, just at Shmack. My ping hovers around 80-90 and then spikes to 180 every once in awhile. The gameplay ends up being stuttery. Any ideas? I'm also on Time Warner Cable in the Midwest. Code: steve$ ping quake.shmack.net PING quake.shmack.net (209.239.113.236): 56 data bytes 64 bytes from 209.239.113.236: icmp_seq=0 ttl=47 time=100.790 ms [b]64 bytes from 209.239.113.236: icmp_seq=1 ttl=47 time=148.387 ms[/b] 64 bytes from 209.239.113.236: icmp_seq=2 ttl=47 time=97.852 ms 64 bytes from 209.239.113.236: icmp_seq=3 ttl=47 time=89.596 ms 64 bytes from 209.239.113.236: icmp_seq=4 ttl=47 time=117.431 ms 64 bytes from 209.239.113.236: icmp_seq=5 ttl=47 time=66.842 ms [b]64 bytes from 209.239.113.236: icmp_seq=6 ttl=47 time=184.777 ms[/b] 64 bytes from 209.239.113.236: icmp_seq=7 ttl=47 time=62.114 ms 64 bytes from 209.239.113.236: icmp_seq=8 ttl=47 time=60.230 ms 64 bytes from 209.239.113.236: icmp_seq=9 ttl=47 time=61.235 ms 64 bytes from 209.239.113.236: icmp_seq=10 ttl=47 time=61.142 ms 64 bytes from 209.239.113.236: icmp_seq=11 ttl=47 time=60.999 ms 64 bytes from 209.239.113.236: icmp_seq=12 ttl=47 time=61.332 ms 64 bytes from 209.239.113.236: icmp_seq=13 ttl=47 time=58.064 ms 64 bytes from 209.239.113.236: icmp_seq=14 ttl=47 time=61.117 ms 64 bytes from 209.239.113.236: icmp_seq=15 ttl=47 time=60.518 ms รง64 bytes from 209.239.113.236: icmp_seq=16 ttl=47 time=59.371 ms 64 bytes from 209.239.113.236: icmp_seq=17 ttl=47 time=58.771 ms 64 bytes from 209.239.113.236: icmp_seq=18 ttl=47 time=60.781 ms My traceroute: Code: steve$ traceroute quake.shmack.net
traceroute to quake.shmack.net (209.239.113.236), 64 hops max, 52 byte packets 1 10.0.1.1 (10.0.1.1) 2.574 ms 0.564 ms 0.482 ms 2 142.254.153.65 (142.254.153.65) 6.021 ms 11.560 ms 12.493 ms 3 tge3-2.nwblwinbln-swt402.wi.rr.com (24.160.230.22) 7.651 ms 9.502 ms 6.184 ms 4 tge1-4.brfdwijana-swt401.wi.rr.com (24.160.228.26) 8.471 ms 7.359 ms 8.106 ms 5 tge0-9-0-0.milzwift-ccr01.mwrtn.rr.com (24.160.225.64) 9.726 ms 11.468 ms 11.946 ms 6 ae-6-0.cr0.chi30.tbone.rr.com (66.109.6.206) 20.265 ms 11.374 ms 11.962 ms 7 ae-0-0.cr0.chi10.tbone.rr.com (66.109.6.20) 12.801 ms 13.415 ms 13.918 ms 8 ae0.pr1.chi10.tbone.rr.com (107.14.17.192) 10.598 ms ae4.pr1.chi10.tbone.rr.com (66.109.1.66) 9.559 ms ae0.pr1.chi10.tbone.rr.com (107.14.17.192) 10.031 ms 9 te0-3-0-27.ccr21.ord03.atlas.cogentco.com (154.54.11.145) 51.156 ms 53.024 ms 53.136 ms 10 be2005.ccr21.ord01.atlas.cogentco.com (66.28.4.73) 54.049 ms be2003.ccr22.ord01.atlas.cogentco.com (154.54.29.21) 51.878 ms be2006.mpd21.ord01.atlas.cogentco.com (154.54.5.17) 55.889 ms 11 te3-2.ccr01.stl03.atlas.cogentco.com (154.54.27.30) 60.010 ms te7-2.ccr01.stl03.atlas.cogentco.com (154.54.2.217) 59.797 ms te8-2.ccr01.stl03.atlas.cogentco.com (154.54.88.30) 58.882 ms 12 te4-1.ccr01.stl04.atlas.cogentco.com (154.54.88.114) 60.028 ms te4-2.ccr01.stl04.atlas.cogentco.com (154.54.88.118) 75.361 ms te7-1.ccr01.stl04.atlas.cogentco.com (154.54.88.122) 80.414 ms 13 38.104.162.90 (38.104.162.90) 68.083 ms 38.88.130.6 (38.88.130.6) 60.951 ms 38.88.130.10 (38.88.130.10) 59.609 ms 14 static-ip-209-239-125-3.inaddr.ip-pool.com (209.239.125.3) 61.242 ms static-ip-209-239-125-4.inaddr.ip-pool.com (209.239.125.4) 68.233 ms static-ip-209-239-125-3.inaddr.ip-pool.com (209.239.125.3) 58.972 ms 15 quake.shmack.net (209.239.113.236) 59.551 ms 60.033 ms 59.214 ms |
|
| Author: | Scoffer [ Thu Oct 31, 2013 6:55 pm ] |
| Post subject: | Re: Any Central-US Time Warner cable users having lag? |
Been crazy slow for me too. Just got back to playing some. I thought it was just me.. The cheats still seem to have good pings...! Except for you two... King Scoffer! |
|
| Author: | Meatwad [ Thu Oct 31, 2013 7:17 pm ] |
| Post subject: | Re: Any Central-US Time Warner cable users having lag? |
Laggy for Me as well Code: Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved. C:\Windows\System32>tracert quake.shmack.net Tracing route to quake.shmack.net [209.239.113.236] over a maximum of 30 hops: 1 5 ms 4 ms 4 ms L100.PITBPA-VFTTP-22.verizon-gni.net [96.236.129 .1] 2 5 ms 4 ms 4 ms G2-0-4-222.PITBPA-LCR-04.verizon-gni.net [130.81 .129.96] 3 11 ms 11 ms 11 ms P5-0-0.PITBPA-LCR-03.verizon-gni.net [130.81.27. 250] 4 16 ms 23 ms 11 ms so-15-0-3-0.RES-BB-RTR1.verizon-gni.net [130.81. 28.204] 5 19 ms 15 ms 15 ms 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37] 6 * 82 ms 77 ms te0-3-0-14.ccr41.iad02.atlas.cogentco.com [154.5 4.13.137] 7 76 ms 74 ms 77 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41 .206] 8 95 ms 95 ms 91 ms be2152.ccr21.ord01.atlas.cogentco.com [154.54.30 .122] 9 92 ms 94 ms 94 ms te8-2.ccr01.stl03.atlas.cogentco.com [154.54.88. 30] 10 93 ms 94 ms 94 ms te4-7.ccr01.stl04.atlas.cogentco.com [154.54.88. 154] 11 90 ms 95 ms 94 ms 38.104.162.66 12 95 ms 95 ms 90 ms static-ip-209-239-125-3.inaddr.ip-pool.com [209. 239.125.3] 13 90 ms 94 ms 94 ms quake.shmack.net [209.239.113.236] |
|
| Page 1 of 1 | All times are UTC - 5 hours [ DST ] |
| Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |
|