Been having the same issues here for the past week, intermittently. I live in the Austin/Round Rock area in TX, and hey guess what? I'm on TWC.
Cogent's backbone gateway in DFW seems to be one likely culprit:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 7 ms 10.239.83.1
3 9 ms 9 ms 7 ms tge7-3.austtxr-er02.texas.rr.com [66.68.3.221]
4 19 ms 22 ms 31 ms tge0-8-0-1.austtxrdcsc-cr02.texas.rr.com [24.175
.42.222]
5 19 ms 24 ms 23 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 22 ms 23 ms 23 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 17 ms 17 ms 17 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 55 ms 220 ms 223 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
9 18 ms 20 ms 18 ms te0-2-0-4.ccr21.dfw01.atlas.cogentco.com [66.28.
4.173]
10 31 ms 31 ms 31 ms te0-2-0-1.ccr21.mci01.atlas.cogentco.com [154.54
.2.114]
11 44 ms 39 ms 40 ms te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
12 63 ms 64 ms 63 ms te0-3-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.198]
13 63 ms 63 ms 66 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 66 ms 71 ms 71 ms 38.111.40.114
15 65 ms 61 ms 65 ms 208.95.185.41
As does their other server, which has commonly popped up here:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 7 ms 7 ms 10.239.83.1
3 9 ms 9 ms 9 ms tge7-3.austtxr-er02.texas.rr.com [66.68.3.221]
4 22 ms 16 ms 22 ms tge0-8-0-1.austtxrdcsc-cr02.texas.rr.com [24.175
.42.222]
5 18 ms 22 ms 16 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 16 ms 23 ms 15 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 17 ms 19 ms 18 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 17 ms 17 ms 17 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
9 18 ms 17 ms 21 ms te0-2-0-4.ccr21.dfw01.atlas.cogentco.com [66.28.
4.173]
10 31 ms 31 ms 31 ms te0-2-0-1.ccr21.mci01.atlas.cogentco.com [154.54
.2.114]
11 40 ms 39 ms 39 ms te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
12 63 ms 63 ms 63 ms te0-3-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.198]
13 282 ms 215 ms 366 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 71 ms 71 ms 70 ms 38.111.40.114
15 62 ms 61 ms 61 ms 208.95.185.41
Haven't had a chance to call TWC yet, mainly because tonight's the first night my frustration level reached "Uninstall the game, burn the remains, eat the ashes, desecrate the graves, and salt the earth as you leave" levels.
did anyone look at the patch notes for tommarow? no mention of this issue even being adressed.... how lovely... ya know some days, your the bug and others your the windshield, today my fellow money spenders to china. I feel we are the bugs on the windshield.
back to ps3 and the epically other glitchy game i play Battlefield 3........woot.............what happened to good games? anyone remember goldeneye on nintendo 64? now those guys could make a good game......hopefully they are still alive and well. maybe they'll re emerge one day to rid us of all this nonsense
I don't know how you expect Cryptic to "patch" a problem that's being caused by Cogent's crappy hardware and/or routing metrics. That's sort of like me blaming my fridge for brown-outs caused by the power company's negligence.
You have a right to be mad, but direct that anger in the right direction: Cogent.
Been having the same issues here for the past week, intermittently. I live in the Austin/Round Rock area in TX, and hey guess what? I'm on TWC.
Cogent's backbone gateway in DFW seems to be one likely culprit:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
...
te9-4.ccr01.dfw03.atlas.cogentco.com is where the problem is occurring for those of us in Texas. Poll it for awhile and you'll see that it intermittently suffers packet loss, anywhere from 1-10%, along with a consistently high latency.
Got a reply from someone at Cogent Co about the emails I've been sending. Figured I'd share.
Hello,
After running some tests to the destination ip address 208.95.184.117 i did not see any issues in our route. The circuit which you mentioned as having problems is one of our core circuit and it does deprioritize icmp packets. There is no issue with the circuit and everything is normal. I also did some ping tests to check for packet drops and i did not see any.
Regards
Ben
Customer Support Engineer
Cogent Communications
T 877.726.4368, option 2
F 202.295.9061
E support@cogentco.com
Ben here claims that the high ping on that hop is normal. I explained to him that I've always been in the habit of running tracerts when I have some form of connection issue and this has never shown to me prior to this issue. He doesn't seem to want to look into the issue any further though... Perhaps I should just start bombarding them with calls till I get someone to look into it, since Cryptic doesn't seem to want to reply to us about it. =\
Why do I feel like I'm doing Cryptic tech support's job? Can I get paid for this, please?
Got a reply from someone at Cogent Co about the emails I've been sending. Figured I'd share.
Ben here claims that the high ping on that hop is normal. I explained to him that I've always been in the habit of running tracerts when I have some form of connection issue and this has never shown to me prior to this issue. He doesn't seem to want to look into the issue any further though... Perhaps I should just start bombarding them with calls till I get someone to look into it, since Cryptic doesn't seem to want to reply to us about it. =\
Why do I feel like I'm doing Cryptic tech support's job? Can I get paid for this, please?
Ben's "these are not the droids you're looking for" response doesn't surprise me. At this point I can only imagine that what money Cryptic is pulling in from this part of the country will soon be drying up, since no one in this region can actually connect to their servers.
After a week of making calls and posting on forums about this issue (without ever seeing a dev chime in), I think I'm done. If the problem isn't resolved before the next billing cycle, I'm cancelling. Why pay when I can't play?
Was hoping that the patch would resolve my issue, but a minute after logging on, "server not responding" to the point of unplayability.
I mentioned before that I have a feeling the 'Server Stability Issues' that they patched last round may have been part of the cause, I still don't know how. But since that's when the issue started for most of us, I still think they're somehow connected...
I'm not sure how likely it is but I suppose it's possible they started paying Cogent Co for a less stable server due to price. All the same, it would be nice to hear from Cryptic on the subject of if they will contact Cogent Co or not.
I did get a reply to my ticket to Cryptic, they asked me for a tracert. Here's my reply:
As requested I am including the tracerts below. The IP that you suggested to run a trace to was not able to be reached, so I have included my tracerts to the IP I'm connected to when I have a connection to the game as well. There are also tracerts in the thread that I've linked to you in a previous ticket. The below tracerts were performed one after another in close succession. As soon as one was finished I started the next one.
C:\Users\Draco>tracert 208.95.184.0
Tracing route to 208.95.184.0 over a maximum of 30 hops
1 8 ms 7 ms 15 ms 10.239.29.1
2 8 ms 7 ms 8 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 17 ms 15 ms 15 ms tge0-15-0-0.austtxa-cr02.texas.rr.com [66.68.2.25]
4 18 ms 15 ms 15 ms agg10.austtxa-cr01.texas.rr.com [24.175.41.204]
5 16 ms 15 ms 14 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 15 ms 15 ms 15 ms 107.14.17.136
7 16 ms 13 ms 13 ms ae-3-0.pr0.dfw10.tbone.rr.com [66.109.6.209]
8 113 ms 208 ms 206 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 17 ms 15 ms 15 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 25 ms 25 ms 25 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54.3.18]
11 47 ms 35 ms 35 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54.45.154]
12 58 ms 58 ms 59 ms te0-0-0-5.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
13 65 ms 210 ms 219 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 81 ms 89 ms 92 ms 38.111.40.114
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\Draco>tracert 208.95.184.117
Tracing route to 208.95.184.117 over a maximum of 30 hops
1 9 ms 7 ms 7 ms 10.239.29.1
2 8 ms 8 ms 9 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 13 ms 13 ms 11 ms tge8-1.austtxa-er02.texas.rr.com [24.175.41.53]
4 17 ms 16 ms 20 ms tge0-15-0-1.austtxa-cr01.texas.rr.com [24.175.41.58]
5 15 ms 22 ms 18 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 19 ms 22 ms 20 ms 107.14.17.136
7 12 ms 14 ms 14 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 21 ms 217 ms 221 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 18 ms 17 ms 19 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
10 23 ms 24 ms 23 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 36 ms 37 ms 36 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com [154.54.45.146]
12 59 ms 62 ms 58 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54.42.254]
13 58 ms 59 ms 59 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 60 ms 56 ms 69 ms 38.111.40.114
15 57 ms 57 ms 61 ms 208.95.184.117
Trace complete.
C:\Users\Draco>tracert 208.95.184.117
Tracing route to 208.95.184.117 over a maximum of 30 hops
1 7 ms 7 ms 8 ms 10.239.29.1
2 9 ms 7 ms 7 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 12 ms 12 ms 33 ms tge8-1.austtxa-er02.texas.rr.com [24.175.41.53]
4 15 ms 16 ms 15 ms tge0-15-0-1.austtxa-cr01.texas.rr.com [24.175.41.58]
5 15 ms 16 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 21 ms 15 ms 15 ms 107.14.17.136
7 13 ms 15 ms 13 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 149 ms 219 ms 222 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 16 ms 18 ms 17 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
10 26 ms 23 ms 25 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 35 ms 37 ms 37 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com [154.54.45.146]
12 59 ms 57 ms 59 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54.42.254]
13 159 ms 198 ms 371 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 59 ms 70 ms 56 ms 38.111.40.114
15 57 ms 57 ms 57 ms 208.95.184.117
Trace complete.
C:\Users\Draco>tracert 208.95.184.117
Tracing route to 208.95.184.117 over a maximum of 30 hops
1 7 ms 7 ms 6 ms 10.239.29.1
2 15 ms 11 ms 9 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 13 ms 12 ms 18 ms tge8-1.austtxa-er02.texas.rr.com [24.175.41.53]
4 20 ms 31 ms 15 ms tge0-15-0-1.austtxa-cr01.texas.rr.com [24.175.41.58]
5 17 ms 15 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 16 ms 23 ms 24 ms 107.14.17.136
7 13 ms 15 ms 13 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 264 ms 219 ms 230 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 15 ms 19 ms 25 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
10 24 ms 23 ms 23 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 35 ms 35 ms 33 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com [154.54.45.146]
12 59 ms 58 ms 59 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54.42.254]
13 60 ms 60 ms 57 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 61 ms 56 ms 67 ms 38.111.40.114
15 56 ms 61 ms 55 ms 208.95.184.117
Trace complete.
C:\Users\Draco>tracert 208.95.184.117
Tracing route to 208.95.184.117 over a maximum of 30 hops
1 10 ms 7 ms 7 ms 10.239.29.1
2 8 ms 8 ms 7 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 11 ms 13 ms 13 ms tge8-1.austtxa-er02.texas.rr.com [24.175.41.53]
4 15 ms 14 ms 15 ms tge0-15-0-1.austtxa-cr01.texas.rr.com [24.175.41.58]
5 14 ms 15 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 23 ms 15 ms 23 ms 107.14.17.136
7 18 ms 13 ms 15 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 15 ms 16 ms 18 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 18 ms 15 ms 15 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
10 22 ms 27 ms 24 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 36 ms 36 ms 34 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com [154.54.45.146]
12 58 ms 60 ms 59 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54.42.254]
13 67 ms 58 ms 57 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 64 ms 58 ms 67 ms 38.111.40.114
15 56 ms 56 ms 57 ms 208.95.184.117
Trace complete.
C:\Users\Draco>tracert 208.95.184.117
Tracing route to 208.95.184.117 over a maximum of 30 hops
1 21 ms 7 ms 7 ms 10.239.29.1
2 7 ms 9 ms 7 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 12 ms 13 ms 13 ms tge8-1.austtxa-er02.texas.rr.com [24.175.41.53]
4 18 ms 16 ms 14 ms tge0-15-0-1.austtxa-cr01.texas.rr.com [24.175.41.58]
5 16 ms 15 ms 16 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 18 ms 14 ms 15 ms 107.14.17.136
7 13 ms 13 ms 13 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 128 ms 214 ms 211 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 17 ms 21 ms 17 ms te0-3-0-4.ccr21.dfw01.atlas.cogentco.com [154.54.82.17]
10 23 ms 24 ms 25 ms te0-2-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.185]
11 35 ms 35 ms 38 ms te0-5-0-4.ccr21.ord01.atlas.cogentco.com [154.54.45.146]
12 59 ms 57 ms 61 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54.42.254]
13 57 ms 59 ms 59 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 66 ms 57 ms 67 ms 38.111.40.114
15 56 ms 69 ms 56 ms 208.95.184.117
Everything was going good, until about 45 min ago. Now, it's back to " Server not Responding". I'm currently in combat, and the ship I was attacking was stuck at 9% for 2 minutes. It also wasn't moving, and neither was I.
I'm also not able to zone into different systems, without the possibility of not being able to load. I've had to X out of the game several times, in order to restart it and try again.
I don't think PWE gives a TRIBBLE. Btw, this really really REALLY needs to be dealt with, it's starting to really TRIBBLE not only myself off but others as well.
It is said the best weapon is one that is never fired. I disagree. The best weapon is one you only have to fire... once.
Been fighting this issue too, living in Austin and using TWC. Unfortunate that Cryptic won't comment on this issue. I guess their Perfect World masters keep them well muzzled.
I'll give them till next Friday before I cancel my account.
yeah was hoping that the patch would have some hidden tability "goodies" myself. sorry to look here first and discover there wasn't a true fix. I'm pretty disapointed myself in the fact that theres not a fix or a comment by cryptic or pwe......
Got a reply from someone at Cogent Co about the emails I've been sending. Figured I'd share.
Hello,
After running some tests to the destination ip address 208.95.184.117 i did not see any issues in our route. The circuit which you mentioned as having problems is one of our core circuit and it does deprioritize icmp packets. There is no issue with the circuit and everything is normal. I also did some ping tests to check for packet drops and i did not see any.
Regards
Ben
Customer Support Engineer
Cogent Communications
T 877.726.4368, option 2
F 202.295.9061
E support@cogentco.com
Ben here claims that the high ping on that hop is normal. I explained to him that I've always been in the habit of running tracerts when I have some form of connection issue and this has never shown to me prior to this issue. He doesn't seem to want to look into the issue any further though... Perhaps I should just start bombarding them with calls till I get someone to look into it, since Cryptic doesn't seem to want to reply to us about it. =\
Why do I feel like I'm doing Cryptic tech support's job? Can I get paid for this, please?
If you can get ahold of Cogent again, see if they are willing to look at TCP packets with certain ranges of IP addresses and port numbers; ICMP packets may not be telling the whole story.
Cryptic servers have IP addresses that begin with 208.95.184 and use port numbers between 7000 and 7999. This can be determined by running netstat while the game is running. For example:
C:\Windows\system32>netstat
Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:10501 Laptop-2008:54896 ESTABLISHED
TCP 127.0.0.1:10502 Laptop-2008:54897 ESTABLISHED
TCP 127.0.0.1:54896 Laptop-2008:10501 ESTABLISHED
TCP 127.0.0.1:54897 Laptop-2008:10502 ESTABLISHED
TCP 192.168.1.100:55005 208.95.184.43:7412 ESTABLISHED
TCP 192.168.1.100:55009 208.95.184.213:7046 ESTABLISHED
In the above example, 208.95.184.43 is the chat server, and 208.95.184.213 is the "game" server. This can be determined by looking at the log file
(Your path may be different depending on where you installed the game.)
The "game" server seems to change each time you connect; the chat server stays the same. The port numbers also change, but they seem to range from 7000 to 7999.
Also, since the problem is sporadic, they may have to log packets over the course of a day.
If you can get ahold of Cogent again, see if they are willing to look at TCP packets with certain ranges of IP addresses and port numbers; ICMP packets may not be telling the whole story.
Also, since the problem is sporadic, they may have to log packets over the course of a day.
I actually just got off the phone w/ Cogent Co again and the agent mentioned that they just finished doing some work on the connections being routed through where we'd been seeing the problem. (A few hours ago, he specified.) So I hope that these issues have been addressed at this time. I did also ask about the sometimes seen high ping on the last cogentco hop on our traces and he mentioned that they have not seen enough issues with that to cause concern.
So from this post onward I hope we no longer have this issue. But please do keep en eye out over the next few days. Any new tracerts showing issues will be helpful if I need to contact them again.
On a side note: I had to laugh at Ben's lack of interest to help when I reported the issue to him. If he told me just yesterday that nothing was wrong then there would not have been any reason for them to work on the trouble point... Good job, Ben... Good job.
Tracing route to 208.95.184.222 over a maximum of 30 hops
1 7 ms 8 ms 9 ms 10.239.29.1
2 8 ms 7 ms 7 ms tge7-1.austtxa-er01.texas.rr.com [66.68.2.162]
3 15 ms 16 ms 14 ms tge0-15-0-1.austtxa-cr02.texas.rr.com [24.175.41.2]
4 16 ms 15 ms 15 ms agg10.austtxa-cr01.texas.rr.com [24.175.41.204]
5 15 ms 15 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 16 ms 15 ms 15 ms 107.14.17.136
7 13 ms 16 ms 13 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 301 ms 212 ms 210 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.49]
9 17 ms 17 ms 15 ms te0-0-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
10 27 ms 26 ms 28 ms te0-2-0-6.mpd21.mci01.atlas.cogentco.com [154.54.46.181]
11 34 ms 35 ms 35 ms te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54.30.169]
12 58 ms 57 ms 57 ms te0-3-0-6.ccr21.bos01.atlas.cogentco.com [154.54.43.182]
13 57 ms 58 ms 59 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 63 ms 56 ms 55 ms 38.111.40.114
15 57 ms 58 ms 59 ms 208.95.184.222
ok so just had a patch and figure Cryptic needs someone other than Cogent or whatever to go through. Cryptic may not be responsible for the timeouts but but they will be held accountable to those who have paid for a game they cant play. Its still a business after all and just cuz the doctor doesnt have the right medicine its not up to the patient to try and find it.
while I haven't seen any " server not responding' messages, this morning, the lag is unbearable. I have moments where I can move normally, but most of the time, it's very jerky and laggy.
Edit: I'm now getting the " server not responding" messages. I can no longer manuever, in my ship, or even accept missions or warp.
Well, you atleast get in the game, ppl. I haven't saved my PC in Account Verification for security reasons so I allways must enter the one time code from email that is send to my email address. But now I do not receive any email with that code anymore for almost 4 hours! I don't even get email with code to get to that security web where I can disable Account Guard!
It all started after last patch. After the game was patched, I had to login 4 times to get one email with code. Now I am trying to get email by reloging. But as said above, amost 4 hours since first try and still no email.
And yes, I looked in spam folder, it is still empty. I also checked if my email address got changed with negative find. These emails never went to spam folder anyway. Also send a ticket to support via web browser.
I Just upgraded my subscription a week ago and now I can't seem to play more than a few hours every other day if that. :mad: So much for the rush work to get a Thorian Ship...
Cryptic, please help.
...and I'd like to see Romulan Warbirds as possible purchasable ships in future
Śledzenie trasy do patchserver.crypticstudios.com [208.95.185.41]
z maksymalną liczbą 30 przeskok?w:
1 1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 13 ms 10.204.0.1
3 7 ms 7 ms 8 ms 172.17.149.21
4 11 ms 12 ms 14 ms 172.17.28.10
5 32 ms 26 ms 30 ms te-4-1.car2.Warsaw3.Level3.net [213.242.118.129]
6 50 ms 40 ms 41 ms ae-11-11.car1.Warsaw3.Level3.net [4.69.148.153]
7 33 ms 28 ms 26 ms ae-13-13.ebr2.Berlin1.Level3.net [4.69.148.150]
8 46 ms 35 ms 40 ms 4.69.200.165
9 39 ms 52 ms 45 ms ae-23-23.ebr1.Dusseldorf1.Level3.net [4.69.143.189]
10 39 ms 38 ms 39 ms ae-45-45.ebr3.Frankfurt1.Level3.net [4.69.143.166]
11 40 ms 42 ms 45 ms ae-83-83.csw3.Frankfurt1.Level3.net [4.69.163.10]
12 41 ms 39 ms 39 ms ae-3-80.edge5.Frankfurt1.Level3.net [4.69.154.137]
13 52 ms 43 ms 45 ms te0-1-0-3.ccr21.fra06.atlas.cogentco.com [130.117.15.129]
14 44 ms 43 ms 46 ms te0-1-0-5.mpd22.fra03.atlas.cogentco.com [130.117.48.102]
15 47 ms 52 ms 48 ms te0-0-0-2.mpd22.ams03.atlas.cogentco.com [130.117.0.133]
16 55 ms 59 ms 55 ms te0-0-0-2.ccr22.lpl01.atlas.cogentco.com [154.54.37.102]
17 137 ms 134 ms 125 ms te0-5-0-3.ccr22.bos01.atlas.cogentco.com [154.54.44.189]
18 124 ms 125 ms 124 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
19 * * * Upłynął limit czasu żądania.
20 * * * Upłynął limit czasu żądania.
21 * * * Upłynął limit czasu żądania.
22 * * * Upłynął limit czasu żądania.
23 * * * Upłynął limit czasu żądania.
24 * * * Upłynął limit czasu żądania.
25 * * * Upłynął limit czasu żądania.
26 * * * Upłynął limit czasu żądania.
27 * * * Upłynął limit czasu żądania.
28 * * * Upłynął limit czasu żądania.
29 * * * Upłynął limit czasu żądania.
30 * * * Upłynął limit czasu żądania.
Comments
here flood this forum with complaints. this is suppose to be perfect world new tech forum.
Cogent's backbone gateway in DFW seems to be one likely culprit:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 7 ms 10.239.83.1
3 9 ms 9 ms 7 ms tge7-3.austtxr-er02.texas.rr.com [66.68.3.221]
4 19 ms 22 ms 31 ms tge0-8-0-1.austtxrdcsc-cr02.texas.rr.com [24.175
.42.222]
5 19 ms 24 ms 23 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 22 ms 23 ms 23 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 17 ms 17 ms 17 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 55 ms 220 ms 223 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
9 18 ms 20 ms 18 ms te0-2-0-4.ccr21.dfw01.atlas.cogentco.com [66.28.
4.173]
10 31 ms 31 ms 31 ms te0-2-0-1.ccr21.mci01.atlas.cogentco.com [154.54
.2.114]
11 44 ms 39 ms 40 ms te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
12 63 ms 64 ms 63 ms te0-3-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.198]
13 63 ms 63 ms 66 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 66 ms 71 ms 71 ms 38.111.40.114
15 65 ms 61 ms 65 ms 208.95.185.41
As does their other server, which has commonly popped up here:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 7 ms 7 ms 10.239.83.1
3 9 ms 9 ms 9 ms tge7-3.austtxr-er02.texas.rr.com [66.68.3.221]
4 22 ms 16 ms 22 ms tge0-8-0-1.austtxrdcsc-cr02.texas.rr.com [24.175
.42.222]
5 18 ms 22 ms 16 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
6 16 ms 23 ms 15 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 17 ms 19 ms 18 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
8 17 ms 17 ms 17 ms te9-4.ccr01.dfw03.atlas.cogentco.com [154.54.11.
49]
9 18 ms 17 ms 21 ms te0-2-0-4.ccr21.dfw01.atlas.cogentco.com [66.28.
4.173]
10 31 ms 31 ms 31 ms te0-2-0-1.ccr21.mci01.atlas.cogentco.com [154.54
.2.114]
11 40 ms 39 ms 39 ms te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
12 63 ms 63 ms 63 ms te0-3-0-6.ccr22.bos01.atlas.cogentco.com [154.54
.43.198]
13 282 ms 215 ms 366 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 71 ms 71 ms 70 ms 38.111.40.114
15 62 ms 61 ms 61 ms 208.95.185.41
Haven't had a chance to call TWC yet, mainly because tonight's the first night my frustration level reached "Uninstall the game, burn the remains, eat the ashes, desecrate the graves, and salt the earth as you leave" levels.
I don't know how you expect Cryptic to "patch" a problem that's being caused by Cogent's crappy hardware and/or routing metrics. That's sort of like me blaming my fridge for brown-outs caused by the power company's negligence.
You have a right to be mad, but direct that anger in the right direction: Cogent.
te9-4.ccr01.dfw03.atlas.cogentco.com is where the problem is occurring for those of us in Texas. Poll it for awhile and you'll see that it intermittently suffers packet loss, anywhere from 1-10%, along with a consistently high latency.
Dunno what good it will do, but as you recommended I posted this over there:
http://techsupport.perfectworld.com/showthread.php?t=4181
Ben here claims that the high ping on that hop is normal. I explained to him that I've always been in the habit of running tracerts when I have some form of connection issue and this has never shown to me prior to this issue. He doesn't seem to want to look into the issue any further though... Perhaps I should just start bombarding them with calls till I get someone to look into it, since Cryptic doesn't seem to want to reply to us about it. =\
Why do I feel like I'm doing Cryptic tech support's job? Can I get paid for this, please?
Ben's "these are not the droids you're looking for" response doesn't surprise me. At this point I can only imagine that what money Cryptic is pulling in from this part of the country will soon be drying up, since no one in this region can actually connect to their servers.
After a week of making calls and posting on forums about this issue (without ever seeing a dev chime in), I think I'm done. If the problem isn't resolved before the next billing cycle, I'm cancelling. Why pay when I can't play?
I also get disco everytime i switch zones and get no response from the server. No luck with playing the game for the past 2 weeks which sucks!
:mad: I hope today's maintenance helps.
I mentioned before that I have a feeling the 'Server Stability Issues' that they patched last round may have been part of the cause, I still don't know how. But since that's when the issue started for most of us, I still think they're somehow connected...
I'm not sure how likely it is but I suppose it's possible they started paying Cogent Co for a less stable server due to price. All the same, it would be nice to hear from Cryptic on the subject of if they will contact Cogent Co or not.
I did get a reply to my ticket to Cryptic, they asked me for a tracert. Here's my reply:
I'm also not able to zone into different systems, without the possibility of not being able to load. I've had to X out of the game several times, in order to restart it and try again.
I'll give them till next Friday before I cancel my account.
If you can get ahold of Cogent again, see if they are willing to look at TCP packets with certain ranges of IP addresses and port numbers; ICMP packets may not be telling the whole story.
Cryptic servers have IP addresses that begin with 208.95.184 and use port numbers between 7000 and 7999. This can be determined by running netstat while the game is running. For example:
In the above example, 208.95.184.43 is the chat server, and 208.95.184.213 is the "game" server. This can be determined by looking at the log file
C:\Users\Public\Games\Cryptic Studios\Star Trek Online\Live\logs\GameClient\Clientservercomm.Log
(Your path may be different depending on where you installed the game.)
The "game" server seems to change each time you connect; the chat server stays the same. The port numbers also change, but they seem to range from 7000 to 7999.
Also, since the problem is sporadic, they may have to log packets over the course of a day.
My other online games work fine except this one.
I log in and get the Server not Responding and 1 to 4 min later I get disconnected
My location is Southern California and use TWC
I actually just got off the phone w/ Cogent Co again and the agent mentioned that they just finished doing some work on the connections being routed through where we'd been seeing the problem. (A few hours ago, he specified.) So I hope that these issues have been addressed at this time. I did also ask about the sometimes seen high ping on the last cogentco hop on our traces and he mentioned that they have not seen enough issues with that to cause concern.
So from this post onward I hope we no longer have this issue. But please do keep en eye out over the next few days. Any new tracerts showing issues will be helpful if I need to contact them again.
On a side note: I had to laugh at Ben's lack of interest to help when I reported the issue to him. If he told me just yesterday that nothing was wrong then there would not have been any reason for them to work on the trouble point... Good job, Ben... Good job.
I don't know if it will help, but along with powercycling your router, did you try flushing your dns cache? (ipconfig /flushdns)
Again, NO idea if it would actually do any good at all...but it can't hurt.
Edit: I'm now getting the " server not responding" messages. I can no longer manuever, in my ship, or even accept missions or warp.
Cryptic please fix your game!
26th Fleet
Task Force Avalon - CO USS Intrepid
[SIGPIC][/SIGPIC]
It all started after last patch. After the game was patched, I had to login 4 times to get one email with code. Now I am trying to get email by reloging. But as said above, amost 4 hours since first try and still no email.
And yes, I looked in spam folder, it is still empty. I also checked if my email address got changed with negative find. These emails never went to spam folder anyway. Also send a ticket to support via web browser.
Cryptic, please help.
...and I'd like to see Romulan Warbirds as possible purchasable ships in future
ATT U-verse is offering a pretty sweet deal to switch over to them, and I'm going to call them today.
Couldn't possibly be worse, that's for sure.
post your complaints here. there is a tech guy giving boilerplate responses over there, but at least someone is looking at the tech issues.