Well considering people are only having troubles with cryptic and nothing else... evidence kinda proves otherwise. I logged in just fine til about 8 PM my time then I can't get the patcher to load half the time with STO or Champions. I can play everything else that isn't PWE related just fine.
Forum mods feel free to relocate this thread if there actually exists a more appropriate location, please.
The last nearly 24 hours now the game has not even been playable for me.
Either not even being able to connect to the login servers or once connected not being able to enter the game once selecting a character. Then if I do get past that but dare to play the game at all and zone or instance change it crashes.
I first approached this problem as something on my side.
I did every thing I could think of:
rebooted my computer
defraged my harddrive
scoured my computer for viruses
uninstalled and reinstalled (with a fresh download) of the game
reset my router
I know others have been having issues, have heard their complaints but I didn't think it was really this bad.
It's been happening here since mid-day, California time. The fault is with a Cogentco node that is flaking out. It's an intermittent fault, so it doesn't always show up in the traces, but it is dropping packets and causing the connections to time out.
Target Name: patchserver.crypticstudios.com
IP: 208.95.185.41
Date/Time: 3/13/2013 4:14:35 AM
1 1 ms 0 ms 0 ms 1 ms homeportal [192.168.1.254]
2 56 ms 27 ms 24 ms 27 ms 108-204-64-2.lightspeed.bkfdca.sbcglobal.net [108.204.64.2]
3 N/A N/A N/A 22 ms [99.160.71.30]
4 25 ms 26 ms 24 ms 25 ms [12.83.69.137]
5 30 ms 78 ms 31 ms 31 ms ggr6.wswdc.ip.att.net [12.122.86.89]
6 33 ms 32 ms 32 ms 32 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45]
7 33 ms 32 ms 32 ms 32 ms te0-3-0-3.ccr21.sjc01.atlas.cogentco.com [154.54.6.81]
8 34 ms 34 ms 34 ms 34 ms te0-3-0-5.mpd21.sfo01.atlas.cogentco.com [154.54.86.185]
9 70 ms 70 ms 71 ms 71 ms te0-3-0-3.mpd21.mci01.atlas.cogentco.com [154.54.0.101]
10 79 ms 79 ms 79 ms 78 ms te0-7-0-33.mpd21.ord01.atlas.cogentco.com [154.54.2.234]
11 N/A N/A N/A 103 ms te0-7-0-2.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
12 104 ms 105 ms 103 ms 103 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 116 ms 108 ms 115 ms 111 ms [38.111.40.114]
14 102 ms 101 ms 102 ms 127 ms [208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 101ms, Maximum = 127ms, Average = 108ms
Target Name: patchserver.crypticstudios.com
IP: 208.95.185.41
Date/Time: 3/13/2013 4:16:05 AM to 3/13/2013 4:17:12 AM
1 0 ms 0 ms N/A N/A 0 ms N/A N/A 0 ms 0 ms 0 ms homeportal [192.168.1.254]
2 23 ms 23 ms N/A N/A 24 ms N/A N/A 24 ms 31 ms 49 ms 108-204-64-2.lightspeed.bkfdca.sbcglobal.net [108.204.64.2]
3 * 23 ms N/A N/A * N/A N/A * * * [99.160.71.30]
4 26 ms 26 ms N/A N/A 26 ms N/A N/A 23 ms 25 ms 24 ms [12.83.69.137]
5 29 ms 30 ms N/A N/A 30 ms N/A N/A 30 ms 30 ms 81 ms ggr6.wswdc.ip.att.net [12.122.86.89]
6 32 ms 32 ms N/A N/A 33 ms N/A N/A 33 ms 32 ms 32 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45]
7 32 ms 32 ms N/A N/A 32 ms N/A N/A 32 ms 32 ms 32 ms te0-3-0-3.ccr21.sjc01.atlas.cogentco.com [154.54.6.81]
8 34 ms 34 ms N/A N/A 35 ms N/A N/A 33 ms 34 ms 32 ms te0-3-0-5.mpd21.sfo01.atlas.cogentco.com [154.54.86.185]
9 70 ms 70 ms N/A N/A 70 ms N/A N/A 70 ms 70 ms 71 ms te0-3-0-3.mpd21.mci01.atlas.cogentco.com [154.54.0.101]
10 77 ms 79 ms N/A N/A 79 ms N/A N/A 78 ms 79 ms 78 ms te0-7-0-33.mpd21.ord01.atlas.cogentco.com [154.54.2.234]
11 104 ms * N/A N/A N/A N/A N/A N/A N/A 103 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 104 ms 129 ms N/A N/A 103 ms N/A N/A 105 ms N/A 103 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 108 ms 103 ms N/A N/A 113 ms N/A N/A 102 ms 109 ms 104 ms [38.111.40.114]
14 103 ms 103 ms N/A N/A 102 ms N/A N/A 103 ms 102 ms 102 ms [208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 102ms, Maximum = 103ms, Average = 102ms
It's going on 13hrs and still every time I try to move between maps= server not responding. What comes next is my favorite ordeal= Server has timed out. Posting the traces is pointless, all online games never ever respond to anything that could be considered lag or connection issue. the only response you will recive is that its your end or sorry we cant help you. Even though the server is almost void of players, they will go down still claiming everything is cool lol. Oh I posted the traces 12hrs ago to 3 sites starting with my i.s.p, Congentco, and PWE.
On a funny note, it was kind a cool to run around the space station with no one there. I guess beaming down is just as nasty as beaming out lol= whooopsy server timeout. There should be a new ship in the Zen market called " The U.S.S Server Timeout- Super duper Battle ship. <-- beam aboard this and have a timeout of your life! lol
Just adding myself to the list of those apparently being affected. I've been having a lot of trouble logging in and transferring between maps for the past two days. It started as just a few disconnects, but it's gotten progressively worse.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms homeportal [192.168.1.254]
2 40 ms 27 ms 29 ms 99-5-TRIBBLE-TRIBBLE.lightspeed.gnvlsc.sbcglobal.net [99.5.TRIBBLE.TRIBBLE]
3 36 ms 30 ms 28 ms 99.168.141.36
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 27 ms 28 ms 72.157.40.144
7 36 ms 39 ms 37 ms 12.81.44.62
8 38 ms 38 ms 38 ms 12.81.104.178
9 53 ms 37 ms 38 ms 12.81.34.3
10 48 ms 49 ms 39 ms ixc01asm-pos-3-3.bellsouth.net [65.83.237.7]
11 44 ms 43 ms 38 ms 12.81.46.3
12 40 ms 39 ms 39 ms 12.81.104.110
13 36 ms 37 ms 38 ms 12.81.56.15
14 40 ms 43 ms 40 ms 74.175.192.54
15 50 ms 51 ms 51 ms cr2.rlgnc.ip.att.net [12.123.152.110]
16 52 ms 51 ms 52 ms cr1.wswdc.ip.att.net [12.122.3.170]
17 49 ms 50 ms 49 ms gar13.n54ny.ip.att.net [12.122.81.245]
18 50 ms 49 ms 50 ms 192.205.37.106
19 51 ms 50 ms 51 ms te0-5-0-5.mpd22.dca01.atlas.cogentco.com [154.54.2.61]
20 55 ms 56 ms 56 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54.3.234]
21 62 ms 62 ms 61 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.22]
22 * * * Request timed out.
23 67 ms 71 ms 71 ms 38.111.40.114
24 63 ms 62 ms 62 ms 208.95.185.41
There's potentially tens of thousands of miles between you and the servers.
It's possible that any trouble you're having is somewhere in those tubes, and has nothing to do with you or the servers.
Might be indeed the problem.
Sometimes related to your general location and some problem the internet service providers (ISPs) need to sort out.
What countries are you folks from?
I've been playing STO since it first came out, and i've never had any problems with the server until about the last month or so. "Server Not Responding" all the time. My screen barely has time to load up before it pops up. I've been stuck at DS9 for over 2 weeks. I'm a paying customer. I feel like i'm waisting my money now, paying for game that i can't even play.
It's pretty easy for me to say it's not my internal issue when EvE runs flawlessly, MWO runs flawlessly (as flawlessly as it ever does), SWGEmu's test servers are happy with me, large (1/2 gig) graphics files go happily to and from the ftp server I administer for the school I work at, and yet there are issues here.
Given all of the above I don't need to back up my claim with a tracert or their nettest
I've gone so far as to DMZ my box for testing purposes and still nothing. nettest is now failing across multiple ports, the launcher went into patch mode at a speed that can only be charitably described as slow...after taking 20+ seconds to even hook.
After closing the launcher in disgust I fired up EvE, and as expected the patch that was waiting for me came down @ 3+mbit/sec.
It's pretty easy for me to say it's not my internal issue when EvE runs flawlessly, MWO runs flawlessly (as flawlessly as it ever does), SWGEmu's test servers are happy with me, large (1/2 gig) graphics files go happily to and from the ftp server I administer for the school I work at, and yet there are issues here.
Given all of the above I don't need to back up my claim with a tracert or their nettest....
I'm not talking about your connection to the Internet, I'm talking about your connection THROUGH THE INTERNET to the STO Servers... You have yet to realize that unless the servers of your other MMOs are located in the same physical location as the STO servers, the fact that you can connect to them are irrelevant to your STO connection issue... And without the Net Test and Trace Route results, your claiming that you have a flawless connection through the Internet to the STO servers with no proof at all to back up this claim...
From my side I can confirm that this is not a individual problem of some rare users. Since about a week I get constant disconnects. Sometimes I can play for half an hour, then during map transition I got kicked after a few seconds ingame.
Either there is a common internet problem all over the world, or that problem is cryptics ISP, or it is a server problem. On my PC all other games and sites are functioning normally.
ya pretty much everything i've researched the last two days (having same prob obviously) indicate this issues appears to be affecting all PWE games and even WOW, plus a few other games here and there.
Its appears to be an issue with AT&T and COX (that i've been able to determine) trying to communicate with the game servers through the Atlas Cogentco Boston and/ore Chicago hubs.
Which is bad, since pretty much a good chunk of the US and even parts of the EU connect through there...or so goes my understanding
Not sure that any of the above helps...but imho...seeing WOW makes me feel a bit better lol
*Edit* This has hit these games before but the above info I've noted has been happening again these last few days
ya pretty much everything i've researched the last two days (having same prob obviously) indicate this issues appears to be affecting all PWE games and even WOW, plus a few other games here and there.
Knowing that the problem exist is the first step towards finding a solution... The thing to keep in mind is that compared to the likes Neflix and Google, Cryptic/PWE is a very small player in the Internet, and major ISP are not going to give well being of Cryptic/PWE connections a priority. This is why the postings of the 'Net Test' and 'Trace Route' results in the PWE Tech Support forum is so important. So that Cryptic/PWE will learn where the Internet connections issues are, (as the Backbone ISPs won't volunteer this info...) and kick their Internet gateway providers with this data, to try to get the problems resolved. Just complaining about the issue without providing the diagnostic data isn't going to get the job done...
Knowing that the problem exist is the first step towards finding a solution... The thing to keep in mind is that compared to the likes Neflix and Google, Cryptic/PWE is a very small player in the Internet, and major ISP are not going to give well being of Cryptic/PWE connections a priority. This is why the postings of the 'Net Test' and 'Trace Route' results in the PWE Tech Support forum is so important. So that Cryptic/PWE will learn where the Internet connections issues are, (as the Backbone ISPs won't volunteer this info...) and kick their Internet gateway providers with this data, to try to get the problems resolved. Just complaining about the issue without providing the diagnostic data isn't going to get the job done...
"It's their job to sort this out" won't phase you in the least, will it?
I spent the better part of two decades in IT management at one of the largest retailers in the US. I project-managed the deployment of the 250+ pizza boxes, storage, database, and middleware servers that run their e-commerce site. I also ran the desktop services team, and help desk for it, that serviced the corporate offices.
If customers were calling the help desk to complain that they could not shop with us because the site was inaccessible, or kept kicking them off, or took 30 seconds to load a page on our site while it took 1 second on JC Penney's site and the help desk operator's response was continually "So hey, you need to run tracert back to our servers and email us the results...oh and run this program to test the port performance and email us that as well...just complaining about it isn't going to do any good" would result in a couple of things:
1. The customers would stop shopping there and shop somewhere else.
2. The help desk operator would be fired.
They own the relaitionship with their ISPs, I don't. If they can't be bothered to expend the trivial effort (And it is trivial. Just using dslReports I can fire up smoke and qos tests against my boxes from multiple sites around the country in less than ten minutes) required to generate remote connections against their systems to troubleshoot their problems why should I be bothered to pay them?
"It's their job to sort this out" won't phase you in the least, will it?...
Um really ??? If you ever bothered to read the 'Terms of Service' agreement for STO...
18. Interruption of Service
(a) PWE reserves the right to interrupt the Service from time to time on a regularly scheduled basis or otherwise with or without prior notice in order to perform maintenance. You agree that PWE will not be liable for any interruption of the Service, delay or failure to perform resulting from any causes whatsoever.
(b) You acknowledge that the Service may be interrupted for reasons beyond the control of PWE, and PWE cannot guarantee that you will be able to access the Services or your Account whenever you may wish to do so. PWE shall not be liable for any interruption of the Services, delay or failure to perform resulting from any causes whatsoever.
(c) PWE has the right at any time with or without reason to change and/or eliminate any aspect(s) of the Services as it sees fit in its sole discretion.
(d) PWE is not be obligated to refund all or any portion of any Account fee (if any), by reason of any interruption of the Services by reason of any of the circumstances described in paragraph (a) or (b).
And by continuing to play STO is taken as defacto agreement to the TOS statement...
Also, there are some differences in functional requirements between a simple HTTP connection vs. a real time MMRPG Client that you should be aware of. Which one do you think requires a higher quality connection...
And by continuing to play STO is taken as defacto agreement to the TOS statement...
Also, there are some differences in functional requirements between a simple HTTP connection vs. a real time MMRPG Client that you should be aware of. Which one do you think requires a higher quality connection...
Do you get paid for this drivel?
The fact that there is a ToS that says these things can go wrong without you having a recourse doesn't make fixing them your problem. Logic much? I'll go slow: It is still their problem. They are the service provider. That they can not be held legally liable for damages in no way makes fixing their issues my responsibility. Their relationship with their network services providers may be my gaming problem, but it's not my issue to resolve.
If you think today's e-commerce sites, with advanced interactive tools, shopping carts, realtime streams to financial services, multi-media, real time video chats in some cases, and real time database calls are simple http it's not me who needs an education here. Then again, you don't want to know. You are a one-trick pony and I'll be darned if I can figure out why you are in a forum where users are supposed to be helping each other...when you are not doing any such thing. At some point, what you are doing amounts to trolling, since you keep repeating the same thing over and over again and not providing any assistance to anyone regarding this problem.
Solid realtime mmo communications has been alive and well since the late 90s, with phone lines and modems. Don't hold yourself out as an expert on this unless you really want to get into it.
Well, everything was going fine this morning. I was even downloading a game in the background and had no connection issues. Then everything just DROPPED in the last hour, and now I'm stuck at "Server Not Responding."
Here's a tracert I ran last night while I was plagued with lag.
1 92 ms 1 ms <1 ms 192.168.15.1
2 * * * Request timed out.
3 9 ms 10 ms 9 ms tge7-1.snantx3600-er02.texas.rr.com [24.28.133.54]
4 18 ms 23 ms 24 ms tge0-9-0-2.snantx3000-tr02.texas.rr.com [24.175.33.172]
5 40 ms 23 ms 24 ms agg23.snantx6000-cr01.texas.rr.com [24.175.32.184]
6 28 ms 24 ms 23 ms agg2.dllatxl3-cr01.texas.rr.com [24.175.32.146]
7 26 ms 23 ms 23 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
8 17 ms 25 ms 18 ms 107.14.17.232
9 53 ms 65 ms 59 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
10 66 ms 76 ms 53 ms te0-2-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.6.93]
11 71 ms 70 ms 69 ms te0-3-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.201]
12 41 ms 43 ms 47 ms te0-1-0-2.ccr21.ord01.atlas.cogentco.com [154.54.25.82]
13 68 ms 66 ms 66 ms te0-3-0-1.ccr21.bos01.atlas.cogentco.com [154.54.42.254]
14 65 ms 204 ms 223 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
15 70 ms 72 ms 72 ms 38.111.40.114
16 67 ms 68 ms 70 ms 208.95.185.41
te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134] seems to be a common culprit from what I've seen on other tracerts. I'll run another when I finish my download.
Well I found a sure-fire way to get my post count up - just post in every outage/problem threads these words: "Post your traceroute and nettest results here...blah blah".
Well I found a sure-fire way to get my post count up - just post in every outage/problem threads these words: "Post your traceroute and nettest results here...blah blah".
Or you could save time and just post the blah blah part.
...Then again, you don't want to know. You are a one-trick pony and I'll be darned if I can figure out why you are in a forum where users are supposed to be helping each other...when you are not doing any such thing. At some point, what you are doing amounts to trolling, since you keep repeating the same thing over and over again and not providing any assistance to anyone regarding this problem..
I wouldn't call being able to work on TCP/IP implementations at the stack level, or dealing with the issues of SSL and PKI deployment a one trick pony... If you don't want to assist Cryptic/PWE in solving your connection, thats fine. Its your decision and your connection...
Well, everything was going fine this morning. I was even downloading a game in the background and had no connection issues. Then everything just DROPPED in the last hour, and now I'm stuck at "Server Not Responding."
Here's a tracert I ran last night while I was plagued with lag.
1 92 ms 1 ms <1 ms 192.168.15.1
2 * * * Request timed out.
3 9 ms 10 ms 9 ms tge7-1.snantx3600-er02.texas.rr.com [24.28.133.54]
4 18 ms 23 ms 24 ms tge0-9-0-2.snantx3000-tr02.texas.rr.com [24.175.33.172]
5 40 ms 23 ms 24 ms agg23.snantx6000-cr01.texas.rr.com [24.175.32.184]
6 28 ms 24 ms 23 ms agg2.dllatxl3-cr01.texas.rr.com [24.175.32.146]
7 26 ms 23 ms 23 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
8 17 ms 25 ms 18 ms 107.14.17.232
9 53 ms 65 ms 59 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
10 66 ms 76 ms 53 ms te0-2-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.6.93]
11 71 ms 70 ms 69 ms te0-3-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.201]
12 41 ms 43 ms 47 ms te0-1-0-2.ccr21.ord01.atlas.cogentco.com [154.54.25.82]
13 68 ms 66 ms 66 ms te0-3-0-1.ccr21.bos01.atlas.cogentco.com [154.54.42.254]
14 65 ms 204 ms 223 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
15 70 ms 72 ms 72 ms 38.111.40.114
16 67 ms 68 ms 70 ms 208.95.185.41
te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134] seems to be a common culprit from what I've seen on other tracerts. I'll run another when I finish my download.
grouchy, first of all, on the whole 200ms latency is not that bad. But you keep saying the same thing over and over to everyone, regardless of their issue. Just how many times must "PWE's network people" need to see that there's a problem with Cogent Co-Lo in Boston?
same here, qo'nos, ds9, sectors, ships and chars going back and forth
1 <1 ms 1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 9 ms 89-73-14-1.dynamic.chello.pl [89.73.14.1]
3 9 ms 7 ms 6 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 35 ms 34 ms 34 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 34 ms 33 ms 33 ms pl-waw04a-rd1-ae12-2158.aorta.net [84.116.252.225]
6 43 ms 77 ms 33 ms 84.116.137.9
7 72 ms 33 ms 33 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 34 ms 35 ms 35 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 120 ms 119 ms 119 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
10 119 ms * 121 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 118 ms 123 ms 119 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 119 ms 126 ms 124 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 * 118 ms 118 ms 208.95.185.41
Bascially Ive had this issue for weeks, constant disconnects...
It seems periodic and its crippling my STO time. Now before you tell me to post the results of the tracert or the net-test there is no point both returned decent replies to my queries well within the parameters. It's odd though it seems more consistant when skype is Running.
It's odd though it seems more consistant when skype is Running.
Wait, are you saying there are more disconnects when you're running Skype, or less? If the former, that's completely understandable and should be expected. If that latter, then yeah that is odd.
Comments
The last nearly 24 hours now the game has not even been playable for me.
Either not even being able to connect to the login servers or once connected not being able to enter the game once selecting a character. Then if I do get past that but dare to play the game at all and zone or instance change it crashes.
I first approached this problem as something on my side.
I did every thing I could think of:
rebooted my computer
defraged my harddrive
scoured my computer for viruses
uninstalled and reinstalled (with a fresh download) of the game
reset my router
I know others have been having issues, have heard their complaints but I didn't think it was really this bad.
Target Name: patchserver.crypticstudios.com
IP: 208.95.185.41
Date/Time: 3/13/2013 4:14:35 AM
1 1 ms 0 ms 0 ms 1 ms homeportal [192.168.1.254]
2 56 ms 27 ms 24 ms 27 ms 108-204-64-2.lightspeed.bkfdca.sbcglobal.net [108.204.64.2]
3 N/A N/A N/A 22 ms [99.160.71.30]
4 25 ms 26 ms 24 ms 25 ms [12.83.69.137]
5 30 ms 78 ms 31 ms 31 ms ggr6.wswdc.ip.att.net [12.122.86.89]
6 33 ms 32 ms 32 ms 32 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45]
7 33 ms 32 ms 32 ms 32 ms te0-3-0-3.ccr21.sjc01.atlas.cogentco.com [154.54.6.81]
8 34 ms 34 ms 34 ms 34 ms te0-3-0-5.mpd21.sfo01.atlas.cogentco.com [154.54.86.185]
9 70 ms 70 ms 71 ms 71 ms te0-3-0-3.mpd21.mci01.atlas.cogentco.com [154.54.0.101]
10 79 ms 79 ms 79 ms 78 ms te0-7-0-33.mpd21.ord01.atlas.cogentco.com [154.54.2.234]
11 N/A N/A N/A 103 ms te0-7-0-2.ccr21.bos01.atlas.cogentco.com [154.54.28.114]
12 104 ms 105 ms 103 ms 103 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 116 ms 108 ms 115 ms 111 ms [38.111.40.114]
14 102 ms 101 ms 102 ms 127 ms [208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 101ms, Maximum = 127ms, Average = 108ms
Target Name: patchserver.crypticstudios.com
IP: 208.95.185.41
Date/Time: 3/13/2013 4:16:05 AM to 3/13/2013 4:17:12 AM
1 0 ms 0 ms N/A N/A 0 ms N/A N/A 0 ms 0 ms 0 ms homeportal [192.168.1.254]
2 23 ms 23 ms N/A N/A 24 ms N/A N/A 24 ms 31 ms 49 ms 108-204-64-2.lightspeed.bkfdca.sbcglobal.net [108.204.64.2]
3 * 23 ms N/A N/A * N/A N/A * * * [99.160.71.30]
4 26 ms 26 ms N/A N/A 26 ms N/A N/A 23 ms 25 ms 24 ms [12.83.69.137]
5 29 ms 30 ms N/A N/A 30 ms N/A N/A 30 ms 30 ms 81 ms ggr6.wswdc.ip.att.net [12.122.86.89]
6 32 ms 32 ms N/A N/A 33 ms N/A N/A 33 ms 32 ms 32 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45]
7 32 ms 32 ms N/A N/A 32 ms N/A N/A 32 ms 32 ms 32 ms te0-3-0-3.ccr21.sjc01.atlas.cogentco.com [154.54.6.81]
8 34 ms 34 ms N/A N/A 35 ms N/A N/A 33 ms 34 ms 32 ms te0-3-0-5.mpd21.sfo01.atlas.cogentco.com [154.54.86.185]
9 70 ms 70 ms N/A N/A 70 ms N/A N/A 70 ms 70 ms 71 ms te0-3-0-3.mpd21.mci01.atlas.cogentco.com [154.54.0.101]
10 77 ms 79 ms N/A N/A 79 ms N/A N/A 78 ms 79 ms 78 ms te0-7-0-33.mpd21.ord01.atlas.cogentco.com [154.54.2.234]
11 104 ms * N/A N/A N/A N/A N/A N/A N/A 103 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54.43.178]
12 104 ms 129 ms N/A N/A 103 ms N/A N/A 105 ms N/A 103 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 108 ms 103 ms N/A N/A 113 ms N/A N/A 102 ms 109 ms 104 ms [38.111.40.114]
14 103 ms 103 ms N/A N/A 102 ms N/A N/A 103 ms 102 ms 102 ms [208.95.185.41]
Ping statistics for patchserver.crypticstudios.com
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 102ms, Maximum = 103ms, Average = 102ms
On a funny note, it was kind a cool to run around the space station with no one there. I guess beaming down is just as nasty as beaming out lol= whooopsy server timeout. There should be a new ship in the Zen market called " The U.S.S Server Timeout- Super duper Battle ship. <-- beam aboard this and have a timeout of your life! lol
contacting nettest server..
Local IP: 99.5.TRIBBLE.TRIBBLE
Ping: 61.2 msec
Port: 80: 325 KB/sec 14 KB/sec 361 KB/sec 500
Port: 80: 429 KB/sec 15 KB/sec 455 KB/sec 500
Port: 443: 383 KB/sec 14 KB/sec 415 KB/sec 500
Port: 443: timed out
Port: 7255: timed out
Port: 7255: 455 KB/sec 18 KB/sec 498 KB/sec 500
Port: 7003: timed out
Port: 7003: 414 KB/sec 15 KB/sec 444 KB/sec 500
Port: 7202: 422 KB/sec 16 KB/sec 460 KB/sec 500
Port: 7202: 403 KB/sec 16 KB/sec 440 KB/sec 500
Port: 7499: timed out
Port: 7499: 354 KB/sec 14 KB/sec 390 KB/sec 500
Port: 80: 488 KB/sec 19 KB/sec 530 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 9 KB/sec
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms homeportal [192.168.1.254]
2 40 ms 27 ms 29 ms 99-5-TRIBBLE-TRIBBLE.lightspeed.gnvlsc.sbcglobal.net [99.5.TRIBBLE.TRIBBLE]
3 36 ms 30 ms 28 ms 99.168.141.36
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 27 ms 28 ms 72.157.40.144
7 36 ms 39 ms 37 ms 12.81.44.62
8 38 ms 38 ms 38 ms 12.81.104.178
9 53 ms 37 ms 38 ms 12.81.34.3
10 48 ms 49 ms 39 ms ixc01asm-pos-3-3.bellsouth.net [65.83.237.7]
11 44 ms 43 ms 38 ms 12.81.46.3
12 40 ms 39 ms 39 ms 12.81.104.110
13 36 ms 37 ms 38 ms 12.81.56.15
14 40 ms 43 ms 40 ms 74.175.192.54
15 50 ms 51 ms 51 ms cr2.rlgnc.ip.att.net [12.123.152.110]
16 52 ms 51 ms 52 ms cr1.wswdc.ip.att.net [12.122.3.170]
17 49 ms 50 ms 49 ms gar13.n54ny.ip.att.net [12.122.81.245]
18 50 ms 49 ms 50 ms 192.205.37.106
19 51 ms 50 ms 51 ms te0-5-0-5.mpd22.dca01.atlas.cogentco.com [154.54.2.61]
20 55 ms 56 ms 56 ms te0-3-0-6.mpd22.jfk02.atlas.cogentco.com [154.54.3.234]
21 62 ms 62 ms 61 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.22]
22 * * * Request timed out.
23 67 ms 71 ms 71 ms 38.111.40.114
24 63 ms 62 ms 62 ms 208.95.185.41
Trace complete.
I'ev tried everything and nothing works. If you recall we had the same issues durining a patch a few weeks ago.
Hope it gets fixed soon!
I did a nettest test and Port 7255 timed out
contacting nettest server..
Local IP:
Ping: 28.6 msec
Port: 80: 1117 KB/sec 36 KB/sec 1186 KB/sec 500
Port: 80: 981 KB/sec 32 KB/sec 1042 KB/sec 500
Port: 443: 754 KB/sec 25 KB/sec 800 KB/sec 500
Port: 443: 1092 KB/sec 36 KB/sec 1158 KB/sec 500
Port: 7255: timed out
Port: 7255: 1161 KB/sec 38 KB/sec 1235 KB/sec 500
Port: 7003: 1119 KB/sec 36 KB/sec 1187 KB/sec 500
Port: 7003: 1130 KB/sec 36 KB/sec 1201 KB/sec 500
Port: 7202: 1120 KB/sec 36 KB/sec 1187 KB/sec 500
Port: 7202: 1130 KB/sec 37 KB/sec 1200 KB/sec 500
Port: 7499: 1169 KB/sec 38 KB/sec 1239 KB/sec 500
Port: 7499: 1127 KB/sec 36 KB/sec 1196 KB/sec 500
Port: 80: 1138 KB/sec 37 KB/sec 1207 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 4 KB/sec
hit return to exit
There's potentially tens of thousands of miles between you and the servers.
It's possible that any trouble you're having is somewhere in those tubes, and has nothing to do with you or the servers.
Sometimes related to your general location and some problem the internet service providers (ISPs) need to sort out.
What countries are you folks from?
It's pretty easy for me to say it's not my internal issue when EvE runs flawlessly, MWO runs flawlessly (as flawlessly as it ever does), SWGEmu's test servers are happy with me, large (1/2 gig) graphics files go happily to and from the ftp server I administer for the school I work at, and yet there are issues here.
Given all of the above I don't need to back up my claim with a tracert or their nettest
I've gone so far as to DMZ my box for testing purposes and still nothing. nettest is now failing across multiple ports, the launcher went into patch mode at a speed that can only be charitably described as slow...after taking 20+ seconds to even hook.
After closing the launcher in disgust I fired up EvE, and as expected the patch that was waiting for me came down @ 3+mbit/sec.
Either there is a common internet problem all over the world, or that problem is cryptics ISP, or it is a server problem. On my PC all other games and sites are functioning normally.
Its appears to be an issue with AT&T and COX (that i've been able to determine) trying to communicate with the game servers through the Atlas Cogentco Boston and/ore Chicago hubs.
Which is bad, since pretty much a good chunk of the US and even parts of the EU connect through there...or so goes my understanding
Not sure that any of the above helps...but imho...seeing WOW makes me feel a bit better lol
*Edit* This has hit these games before but the above info I've noted has been happening again these last few days
It's also strange these kinds of things happen (for me anyway) after maintenance.
"It's their job to sort this out" won't phase you in the least, will it?
I spent the better part of two decades in IT management at one of the largest retailers in the US. I project-managed the deployment of the 250+ pizza boxes, storage, database, and middleware servers that run their e-commerce site. I also ran the desktop services team, and help desk for it, that serviced the corporate offices.
If customers were calling the help desk to complain that they could not shop with us because the site was inaccessible, or kept kicking them off, or took 30 seconds to load a page on our site while it took 1 second on JC Penney's site and the help desk operator's response was continually "So hey, you need to run tracert back to our servers and email us the results...oh and run this program to test the port performance and email us that as well...just complaining about it isn't going to do any good" would result in a couple of things:
1. The customers would stop shopping there and shop somewhere else.
2. The help desk operator would be fired.
They own the relaitionship with their ISPs, I don't. If they can't be bothered to expend the trivial effort (And it is trivial. Just using dslReports I can fire up smoke and qos tests against my boxes from multiple sites around the country in less than ten minutes) required to generate remote connections against their systems to troubleshoot their problems why should I be bothered to pay them?
And by continuing to play STO is taken as defacto agreement to the TOS statement...
Also, there are some differences in functional requirements between a simple HTTP connection vs. a real time MMRPG Client that you should be aware of. Which one do you think requires a higher quality connection...
Do you get paid for this drivel?
The fact that there is a ToS that says these things can go wrong without you having a recourse doesn't make fixing them your problem. Logic much? I'll go slow: It is still their problem. They are the service provider. That they can not be held legally liable for damages in no way makes fixing their issues my responsibility. Their relationship with their network services providers may be my gaming problem, but it's not my issue to resolve.
If you think today's e-commerce sites, with advanced interactive tools, shopping carts, realtime streams to financial services, multi-media, real time video chats in some cases, and real time database calls are simple http it's not me who needs an education here. Then again, you don't want to know. You are a one-trick pony and I'll be darned if I can figure out why you are in a forum where users are supposed to be helping each other...when you are not doing any such thing. At some point, what you are doing amounts to trolling, since you keep repeating the same thing over and over again and not providing any assistance to anyone regarding this problem.
Solid realtime mmo communications has been alive and well since the late 90s, with phone lines and modems. Don't hold yourself out as an expert on this unless you really want to get into it.
Here's a tracert I ran last night while I was plagued with lag.
1 92 ms 1 ms <1 ms 192.168.15.1
2 * * * Request timed out.
3 9 ms 10 ms 9 ms tge7-1.snantx3600-er02.texas.rr.com [24.28.133.54]
4 18 ms 23 ms 24 ms tge0-9-0-2.snantx3000-tr02.texas.rr.com [24.175.33.172]
5 40 ms 23 ms 24 ms agg23.snantx6000-cr01.texas.rr.com [24.175.32.184]
6 28 ms 24 ms 23 ms agg2.dllatxl3-cr01.texas.rr.com [24.175.32.146]
7 26 ms 23 ms 23 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
8 17 ms 25 ms 18 ms 107.14.17.232
9 53 ms 65 ms 59 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]
10 66 ms 76 ms 53 ms te0-2-0-3.ccr21.dfw01.atlas.cogentco.com [154.54.6.93]
11 71 ms 70 ms 69 ms te0-3-0-6.ccr21.mci01.atlas.cogentco.com [154.54.46.201]
12 41 ms 43 ms 47 ms te0-1-0-2.ccr21.ord01.atlas.cogentco.com [154.54.25.82]
13 68 ms 66 ms 66 ms te0-3-0-1.ccr21.bos01.atlas.cogentco.com [154.54.42.254]
14 65 ms 204 ms 223 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
15 70 ms 72 ms 72 ms 38.111.40.114
16 67 ms 68 ms 70 ms 208.95.185.41
te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134] seems to be a common culprit from what I've seen on other tracerts. I'll run another when I finish my download.
Or you could save time and just post the blah blah part.
1 <1 ms 1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 9 ms 89-73-14-1.dynamic.chello.pl [89.73.14.1]
3 9 ms 7 ms 6 ms 89-75-4-65.infra.chello.pl [89.75.4.65]
4 35 ms 34 ms 34 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70]
5 34 ms 33 ms 33 ms pl-waw04a-rd1-ae12-2158.aorta.net [84.116.252.225]
6 43 ms 77 ms 33 ms 84.116.137.9
7 72 ms 33 ms 33 ms de-fra01a-ri2-xe-4-1-0.aorta.net [84.116.130.146]
8 34 ms 35 ms 35 ms xe-5-1-1.fra23.ip4.tinet.net [77.67.73.105]
9 120 ms 119 ms 119 ms xe-1-2-0.bos11.ip4.tinet.net [89.149.183.13]
10 119 ms * 121 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 118 ms 123 ms 119 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
12 119 ms 126 ms 124 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
13 * 118 ms 118 ms 208.95.185.41
It seems periodic and its crippling my STO time. Now before you tell me to post the results of the tracert or the net-test there is no point both returned decent replies to my queries well within the parameters. It's odd though it seems more consistant when skype is Running.