I actually have no complaints about Time Warner, no other internet problems besides this. It all started a little over a week or so ago and it is slowly getting worse each day. All my fleetmates are having the same issue. Whats weird is it sounds a lot like the same problem people were having back in June if you check some of the other server disconnect threads. Well, anyway, not much I can do except wait for an answer from Cryptic. I'm a lifer so....yeah....waiting :P.
I also have Time Warner, and I'm in Texas as well. I can't get past the load screen unless I use a proxy, but then there's the inherent issue of latency introduced by the extra routing. The fact that using a proxy connection causes me to think that we're all going through a bad node somewhere in our normal connection route. If tech support compares our respective tracert results there's probably some common elements we share.
I really want to play again. I seem to be getting DCed every 30 seconds or so for anywhere between 11 and 63 seconds. in loading i always get dropped....been stuck in K7s parking lot for 3 days. it wont even load me in and i dont want to play another toon. I hope you guys can hotfix this issue quick without breaking anything else. can you all imagine how hard it is for these designers...1 little line...makes it almost unplayable. (ill keep playing even if i just get to look at my ship...lol)
im out here in WV...i dont think its our providers...but maybe that isnt helping us either.
ive been having probelms too and im not on timewarner or what ever its called im in the UK using SKY but other games work fine, sto seems to have its good and bad days some times i give up completly and just play something else.
recently been getting server not responding lag longer load time than normal. ive also got the odd crash while in game always send a crash report to cryptic at least when the crash manager doesnt crash lol.
i dont think its on my end as other games work fine skrim crysis2 metro they all play perfect.
ive been having problems too and im not on timewarner or what ever its called im in the UK using SKY ....
Same here. Last night wasnt too bad, the game was playable, but there were still obvious "issues". NPC's that seemed to freeze and then all of a sudden rocket forward like something out of the Benny Hill Show! That was quite amusing actually when A Jem'hadar did it lol
Also when beaming in to an area it was slow to draw the environment. I also had a few DC's but not as bad as it was over the weekend.
wow, lots of texas trekkies, happy sight! last night was good until about midnight or eleven o clock, and then the tidal wave of issues hit me, in past nights it seemed that if i could "escape" to a(betreka nebula or other offshoot zone) I' stabilize and could que and enjoy the game, but last night it wasn't to be, it kept giving me the same issues. up there on top you all linked more forums, if they are still active would you mind copy pasting a link to this thread there as well so we can all be aware of each other and if one dev is looking around he see's issues in both spots...although its looking like if we get a patch this thursday it will likely be to only fix this issue...at least we hope........
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 7 ms 9 ms 18 ms 8 ms 9 ms 9 ms 8 ms 7 ms 7 ms 8 ms [10.239.53.1]
3 8 ms 8 ms 7 ms 8 ms 8 ms 7 ms 7 ms 8 ms 7 ms 9 ms tge7-4.austtxm-er02.texas.rr.com [66.68.1.149]
4 20 ms 26 ms 17 ms 26 ms 20 ms 22 ms 33 ms 22 ms 22 ms 26 ms tge0-10-0-13.austtxrdcsc-cr01.texas.rr.com [66.68.5.75]
5 19 ms 17 ms 24 ms 18 ms 20 ms 21 ms 24 ms 21 ms 21 ms 17 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 15 ms 29 ms 20 ms 22 ms 16 ms 17 ms 20 ms 17 ms 25 ms 21 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 22 ms 20 ms 19 ms 20 ms 22 ms 19 ms 25 ms 22 ms 19 ms 23 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 169 ms 17 ms 44 ms 19 ms 101 ms 224 ms 384 ms 154 ms 17 ms 28 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 20 ms 20 ms 20 ms 21 ms 22 ms 20 ms 20 ms 20 ms 20 ms 21 ms te0-1-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.6.65]
10 32 ms 31 ms 29 ms 29 ms 30 ms 31 ms 30 ms 30 ms 30 ms 31 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54.3.18]
11 43 ms 39 ms 54 ms 39 ms 40 ms 39 ms 40 ms 49 ms 39 ms 41 ms te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54.30.169]
12 62 ms 64 ms 62 ms 64 ms 63 ms 62 ms 62 ms 63 ms 62 ms 64 ms te0-0-0-5.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
13 62 ms 64 ms 205 ms 383 ms 66 ms 64 ms 62 ms 65 ms 62 ms 63 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 68 ms 62 ms 60 ms 74 ms 65 ms 63 ms 62 ms 74 ms 70 ms 63 ms [38.111.40.114]
15 60 ms 63 ms 60 ms 61 ms 60 ms 61 ms 65 ms 75 ms 60 ms 60 ms [208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 60ms, Maximum = 75ms, Average = 62ms
I'm playing in Austin on Time Warner as well. Server timeouts... etc... all I can say is completely unacceptable gameplay that happened just following this last patch. I submitted a ticket and I got the standard TRIBBLE that everyone already knows how to do before contacting support. Contact support on this issue only if you want a nice tap dance.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 42 ms * 24 ms cpe-72-190-124-1.tx.res.rr.com [72.190.124.1]
2 10 ms * 10 ms tge7-1.dllatx19-er02.texas.rr.com [24.164.211.12
1]
3 24 ms * 47 ms tge2-2.dllatx10-tr02.texas.rr.com [24.175.38.192
]
4 21 ms * 20 ms 24.175.49.8
5 21 ms * 24 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
6 22 ms * 50 ms 107.14.17.141
7 21 ms * 21 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
8 20 ms * 21 ms te0-2-0-3.ccr21.dfw01.atlas.cogentco.com [154.54
.6.93]
9 27 ms * 29 ms te0-4-0-1.mpd21.mci01.atlas.cogentco.com [154.54
.5.126]
10 74 ms * 39 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
11 60 ms 79 ms 64 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.43.178]
12 63 ms 63 ms 63 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 65 ms 71 ms 71 ms 38.111.40.114
14 62 ms 63 ms 60 ms 208.95.185.41
Trace complete.
Pinging patchserver.crypicstudios.com [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=36ms TTL=50
Reply from 67.215.65.132: bytes=32 time=36ms TTL=50
Reply from 67.215.65.132: bytes=32 time=37ms TTL=50
Reply from 67.215.65.132: bytes=32 time=34ms TTL=50
Ping statistics for 67.215.65.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 37ms, Average = 35ms
After several tests of my connection, (In Austin) I have contacted TWC and I have reported the issue. They have opened a trouble ticket and will be watching the data-flow for the next few hours.
The problem that I located is NOT on a TWC server, but on a Cogent Co server. Below is one of several tests.
9 * 157 ms 214 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
This does not seem to be a full time issue. At times we can play just fine, and at other times we have issues. I strongly recommend that everyone else using TWC here in Austin contact their tech support and report that you're having this same problem. When you speak with an agent, please give them this "Trouble ticket number" 11143479. That way they can use the information as data collection for how many PPL are having this issue and what servers they are connecting through.
Please report the issue ASAP so that the data collection can begin and we can get this issue fully resolved sooner.
Also please keep in mind that TWC can NOT fix the issue directly. They will have to report their findings to Cogent Co and they will have to pick it up from there to resolve it. With that in mind, there is no reason to be angry with or yell at any TWC rep that you speak with. Unless they give you a hard time about accepting that you're trying to add to the trouble ticket...
Draco, that's exactly what I've been thinking, and the same node I've been suspecting as well. That's the first non time warner element I hit on my route, and after about a hundred tracerts waiting for timeouts, almost all of them occur on the last TW node or the first non TW one. Pair that up with tracerts done on services I have no issue with (streaming video/audio and other games) and I have no other problems through 66.109.6.179 so the issues are likely from 154.54.11.49 not responding.
Now, this is not to say everyone is in the same boat, but for all the time warner people out there, how many of you go through that address?
Test results: tracert -w 1000 patchserver.crypticstudios.com
1 <1 ms 1 ms <1 ms 192.168.1.1
2 29 ms 37 ms 31 ms 10.88.19.1
3 17 ms 33 ms 51 ms tge7-3.wacotxkil-er02.texas.rr.com [24.26.192.86]
4 38 ms 39 ms 47 ms tge0-8-0-3.wacotxmhe-cr02.texas.rr.com [24.175.62.144]
5 24 ms 38 ms 24 ms agg24.hstntxl3-cr01.texas.rr.com [24.175.62.236]
6 31 ms 38 ms 31 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 39 ms 91 ms 52 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 35 ms 217 ms 217 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 32 ms 86 ms 109 ms te0-4-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.82.21]
10 55 ms 48 ms 50 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54.3.18]
11 50 ms 55 ms 45 ms te0-1-0-5.mpd21.ord01.atlas.cogentco.com [154.54.84.82]
12 73 ms 86 ms 65 ms te0-0-0-5.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
13 79 ms 80 ms 90 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 92 ms 89 ms 106 ms 38.111.40.114
15 103 ms 71 ms 79 ms 208.95.185.41
I wasn't having lag issues when I ran the tracer but the info should still be helpful. I'm in Killeen, Texas using TWC.
Edit: Adding ping test results
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=84ms TTL=47
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=80ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=93ms TTL=47
Reply from 208.95.185.41: bytes=32 time=74ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=66ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=75ms TTL=47
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=75ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=92ms TTL=47
Ping statistics for 208.95.185.41:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 93ms, Average = 73ms
8 35 ms 217 ms 217 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
Looks like you're hitting that same server that's causing the issues. The ping on that server is also rather high, as you can see in your trace. You may want to report it as well. I know a guy in Dallas that's also having the same issue.
Another thing is that I did contact Cogent Co about the issue, they are unwilling to even look into the issue due to my not being a customer of theirs. However, I did get the email address to send traces to so that they can be looked at by their support staff.
You can email the trace routes to support@cogentco.com and report the connection issues to them for investigation. Hopefully hitting both TWC and Cogent Co with reports of the issue will help make this issue get resolved faster. We can also hope that Cryptic will send the report down to them to let them know that we're having this issue.
I provided TWC the trouble ticket number Draco0167 gave us.
TWC pushed a firmware update to my modem that might help for gaming, and they said they are working on the issue.
It seems everyone is getting very high spikes from the dfw03.atlas.cogentco.com hop. Not sure if this is causing the problem though, because we getting a good overall connection time.
This is the ping result for that first cogent co server:
Pinging 154.54.11.49 with 32 bytes of data:
Reply from 154.54.11.49: bytes=32 time=55ms TTL=248
Reply from 154.54.11.49: bytes=32 time=21ms TTL=248
Reply from 154.54.11.49: bytes=32 time=23ms TTL=248
Reply from 154.54.11.49: bytes=32 time=27ms TTL=248
Reply from 154.54.11.49: bytes=32 time=20ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=24ms TTL=248
Reply from 154.54.11.49: bytes=32 time=23ms TTL=248
Reply from 154.54.11.49: bytes=32 time=46ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=60ms TTL=248
Reply from 154.54.11.49: bytes=32 time=43ms TTL=248
Reply from 154.54.11.49: bytes=32 time=68ms TTL=248
Reply from 154.54.11.49: bytes=32 time=42ms TTL=248
Reply from 154.54.11.49: bytes=32 time=60ms TTL=248
Reply from 154.54.11.49: bytes=32 time=231ms TTL=248
Request timed out.
Reply from 154.54.11.49: bytes=32 time=175ms TTL=248
Ping statistics for 154.54.11.49:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 231ms, Average = 54ms
TWC pushed a firmware update to my modem that might help for gaming, and they said they are working on the issue.
It seems everyone is getting very high spikes from the dfw03.atlas.cogentco.com hop. Not sure if this is causing the problem though, because we getting a good overall connection time.
We're getting a good connection time when the server is letting us through but it's not stable. The connection is fine at some points but horrible at other points, up to causing the disconnects that we've all seen.
While it's possible that this connection point is not the issue it is unlikely from the tests I've been doing. When not having "Server Not Responding" message the connection is fine or just high ping. But when I am getting that message, the connection is high ping or timed out. This is either the problem or a very odd coincidence.
Also, just an update, I just got off the phone w/ TWC again since the connection became unstable for a short time and I wanted them to look at it while it was going on. They gave me a hard time about it for a little bit and by the time I got them to look at it, the issue had subsided... The last person I spoke w/ informed me that in order to get a senior tech to look at the issue I must bypass my router (To rule the firewall on the router out of the equation.) and while I don't believe it will mean anything, I will do that tonight just so that I can make them happy and get to a senior tech to discuss the issue. =\
9 172 ms 201 ms 489 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
As you can see, one of my spikes hit 489 and this is while I can stay connected. The only thing I notice right now is a bit of lag here and there. One of them that I posted earlier timed out. This is just not a stable connection. Medtac124 is also catching the spikes on the ping test.
I am also in the Killeen/Fort Hood/Copperas Cove area and I started getting these issues last thursday right after patch day. Seemed to fix itself then bam tonight right back to it again. I am not a huge tech geek so all the tracer pings and everything else seem like jibberish to me but yea no STO for me and I was playing just fine this morning.
[as of 11:03 Sept 11 2012]
Well i am done tried everything to get this stupid game back up and NOTHING! again i am so happy to waste my money on a product that dosen't give me anything. Thank you so much TPW for not checking your work before you turn it in. This is like playing with one bullet in the chamber! Oohh I am going to DC now.....no wait now..... oohhh wait NOW it DCed me. Thank you.
After several tests of my connection, (In Austin) I have contacted TWC and I have reported the issue. They have opened a trouble ticket and will be watching the data-flow for the next few hours.
The problem that I located is NOT on a TWC server, but on a Cogent Co server. Below is one of several tests.
This does not seem to be a full time issue. At times we can play just fine, and at other times we have issues. I strongly recommend that everyone else using TWC here in Austin contact their tech support and report that you're having this same problem. When you speak with an agent, please give them this "Trouble ticket number" 11143479. That way they can use the information as data collection for how many PPL are having this issue and what servers they are connecting through.
Please report the issue ASAP so that the data collection can begin and we can get this issue fully resolved sooner.
Also please keep in mind that TWC can NOT fix the issue directly. They will have to report their findings to Cogent Co and they will have to pick it up from there to resolve it. With that in mind, there is no reason to be angry with or yell at any TWC rep that you speak with. Unless they give you a hard time about accepting that you're trying to add to the trouble ticket...
So I called TWC... after 15 minutes they admitted they that they did have this ticket... but then they told me that they needed more than the few players that had already contacted them about it for them to launch a full investigation... I asked why more than a few people were necessary to look into an issue but he was just a desk clerk who liked to talk over me... He also told me that "I" should contact Cryptic and Cogent Co and tell them they should call TWC and open a dialog... bleh
moral of this? everyone who has this issue please call in!
(512)-485-5555
Ticket #: 11143479
Edit: So I searched for a known cryptic ticket without success and informed them of the issue and copied this body of text to go with it. They most likely already know but it really sucks that such a unique and focused group of TWC users are having such difficulty
Comments
In dallas
im out here in WV...i dont think its our providers...but maybe that isnt helping us either.
recently been getting server not responding lag longer load time than normal. ive also got the odd crash while in game always send a crash report to cryptic at least when the crash manager doesnt crash lol.
i dont think its on my end as other games work fine skrim crysis2 metro they all play perfect.
Same here. Last night wasnt too bad, the game was playable, but there were still obvious "issues". NPC's that seemed to freeze and then all of a sudden rocket forward like something out of the Benny Hill Show! That was quite amusing actually when A Jem'hadar did it lol
Also when beaming in to an area it was slow to draw the environment. I also had a few DC's but not as bad as it was over the weekend.
These disconnects are very bothersome, and make the game unplayable.
Here are sample traces for each of the IPs in my trace route:
Target Name: patchserver.crypticstudios.com
IP: 208.95.185.41
Date/Time: 9/11/2012 12:45:38 PM to 9/11/2012 12:46:23 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms
[192.168.1.1]
2 7 ms 9 ms 18 ms 8 ms 9 ms 9 ms 8 ms 7 ms 7 ms 8 ms
[10.239.53.1]
3 8 ms 8 ms 7 ms 8 ms 8 ms 7 ms 7 ms 8 ms 7 ms 9 ms
tge7-4.austtxm-er02.texas.rr.com [66.68.1.149]
4 20 ms 26 ms 17 ms 26 ms 20 ms 22 ms 33 ms 22 ms 22 ms 26 ms
tge0-10-0-13.austtxrdcsc-cr01.texas.rr.com [66.68.5.75]
5 19 ms 17 ms 24 ms 18 ms 20 ms 21 ms 24 ms 21 ms 21 ms 17 ms
agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 15 ms 29 ms 20 ms 22 ms 16 ms 17 ms 20 ms 17 ms 25 ms 21 ms
ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 22 ms 20 ms 19 ms 20 ms 22 ms 19 ms 25 ms 22 ms 19 ms 23 ms
ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 169 ms 17 ms 44 ms 19 ms 101 ms 224 ms 384 ms 154 ms 17 ms 28 ms
te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 20 ms 20 ms 20 ms 21 ms 22 ms 20 ms 20 ms 20 ms 20 ms 21 ms
te0-1-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.6.65]
10 32 ms 31 ms 29 ms 29 ms 30 ms 31 ms 30 ms 30 ms 30 ms 31 ms
te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54.3.18]
11 43 ms 39 ms 54 ms 39 ms 40 ms 39 ms 40 ms 49 ms 39 ms 41 ms
te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54.30.169]
12 62 ms 64 ms 62 ms 64 ms 63 ms 62 ms 62 ms 63 ms 62 ms 64 ms
te0-0-0-5.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
13 62 ms 64 ms 205 ms 383 ms 66 ms 64 ms 62 ms 65 ms 62 ms 63 ms
te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 68 ms 62 ms 60 ms 74 ms 65 ms 63 ms 62 ms 74 ms 70 ms 63 ms
[38.111.40.114]
15 60 ms 63 ms 60 ms 61 ms 60 ms 61 ms 65 ms 75 ms 60 ms 60 ms
[208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 60ms, Maximum = 75ms, Average = 62ms
when can we expect an emergency patch? does anyone know whats going on?:mad:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 42 ms * 24 ms cpe-72-190-124-1.tx.res.rr.com [72.190.124.1]
2 10 ms * 10 ms tge7-1.dllatx19-er02.texas.rr.com [24.164.211.12
1]
3 24 ms * 47 ms tge2-2.dllatx10-tr02.texas.rr.com [24.175.38.192
]
4 21 ms * 20 ms 24.175.49.8
5 21 ms * 24 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
6 22 ms * 50 ms 107.14.17.141
7 21 ms * 21 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
8 20 ms * 21 ms te0-2-0-3.ccr21.dfw01.atlas.cogentco.com [154.54
.6.93]
9 27 ms * 29 ms te0-4-0-1.mpd21.mci01.atlas.cogentco.com [154.54
.5.126]
10 74 ms * 39 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
11 60 ms 79 ms 64 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.43.178]
12 63 ms 63 ms 63 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 65 ms 71 ms 71 ms 38.111.40.114
14 62 ms 63 ms 60 ms 208.95.185.41
Trace complete.
Pinging patchserver.crypicstudios.com [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=36ms TTL=50
Reply from 67.215.65.132: bytes=32 time=36ms TTL=50
Reply from 67.215.65.132: bytes=32 time=37ms TTL=50
Reply from 67.215.65.132: bytes=32 time=34ms TTL=50
Ping statistics for 67.215.65.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 37ms, Average = 35ms
The problem that I located is NOT on a TWC server, but on a Cogent Co server. Below is one of several tests.
This does not seem to be a full time issue. At times we can play just fine, and at other times we have issues. I strongly recommend that everyone else using TWC here in Austin contact their tech support and report that you're having this same problem. When you speak with an agent, please give them this "Trouble ticket number" 11143479. That way they can use the information as data collection for how many PPL are having this issue and what servers they are connecting through.
Please report the issue ASAP so that the data collection can begin and we can get this issue fully resolved sooner.
Also please keep in mind that TWC can NOT fix the issue directly. They will have to report their findings to Cogent Co and they will have to pick it up from there to resolve it. With that in mind, there is no reason to be angry with or yell at any TWC rep that you speak with. Unless they give you a hard time about accepting that you're trying to add to the trouble ticket...
Now, this is not to say everyone is in the same boat, but for all the time warner people out there, how many of you go through that address?
Well how interesting.
I am on the phone with Time Warner now.
1 <1 ms 1 ms <1 ms 192.168.1.1
2 29 ms 37 ms 31 ms 10.88.19.1
3 17 ms 33 ms 51 ms tge7-3.wacotxkil-er02.texas.rr.com [24.26.192.86]
4 38 ms 39 ms 47 ms tge0-8-0-3.wacotxmhe-cr02.texas.rr.com [24.175.62.144]
5 24 ms 38 ms 24 ms agg24.hstntxl3-cr01.texas.rr.com [24.175.62.236]
6 31 ms 38 ms 31 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 39 ms 91 ms 52 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 35 ms 217 ms 217 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 32 ms 86 ms 109 ms te0-4-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.82.21]
10 55 ms 48 ms 50 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54.3.18]
11 50 ms 55 ms 45 ms te0-1-0-5.mpd21.ord01.atlas.cogentco.com [154.54.84.82]
12 73 ms 86 ms 65 ms te0-0-0-5.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
13 79 ms 80 ms 90 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 92 ms 89 ms 106 ms 38.111.40.114
15 103 ms 71 ms 79 ms 208.95.185.41
I wasn't having lag issues when I ran the tracer but the info should still be helpful. I'm in Killeen, Texas using TWC.
Edit: Adding ping test results
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=84ms TTL=47
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=80ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=93ms TTL=47
Reply from 208.95.185.41: bytes=32 time=74ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=66ms TTL=47
Reply from 208.95.185.41: bytes=32 time=71ms TTL=47
Reply from 208.95.185.41: bytes=32 time=75ms TTL=47
Reply from 208.95.185.41: bytes=32 time=67ms TTL=47
Reply from 208.95.185.41: bytes=32 time=75ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=70ms TTL=47
Reply from 208.95.185.41: bytes=32 time=69ms TTL=47
Reply from 208.95.185.41: bytes=32 time=92ms TTL=47
Ping statistics for 208.95.185.41:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 93ms, Average = 73ms
Looks like you're hitting that same server that's causing the issues. The ping on that server is also rather high, as you can see in your trace. You may want to report it as well. I know a guy in Dallas that's also having the same issue.
Another thing is that I did contact Cogent Co about the issue, they are unwilling to even look into the issue due to my not being a customer of theirs. However, I did get the email address to send traces to so that they can be looked at by their support staff.
You can email the trace routes to support@cogentco.com and report the connection issues to them for investigation. Hopefully hitting both TWC and Cogent Co with reports of the issue will help make this issue get resolved faster. We can also hope that Cryptic will send the report down to them to let them know that we're having this issue.
TWC pushed a firmware update to my modem that might help for gaming, and they said they are working on the issue.
It seems everyone is getting very high spikes from the dfw03.atlas.cogentco.com hop. Not sure if this is causing the problem though, because we getting a good overall connection time.
Pinging 154.54.11.49 with 32 bytes of data:
Reply from 154.54.11.49: bytes=32 time=55ms TTL=248
Reply from 154.54.11.49: bytes=32 time=21ms TTL=248
Reply from 154.54.11.49: bytes=32 time=23ms TTL=248
Reply from 154.54.11.49: bytes=32 time=27ms TTL=248
Reply from 154.54.11.49: bytes=32 time=20ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=24ms TTL=248
Reply from 154.54.11.49: bytes=32 time=23ms TTL=248
Reply from 154.54.11.49: bytes=32 time=46ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=28ms TTL=248
Reply from 154.54.11.49: bytes=32 time=60ms TTL=248
Reply from 154.54.11.49: bytes=32 time=43ms TTL=248
Reply from 154.54.11.49: bytes=32 time=68ms TTL=248
Reply from 154.54.11.49: bytes=32 time=42ms TTL=248
Reply from 154.54.11.49: bytes=32 time=60ms TTL=248
Reply from 154.54.11.49: bytes=32 time=231ms TTL=248
Request timed out.
Reply from 154.54.11.49: bytes=32 time=175ms TTL=248
Ping statistics for 154.54.11.49:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 231ms, Average = 54ms
Nice little spike there at the end.
I thought it was just me. I'm laid up in the hospital, and thought it was their internet server.
We're getting a good connection time when the server is letting us through but it's not stable. The connection is fine at some points but horrible at other points, up to causing the disconnects that we've all seen.
While it's possible that this connection point is not the issue it is unlikely from the tests I've been doing. When not having "Server Not Responding" message the connection is fine or just high ping. But when I am getting that message, the connection is high ping or timed out. This is either the problem or a very odd coincidence.
Also, just an update, I just got off the phone w/ TWC again since the connection became unstable for a short time and I wanted them to look at it while it was going on. They gave me a hard time about it for a little bit and by the time I got them to look at it, the issue had subsided... The last person I spoke w/ informed me that in order to get a senior tech to look at the issue I must bypass my router (To rule the firewall on the router out of the equation.) and while I don't believe it will mean anything, I will do that tonight just so that I can make them happy and get to a senior tech to discuss the issue. =\
As you can see, one of my spikes hit 489 and this is while I can stay connected. The only thing I notice right now is a bit of lag here and there. One of them that I posted earlier timed out. This is just not a stable connection. Medtac124 is also catching the spikes on the ping test.
EDIT: Nevermind. Worked for about 30 minutes, then got timed out.
That was suggested to me by the Cryptic support team also. It doesn't help the problem. =(
[as of 11:03 Sept 11 2012]
Well i am done tried everything to get this stupid game back up and NOTHING! again i am so happy to waste my money on a product that dosen't give me anything. Thank you so much TPW for not checking your work before you turn it in. This is like playing with one bullet in the chamber! Oohh I am going to DC now.....no wait now..... oohhh wait NOW it DCed me. Thank you.
So I called TWC... after 15 minutes they admitted they that they did have this ticket... but then they told me that they needed more than the few players that had already contacted them about it for them to launch a full investigation... I asked why more than a few people were necessary to look into an issue but he was just a desk clerk who liked to talk over me... He also told me that "I" should contact Cryptic and Cogent Co and tell them they should call TWC and open a dialog... bleh
moral of this? everyone who has this issue please call in!
(512)-485-5555
Ticket #: 11143479
Edit: So I searched for a known cryptic ticket without success and informed them of the issue and copied this body of text to go with it. They most likely already know but it really sucks that such a unique and focused group of TWC users are having such difficulty