I've been having severe lag today, and occasional lag the past few days. Today was so bad it went beyond rubberbanding to every character and AI in a map freezing, with only some effects still rendering like plasma.
I'm having this exact same problem since today's patch. Game is unplayable. Server Not Responding messages lasting up to to ten minutes while everything on screen is frozen.
I wanted to chime in, I have been noticing very bad lag with this game for the past couple or so days, if not more
This is not a problem with my overall connection as I have run multiple speed tests, reset my modem and router, and speeds are constant of everything else I do on the internet that requires constant streaming...just STO is having this issue.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms JIGGLES [192.168.1.1]
2 90 ms 9 ms 9 ms 10.90.128.1
3 13 ms 15 ms 20 ms d226-12-165.home.cgocable.net [24.226.12.165]
4 15 ms 15 ms 15 ms d226-6-138.home.cgocable.net [24.226.6.138]
5 22 ms 25 ms 19 ms te3-3.ccr01.yhm01.atlas.cogentco.com [38.122.17.
21]
6 18 ms 16 ms 18 ms te3-7.ccr01.buf02.atlas.cogentco.com [154.54.82.
101]
7 25 ms 23 ms 24 ms te8-7.ccr01.alb02.atlas.cogentco.com [154.54.81.
137]
8 29 ms 30 ms 28 ms te0-7-0-25.ccr21.bos01.atlas.cogentco.com [154.5
4.43.9]
9 44 ms 206 ms 155 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 40 ms 34 ms 35 ms 38.111.40.114
11 29 ms 29 ms 31 ms 208.95.185.41
Gawd never seen anything this bad, can anyone give me a hand with this? Been rubberbanding since Monday the 2nd.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms <1 ms [yeah me]
2 13 ms 11 ms 13 ms pa-67-234-40-1.dhcp.embarqhsd.net [67.234.40.1]
3 15 ms 19 ms 14 ms 67.239.95.137
4 291 ms 268 ms 393 ms 208-110-248-217.centurylink.net [208.110.248.217
]
5 869 ms 853 ms 876 ms jfk-edge-25.inet.qwest.net [63.144.128.249]
6 839 ms 874 ms 774 ms jfk-brdr-04.inet.qwest.net [67.14.5.26]
7 848 ms 710 ms 770 ms te0-7-0-12.ccr21.jfk04.atlas.cogentco.com [154.5
4.11.181]
8 758 ms 840 ms 819 ms te0-1-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.44.69]
9 309 ms 299 ms 459 ms te0-2-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.44.94]
10 559 ms 613 ms 473 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 76 ms 72 ms 90 ms 38.111.40.114
12 614 ms 469 ms 164 ms 208.95.185.41
This sums up what the problem is... A ping value up to 180ms is considered playable. Your's isn't...
There appears to be an issue between your ISP and its connection to the qwest communication backbone... Since this is a ISP issue, there is nothing you can do yourself to correct the problem... You should contact your ISP and see if they can do something to correct the issue...
Been having this issue while playing STO or new Neverwinter from PWE/Cryptic. As my other MMO's such as WoW, SWTOR, Rift, Terra and EVE run fine im thinking it must be something wrong with my connection to Cryptic servers. I have tryed opening all ports in 7000-7500 range, incoming as well as outgoing, and i tryed using EU and US proxy. Even tried adjusting my graphic options. Nothing seems to help.
Please tell me if there is a way to fix this issue.
My ISP is T-Com, location Croatia
Here is my tracert and nettest, and i also added tracert for eu and us proxy's:
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 9 ms 12 ms 23 ms 172.16.0.1
2 * * * Request timed out.
3 16 ms 40 ms 14 ms 172.29.80.241
4 25 ms 125 ms 71 ms htr01-hvz02.ip.t-com.hr [195.29.241.181]
5 25 ms 20 ms 28 ms gtr10-htr01.ip.t-com.hr [195.29.240.97]
6 17 ms 27 ms 24 ms 212.162.29.17
7 973 ms 67 ms 64 ms ae-15-15.ebr2.berlin1.level3.net [4.69.151.190]
8 71 ms 65 ms 86 ms ae-27-27.ebr2.dusseldorf1.level3.net [4.69.200.169]
9 69 ms 61 ms 67 ms ae-23-23.ebr1.dusseldorf1.level3.net [4.69.143.189]
10 69 ms 62 ms 77 ms ae-48-48.ebr3.frankfurt1.level3.net [4.69.143.178]
11 80 ms 61 ms 62 ms ae-83-83.csw3.frankfurt1.level3.net [4.69.163.10]
12 * * * Request timed out.
13 62 ms 60 ms 61 ms be3020.ccr21.fra06.atlas.cogentco.com [130.117.15.193]
14 51 ms 64 ms 50 ms te0-6-0-5.ccr22.fra03.atlas.cogentco.com [154.54.76.57]
15 65 ms 74 ms 81 ms te0-3-0-4.mpd21.ams03.atlas.cogentco.com[154.54.39.173]
16 1187 ms 80 ms 76 ms te0-5-0-7.mpd22.lon13.atlas.cogentco.com[154.54.37.102]
17 191 ms 150 ms 154 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com[154.54.31.229]
18 158 ms 147 ms 162 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
19 161 ms 177 ms 158 ms 38.111.40.114
20 151 ms 154 ms 194 ms 208.95.185.41
Tracing route to eu2.proxy.crypticstudios.com [79.125.26.110]
over a maximum of 30 hops:
1 5 ms 3 ms 6 ms 172.16.0.1
2 * * * Request timed out.
3 15 ms 15 ms 15 ms 172.29.80.241
4 116 ms 31 ms 17 ms htr01-hvz02-2.ip.t-com.hr [195.29.241.109]
5 17 ms 17 ms 17 ms gtr10-htr01.ip.t-com.hr [195.29.240.97]
6 17 ms 18 ms 17 ms 212.162.29.21
7 539 ms 83 ms 79 ms ae-15-15.ebr2.berlin1.level3.net [4.69.151.190]
8 78 ms 82 ms 79 ms ae-26-26.ebr2.dusseldorf1.level3.net [4.69.200.165]
9 79 ms 81 ms 78 ms ae-46-46.ebr1.amsterdam1.level3.net [4.69.143.201]
10 80 ms 78 ms 81 ms ae-22-22.ebr2.amsterdam1.level3.net [4.69.143.58]
11 83 ms 82 ms 79 ms ae-47-47.ebr2.london1.level3.net [4.69.143.78]
12 79 ms 78 ms 80 ms vlan103.ebr1.london1.level3.net [4.69.143.93]
13 79 ms 78 ms 80 ms ae-1-8.bar1.dublin1.level3.net [4.69.153.230]
14 78 ms 80 ms 80 ms 213.242.106.86
15 84 ms 79 ms 80 ms 178.236.0.110
16 2041 ms 89 ms 94 ms 178.236.0.58
17 80 ms 81ms 85ms ec2-79-125-0-73.euwest1.compute.amazonaws.com[79.125.0.73]
18 * * * Request timed out.
19 * * * Request timed out.
20 694 ms 80 ms 85 ms ec2-79-125-26-110.eu-west-1.compute.amazonaws.com [79.125.26.110]
Trace complete.
US
Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
over a maximum of 30 hops:
1 7 ms 9 ms 3 ms 172.16.0.1
2 * * * Request timed out.
3 15 ms 16 ms 16 ms 172.29.80.241
4 32 ms 17 ms 18 ms htr01-hvz02-2.ip.t-com.hr [195.29.241.109]
5 19 ms 20 ms 17 ms gtr10-htr01.ip.t-com.hr [195.29.240.97]
6 16 ms 18 ms 18 ms 212.162.29.21
7 59 ms 60 ms 62 ms ae-15-15.ebr2.berlin1.level3.net [4.69.151.190]
8 61 ms 61 ms 61 ms ae-25-25.ebr2.dusseldorf1.level3.net [4.69.200.161]
9 63 ms 61 ms 60 ms ae-24-24.ebr1.dusseldorf1.level3.net [4.69.143.193]
10 62 ms 63 ms 61 ms ae-48-48.ebr3.frankfurt1.level3.net [4.69.143.178]
11 60 ms 61 ms 61 ms ae-73-73.csw2.frankfurt1.level3.net [4.69.163.6]
12 * * * Request timed out.
13 64 ms 62 ms 64 ms be3020.ccr21.fra06.atlas.cogentco.com [130.117.15.193]
14 1526 ms 66 ms 63 ms te0-3-0-6.mpd21.fra03.atlas.cogentco.com [154.54.76.53]
15 63 ms 76 ms 81 ms te0-3-0-2.mpd21.ams03.atlas.cogentco.com [130.117.2.41]
16 72 ms 74 ms 72 ms te0-1-0-0.mpd22.lon13.atlas.cogentco.com [130.117.0.198]
17 153 ms 145 ms 146 ms te0-3-1-0.ccr22.bos01.atlas.cogentco.com [154.54.5.122]
18 145 ms 146 ms 153 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
19 153 ms 150 ms 152 ms 38.111.40.114
20 145 ms 145 ms 145 ms us1.proxy.crypticstudios.com [208.95.184.152]
Trace complete.
I see my connection has some problems connecting to cryptic servers at times whitch results in my issue seen in video i think.
BTW, my other MMO's run just fine with low lag around 60-85ms at all times.
Here is my tracert and nettest, and i also added tracert for eu and us proxy's:
Tracert:
15 65 ms 74 ms 81 ms te0-3-0-4.mpd21.ams03.atlas.cogentco.com[154.54.39.173] 16 1187 ms 80 ms 76 ms te0-5-0-7.mpd22.lon13.atlas.cogentco.com[154.54.37.102]
17 191 ms 150 ms 154 ms te0-3-0-3.ccr21.bos01.atlas.cogentco.com[154.54.31.229]
....
Looks like Cogent Communications London gateway (Trans-Atlantic cable link) is having congestion issues... which means theirs nothing you can do yourself, (besides complain to your ISP...) as this is a ISP issue, and their the only ones who can correct the problem...
Yea, i was thinking the same thing, its wierd though, i have that problem only on Cryptic/PWE games. Was thinking about changing my ISP, though basicaly all ISP's in my country that are available for my region preety much suck, they have low bandwith up to 4MB/s because there still isn't optical cables in my region, only in major city's.
Anyway, i noticed that my problem only happens while on ground, works fine while in space (i have tryed starbase 42 group event and i didn't get any hickups).
EDIT:
Been looking around net for cogentco issue with STO and it seems lots of people have huge spikes when tracert gets to cogentco, good to know its not problem on my end. They should realy look into fixing their infastructure if it gets cogged up for so many people. Also, might be a good idea for Cryptic or PWE to appeal to them to fix it
Right now I am lucky to be patching at around 1mb a minute and a call into the cable company didnt seem to give any good results, additionally nothing else seems to be troubled except the speed of my download from cryptic.
Tracert:
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.1.1
2 * * * Request timed out.
3 15 ms 8 ms 9 ms ten0-0-0-7.orld38-ser1.bhn.net [72.31.194.148]
4 29 ms 22 ms 23 ms ten0-4-0-3.orld71-car1.bhn.net [71.44.61.88]
5 12 ms 11 ms 15 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 14 ms 23 ms 14 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 22 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
8 21 ms 20 ms 20 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms 89 ms 89 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
10 90 ms 95 ms 91 ms be2051.ccr22.atl01.atlas.cogentco.com [154.54.0.161]
11 108 ms 96 ms 98 ms te0-1-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.226]
12 100 ms 106 ms 104 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
13 106 ms 107 ms 106 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.34]
14 * 107 ms 105 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 113 ms 107 ms 107 ms 38.111.40.114
16 106 ms 110 ms 107 ms 208.95.185.41
Right now I am lucky to be patching at around 1mb a minute and a call into the cable company didnt seem to give any good results, additionally nothing else seems to be troubled except the speed of my download from cryptic.
Tracert:
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.1.1
2 * * * Request timed out.
3 15 ms 8 ms 9 ms ten0-0-0-7.orld38-ser1.bhn.net [72.31.194.148]
4 29 ms 22 ms 23 ms ten0-4-0-3.orld71-car1.bhn.net [71.44.61.88]
5 12 ms 11 ms 15 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 14 ms 23 ms 14 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 22 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72] 8 21 ms 20 ms 20 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms 89 ms 89 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
10 90 ms 95 ms 91 ms be2051.ccr22.atl01.atlas.cogentco.com [154.54.0.161]
11 108 ms 96 ms 98 ms te0-1-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.226]
12 100 ms 106 ms 104 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
13 106 ms 107 ms 106 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.34]
14 * 107 ms 105 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 113 ms 107 ms 107 ms 38.111.40.114
16 106 ms 110 ms 107 ms 208.95.185.41
Your Net Test throughput indicates you're suffering from severe packet drop. And the Trace Route hints that its occurring on the Road Runner gateway to Cogent Communications backbone.
(It could very well be that this gateway is being chocked by Netflix traffic and Road Runner hasn't expanded the gateway bandwidth enough to meet demand...)
And what kind of background task do you have running that is sending/receiving at 2KB/27KB while the Net Test itself was idle???
Your Net Test throughput indicates you're suffering from severe packet drop. And the Trace Route hints that its occurring on the Road Runner gateway to Cogent Communications backbone.
(It could very well be that this gateway is being chocked by Netflix traffic and Road Runner hasn't expanded the gateway bandwidth enough to meet demand...)
And what kind of background task do you have running that is sending/receiving at 2KB/27KB while the Net Test itself was idle???
If I was to guess at that point I still hadat least 1 active webpage continually sending information requests, dropbox, pandora and maybe something else running in the background, killing every process that I knew was talking out and running nettest again reduced that to 0/0.
Having dug up a copy of wireshark and watching it while the patcher was running, I can now see that yes, there is a large scale packet drop going on as a large number of packets were being marked out for various reasons. I can assume that complaining to the isp over this will be a fruitless gesture? From the looks of it the proxy also routes through the cogent trunk, so thats not a way to avoid it either
Why Developers don't do something about implementation of some measurement of lag in game, while playing, so players know how much lag they have, most of time i die in game because i don't know i have lag, in one moment i fighting and then msg is shown on screen server not responding, and die after msg disappear. If i have lag meter all the time i would know if i am able to play or not, and either i lagging or not.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 13 ms 9 ms 7 ms ten0-0-0-7.orld38-ser1.bhn.net [72.31.194.148]
4 24 ms 16 ms 20 ms ten0-1-0-5.orld71-car1.bhn.net [71.44.60.30]
5 10 ms 15 ms 15 ms hun0-0-0-0.orld71-cbr3.bhn.net [72.31.193.18]
6 11 ms 11 ms 10 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 21 ms 19 ms 27 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
8 19 ms 19 ms 19 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 * 91 ms 92 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
10 92 ms * 91 ms be2051.ccr22.atl01.atlas.cogentco.com [154.54.0.161]
11 97 ms 97 ms 97 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
12 102 ms 100 ms * be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
13 105 ms 106 ms 107 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
14 106 ms 107 ms 104 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 118 ms * 112 ms 38.111.40.114
16 105 ms 105 ms 105 ms 208.95.185.41
Trace complete.
C:\Users\Alex K>
the only things that may have slow me down is one computer on Hulu in the house, I do have a 20mb line, so I dont know if it will cause such a slow down.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms telstra.gateway [10.0.0.138]
2 32 ms 33 ms 31 ms lns02.sydnmtc.syd.iprimus.net.au
3 32 ms 31 ms 31 ms 50.72-134-203.static.sydnmtc.iprimus.net.au [203
.134.72.50]
4 31 ms 30 ms 31 ms xe-0-2-0.csr02.sydnmtc.nsw.iprimus.net.au [203.1
34.72.41]
5 80 ms 82 ms 87 ms xe-1-2-0.csr02.equ.iprimus.net.au [203.134.2.130
]
6 32 ms 31 ms 85 ms xe-1-0-0.bsr01.equ.iprimus.net.au [203.134.2.254
]
7 168 ms 168 ms 205 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138
]
8 168 ms 169 ms 169 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
9 254 ms 254 ms 254 ms xe-2-0-0.bos10.ip4.tinet.net [89.149.182.170]
10 256 ms 256 ms 257 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 264 ms 256 ms 256 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
12 261 ms 269 ms 267 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
13 265 ms 264 ms 265 ms 208.95.185.41
Any help would be greatly appreciated, haven't really had to fiddle with this stuff before, all my other MMOs work just fine, but I am a die hard trekkie nerd and can't bring myself to give up on it haha
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms telstra.gateway [10.0.0.138]
2 32 ms 33 ms 31 ms lns02.sydnmtc.syd.iprimus.net.au
3 32 ms 31 ms 31 ms 50.72-134-203.static.sydnmtc.iprimus.net.au [203
.134.72.50]
4 31 ms 30 ms 31 ms xe-0-2-0.csr02.sydnmtc.nsw.iprimus.net.au [203.1
34.72.41]
5 80 ms 82 ms 87 ms xe-1-2-0.csr02.equ.iprimus.net.au [203.134.2.130
] 6 32 ms 31 ms 85 ms xe-1-0-0.bsr01.equ.iprimus.net.au [203.134.2.254
]
7 168 ms 168 ms 205 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138
]
8 168 ms 169 ms 169 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
9 254 ms 254 ms 254 ms xe-2-0-0.bos10.ip4.tinet.net [89.149.182.170]
10 256 ms 256 ms 257 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 264 ms 256 ms 256 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
12 261 ms 269 ms 267 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
13 265 ms 264 ms 265 ms 208.95.185.41
Trace complete.
...
This explains the problem... Your ISP (iprimus.net.au) is having problems pushing traffic onto the tinet.net backbone (Trans-Pacific link?)
Only the ISP can correct this problem. The only thing you can do is complain to your ISP to fix the problem...
I've been having massive amounts of rubberbanding most noticeably since the start of the recent Crystalline Entity event and I assume the troubles started about then, though it's possible it's been happening longer and I just hadn't noticed. Though along with that, I hadn't noticed NPCs and players skipping in motion prior with occasional pauses like I have seen recently either, so I'd like to think it's recent.
While playing earlier, the game was getting particularly flaky so I took these while it was happening, hoping someone could point me in the right direction.
Did a tracert, the nettest, and a ping test, all following:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.209.64.1
2 9 ms 8 ms 8 ms ten0-0-0-7.orld13-ser1.bhn.net [72.31.239.196]
3 11 ms 11 ms 11 ms ten0-3-0-5.orld48-car1.bhn.net [71.44.60.24]
4 13 ms 24 ms 11 ms ten0-10-0-5.orld71-car1.bhn.net [71.44.61.40]
5 15 ms 23 ms 16 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 16 ms 15 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
7 23 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
8 26 ms 21 ms 21 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms * 92 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
10 93 ms 92 ms 92 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.
145]
11 99 ms * 101 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
12 100 ms 101 ms * be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
13 110 ms 110 ms * be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
14 109 ms 150 ms 110 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
15 120 ms 109 ms * 38.111.40.114
16 * 107 ms 107 ms 208.95.185.41
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 106ms, Average = 106ms
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=104ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=113ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=110ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=110ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Ping statistics for 208.95.185.41:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 113ms, Average = 106ms
I've been having massive amounts of rubberbanding most noticeably since the start of the recent Crystalline Entity event and I assume the troubles started about then, though it's possible it's been happening longer and I just hadn't noticed. Though along with that, I hadn't noticed NPCs and players skipping in motion prior with occasional pauses like I have seen recently either, so I'd like to think it's recent.
While playing earlier, the game was getting particularly flaky so I took these while it was happening, hoping someone could point me in the right direction.
Did a tracert, the nettest, and a ping test, all following:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.209.64.1
2 9 ms 8 ms 8 ms ten0-0-0-7.orld13-ser1.bhn.net [72.31.239.196]
3 11 ms 11 ms 11 ms ten0-3-0-5.orld48-car1.bhn.net [71.44.60.24]
4 13 ms 24 ms 11 ms ten0-10-0-5.orld71-car1.bhn.net [71.44.61.40]
5 15 ms 23 ms 16 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 16 ms 15 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
7 23 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72] 8 26 ms 21 ms 21 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms * 92 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
10 93 ms 92 ms 92 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.
145]
11 99 ms * 101 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
12 100 ms 101 ms * be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
13 110 ms 110 ms * be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
14 109 ms 150 ms 110 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
15 120 ms 109 ms * 38.111.40.114
16 * 107 ms 107 ms 208.95.185.41
Trace complete.
Ping statistics for 208.95.185.41:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 113ms, Average = 106ms
Looks like the dropped packets is occurring on the gateway between the Road Runner Backbone and the Cogent Backbone. You are also suffering from a greater packet drop then what the ping statistics indicate, as ping uses multiple independent IP packets, while the TCP/IP connection needs a streamed sequence of packets which is easier to break.. (as your Net Test results show...)
This is strictly a ISP issue. The only thing you can really do is to complain to your ISP, so they can complain to Road Runner to get their act together...
What does it mean when you can't even get nettest to work? Whenever I run it, it says "timed out".
I found my way to this thread after already having problems running the game. Whenever I try to load up the launcher for STO, I get a window saying "Trying to update the launcher. Please be patient." It tries for about 5 times and then I get an error window saying "Unable to establish connection to Patch Server. Please check your Internet connection. If problem persists, please contact Technical Support."
I've already tried some of the other suggestions I've seen, such as flushing my DNS cache and renewing my IP address, to no avail. The most frustrating thing is I was just playing the game mere hours ago, took a break, and then had this suddenly crop up when I tried to play again.
"There will never be enough blood to wash away my need for vengeance! A single world...I could destroy a million worlds and it would not be enough! Your existence is an insult to the memory of my people! I will continue my fight, even if I must fight alone!"
What does it mean when you can't even get nettest to work? Whenever I run it, it says "timed out".
...
If you want to be technical, it means that 'Net Test' and the diagnostic server on the STO network could not complete the TCP/IP three way handshake used to establish a connection...
In simpler layman terms, it can't connect...
And this is a connection to a much simpler diagnostic server, so any additional overhead and load on the STO Servers are out of the picture here. So if you can't connect to the Net Test Server, its highly unlikely you can connect to the STO Server, showing that this is a Internet connection issue and not a STO Server issue...
Now why it can't connect, it could be router issues, firewall misconfiguration, ISP blocking or throttling, excessive network congestion, etc. etc. Thats what the other network diagnostics are for, to rule out other causes and try to pinpoint what the exact issue is. The 'Trace Route' diagnostic is useful for looking at ISP issues and network congestion on the route to the STO servers....
Now why it can't connect, it could be router issues, firewall misconfiguration, ISP blocking or throttling, excessive network congestion, etc. etc. Thats what the other network diagnostics are for, to rule out other causes and try to pinpoint what the exact issue is. The 'Trace Route' diagnostic is useful for looking at ISP issues and network congestion on the route to the STO servers....
I think it may have been an "etc." on my computer's end. I had some theories as to what may have been causing the problem, and did a system restore just to see. That seems to have fixed the problem: I was able to log on and play.
Thanks for all that info though. If I have problems of a similar nature, next time I'll try posting what my Trace Route diagnostic came up with, too.
"There will never be enough blood to wash away my need for vengeance! A single world...I could destroy a million worlds and it would not be enough! Your existence is an insult to the memory of my people! I will continue my fight, even if I must fight alone!"
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.1.1
2 * * * Request timed out.
3 10 ms 9 ms 11 ms ten0-7-0-0.ORLD23-ser2.bhn.net [72.31.194.42]
4 10 ms 11 ms 11 ms ten0-1-0-7.orld31-car2.bhn.net [97.69.194.196]
5 27 ms 23 ms 22 ms ten0-4-0-6.orld71-car2.bhn.net [71.44.61.22]
6 13 ms 15 ms 15 ms 72-31-193-191.net.bhntampa.com [72.31.193.191]
7 19 ms 19 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98] 8 25 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
9 23 ms 23 ms 24 ms 107.14.19.13
10 93 ms 93 ms 88 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
11 92 ms 91 ms 94 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.
165]
12 96 ms 103 ms 98 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31
.106]
13 104 ms 103 ms 102 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
14 109 ms 107 ms 108 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
15 127 ms 110 ms 108 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
16 116 ms 111 ms 110 ms 38.111.40.114
17 108 ms 108 ms 106 ms 208.95.185.41
Trace complete.
My ISP is Brighthouse/Roadrunner in the central Florida USA area. I'm curious what I can do to fix my issue
Your showing the same symptoms as other players who connect via the Road Runner service. The 'Net Test' results shows degraded performance, most likely from excessive packet drop. And the Trace Route hints that this is occurring on the gateway between the Road Runner and Cogent backbone. This is a ISP issue as only the ISP involved can correct this problem. Looks like its time to contact your ISP... (complain about severe packet drop on your connection to the STO Servers)
I'm not entirely sure where to post this, but starting since last night I haven't been able to log in AT ALL. I keep getting disconnected almost immediatly after managing to make my way into the game. Sometimes I can stay in or several minutes, but lately it's just effing broken. There's nothing wrong with my connection, but for some reason I am CONSTANTLY getting disconnected from the server everytime I get into game.
I'm not entirely sure where to post this, but starting since last night I haven't been able to log in AT ALL. I keep getting disconnected almost immediatly after managing to make my way into the game. Sometimes I can stay in or several minutes, but lately it's just effing broken. There's nothing wrong with my connection, but for some reason I am CONSTANTLY getting disconnected from the server everytime I get into game.
So what does your 'Net Test' and 'Trace Route' results look like??? No one will be able to help you unless you provide some information...
I have been keeping a close eye on threads such as this one after last Thursday's update. Ever since then I have had the same symptoms as many other people are reporting, the Lag, rubber banding ETC. I have tried using both a static IP and a dynamic IP and there has been no difference. The Traceroute looks to be ok but my Nettest results seem terrible when compared with the good results marked in the first post. Any advice would be greatly appreciated! I managed to get through a CCE mission without any problems when I tried at 07:30GMT which I have been unable to do since Thursday night!
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 36 ms 36 ms 35 ms 62.72.148.128
3 34 ms 35 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
4 37 ms 34 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
5 69 ms 60 ms 57 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
6 37 ms 35 ms 36 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
7 36 ms 35 ms 34 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
8 36 ms 37 ms 35 ms ge-7-0-0.mpr1.lhr2.uk.above.net [64.125.28.25]
9 108 ms 107 ms 108 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
10 108 ms 109 ms 108 ms xe-0-0-0.cr2.dca2.us.above.net [64.125.28.242]
11 120 ms 119 ms 119 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]
12 118 ms 119 ms 119 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
13 117 ms 116 ms 116 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
14 129 ms 115 ms 116 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 116 ms 124 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 116 ms 115 ms 115 ms 208.95.185.41
I have been keeping a close eye on threads such as this one after last Thursday's update. Ever since then I have had the same symptoms as many other people are reporting, the Lag, rubber banding ETC. I have tried using both a static IP and a dynamic IP and there has been no difference. The Traceroute looks to be ok ...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 36 ms 36 ms 35 ms 62.72.148.128
3 34 ms 35 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
4 37 ms 34 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
5 69 ms 60 ms 57 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
6 37 ms 35 ms 36 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
7 36 ms 35 ms 34 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
8 36 ms 37 ms 35 ms ge-7-0-0.mpr1.lhr2.uk.above.net [64.125.28.25]
9 108 ms 107 ms 108 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
10 108 ms 109 ms 108 ms xe-0-0-0.cr2.dca2.us.above.net [64.125.28.242]
11 120 ms 119 ms 119 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]
12 118 ms 119 ms 119 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
13 117 ms 116 ms 116 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
14 129 ms 115 ms 116 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 116 ms 124 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 116 ms 115 ms 115 ms 208.95.185.41
Trace complete.
Looks like the above.net Trans-Atlantic link (uk - us) is suffering from network congestion issues, and most likely is the source of the severe packet drop that is causing your poor Net Test results....
This is a ISP issue, as only above.net can correct the problem with their Trans-Atlantic cable connection...
Looks like the above.net Trans-Atlantic link (uk - us) is suffering from network congestion issues, and most likely is the source of the severe packet drop that is causing your poor Net Test results....
This is a ISP issue, as only above.net can correct the problem with their Trans-Atlantic cable connection...
Many thanks Grouchy! I will get on them straight away!
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 28 ms 24 ms 25 ms albq-dsl-gw48.albq.qwest.net [67.42.200.48]
3 103 ms 128 ms 123 ms albq-agw1.inet.qwest.net [71.222.249.121]
4 48 ms 48 ms 59 ms lap-brdr-04.inet.qwest.net [67.14.22.158]
5 76 ms 79 ms 82 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.54.11.125]
6 86 ms 88 ms 90 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
7 116 ms 112 ms 116 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.157]
8 128 ms 124 ms 138 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 125 ms 131 ms 134 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
10 100 ms 102 ms 101 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 107 ms 105 ms 107 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
12 183 ms 104 ms 105 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
13 112 ms 107 ms 107 ms 38.111.40.114
14 105 ms 111 ms 114 ms 208.95.185.41
Comments
I'm having this exact same problem since today's patch. Game is unplayable. Server Not Responding messages lasting up to to ten minutes while everything on screen is frozen.
Please fix this.
This is not a problem with my overall connection as I have run multiple speed tests, reset my modem and router, and speeds are constant of everything else I do on the internet that requires constant streaming...just STO is having this issue.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms JIGGLES [192.168.1.1]
2 90 ms 9 ms 9 ms 10.90.128.1
3 13 ms 15 ms 20 ms d226-12-165.home.cgocable.net [24.226.12.165]
4 15 ms 15 ms 15 ms d226-6-138.home.cgocable.net [24.226.6.138]
5 22 ms 25 ms 19 ms te3-3.ccr01.yhm01.atlas.cogentco.com [38.122.17.
21]
6 18 ms 16 ms 18 ms te3-7.ccr01.buf02.atlas.cogentco.com [154.54.82.
101]
7 25 ms 23 ms 24 ms te8-7.ccr01.alb02.atlas.cogentco.com [154.54.81.
137]
8 29 ms 30 ms 28 ms te0-7-0-25.ccr21.bos01.atlas.cogentco.com [154.5
4.43.9]
9 44 ms 206 ms 155 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
10 40 ms 34 ms 35 ms 38.111.40.114
11 29 ms 29 ms 31 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
This is the first test is this good ?
contacting nettest server..
Local IP: 67.193.182.14
Ping: 31.3 msec
Port: 80: 1238 KB/sec 41 KB/sec 1306 KB/sec 500
Port: 80: 1206 KB/sec 40 KB/sec 1272 KB/sec 500
Port: 443: 1356 KB/sec 44 KB/sec 1430 KB/sec 500
Port: 443: 862 KB/sec 30 KB/sec 925 KB/sec 500
Port: 7255: 1192 KB/sec 39 KB/sec 1256 KB/sec 500
Port: 7255: 1134 KB/sec 38 KB/sec 1196 KB/sec 500
Port: 7003: 616 KB/sec 21 KB/sec 654 KB/sec 500
Port: 7003: 1168 KB/sec 38 KB/sec 1230 KB/sec 500
Port: 7202: 896 KB/sec 30 KB/sec 945 KB/sec 500
Port: 7202: 1282 KB/sec 42 KB/sec 1351 KB/sec 500
Port: 7499: 1314 KB/sec 43 KB/sec 1386 KB/sec 500
Port: 7499: 1262 KB/sec 41 KB/sec 1331 KB/sec 500
Port: 80: 7 KB/sec 2 KB/sec 11 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
This is the second test i am really dumb with computers is this good?
I keep getting server connection failed and it is really getting annoying.
Thank you for any help.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 2 ms <1 ms [yeah me]
2 13 ms 11 ms 13 ms pa-67-234-40-1.dhcp.embarqhsd.net [67.234.40.1]
3 15 ms 19 ms 14 ms 67.239.95.137
4 291 ms 268 ms 393 ms 208-110-248-217.centurylink.net [208.110.248.217
]
5 869 ms 853 ms 876 ms jfk-edge-25.inet.qwest.net [63.144.128.249]
6 839 ms 874 ms 774 ms jfk-brdr-04.inet.qwest.net [67.14.5.26]
7 848 ms 710 ms 770 ms te0-7-0-12.ccr21.jfk04.atlas.cogentco.com [154.5
4.11.181]
8 758 ms 840 ms 819 ms te0-1-0-0.mpd21.jfk02.atlas.cogentco.com [154.54
.44.69]
9 309 ms 299 ms 459 ms te0-2-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.44.94]
10 559 ms 613 ms 473 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 76 ms 72 ms 90 ms 38.111.40.114
12 614 ms 469 ms 164 ms 208.95.185.41
Trace complete.
That looks horrible. What can I do about that?
Anything of interest in this nettest?
contacting nettest server..
Local IP: [It's me]
Ping: 601.5 msec
Port: 80: 142 KB/sec 83 KB/sec 199 KB/sec 500
Port: 80: 43 KB/sec 87 KB/sec 128 KB/sec 500
Port: 443: 93 KB/sec 76 KB/sec 172 KB/sec 500
Port: 443: 56 KB/sec 87 KB/sec 142 KB/sec 500
Port: 7255: 68 KB/sec 79 KB/sec 154 KB/sec 500
Port: 7255: 100 KB/sec 72 KB/sec 162 KB/sec 500
Port: 7003: 258 KB/sec 29 KB/sec 301 KB/sec 500
Port: 7003: 206 KB/sec 26 KB/sec 284 KB/sec 500
Port: 7202: 54 KB/sec 81 KB/sec 138 KB/sec 500
Port: 7202: 214 KB/sec 56 KB/sec 286 KB/sec 500
Port: 7499: 63 KB/sec 84 KB/sec 155 KB/sec 500
Port: 7499: 112 KB/sec 74 KB/sec 189 KB/sec 500
Port: 80: 215 KB/sec 31 KB/sec 266 KB/sec 500
Idle NIC bandwidth Send: 27 KB/sec Recv: 28 KB/sec
hit return to exit
This sums up what the problem is... A ping value up to 180ms is considered playable. Your's isn't...
There appears to be an issue between your ISP and its connection to the qwest communication backbone... Since this is a ISP issue, there is nothing you can do yourself to correct the problem... You should contact your ISP and see if they can do something to correct the issue...
Please tell me if there is a way to fix this issue.
My ISP is T-Com, location Croatia
Thanx guys !!!
Check out my issue on youtube:
Issue Video
Here is my tracert and nettest, and i also added tracert for eu and us proxy's:
Tracert:
Nettest:
Tracert EU and US proxy:
EU:
US
I see my connection has some problems connecting to cryptic servers at times whitch results in my issue seen in video i think.
BTW, my other MMO's run just fine with low lag around 60-85ms at all times.
Looks like Cogent Communications London gateway (Trans-Atlantic cable link) is having congestion issues... which means theirs nothing you can do yourself, (besides complain to your ISP...) as this is a ISP issue, and their the only ones who can correct the problem...
Anyway, i noticed that my problem only happens while on ground, works fine while in space (i have tryed starbase 42 group event and i didn't get any hickups).
EDIT:
Been looking around net for cogentco issue with STO and it seems lots of people have huge spikes when tracert gets to cogentco, good to know its not problem on my end. They should realy look into fixing their infastructure if it gets cogged up for so many people. Also, might be a good idea for Cryptic or PWE to appeal to them to fix it
Tracert:
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.1.1
2 * * * Request timed out.
3 15 ms 8 ms 9 ms ten0-0-0-7.orld38-ser1.bhn.net [72.31.194.148]
4 29 ms 22 ms 23 ms ten0-4-0-3.orld71-car1.bhn.net [71.44.61.88]
5 12 ms 11 ms 15 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 14 ms 23 ms 14 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 22 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
8 21 ms 20 ms 20 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms 89 ms 89 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
10 90 ms 95 ms 91 ms be2051.ccr22.atl01.atlas.cogentco.com [154.54.0.161]
11 108 ms 96 ms 98 ms te0-1-0-2.mpd21.dca01.atlas.cogentco.com [154.54.28.226]
12 100 ms 106 ms 104 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
13 106 ms 107 ms 106 ms te0-1-0-2.ccr22.bos01.atlas.cogentco.com [154.54.44.34]
14 * 107 ms 105 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 113 ms 107 ms 107 ms 38.111.40.114
16 106 ms 110 ms 107 ms 208.95.185.41
Trace complete.
Nettest:
Ping: 158.0 msec
Port: 80: 27 KB/sec 4 KB/sec 67 KB/sec 500
Port: 80: 16 KB/sec 5 KB/sec 56 KB/sec 500
Port: 443: 20 KB/sec 2 KB/sec 58 KB/sec 500
Port: 443: 18 KB/sec 2 KB/sec 53 KB/sec 500
Port: 7255: 27 KB/sec 3 KB/sec 68 KB/sec 500
Port: 7255: 20 KB/sec 3 KB/sec 63 KB/sec 500
Port: 7003: 23 KB/sec 3 KB/sec 68 KB/sec 500
Port: 7003: 22 KB/sec 3 KB/sec 62 KB/sec 500
Port: 7202: timed out
Port: 7202: 21 KB/sec 3 KB/sec 63 KB/sec 500
Port: 7499: 16 KB/sec 3 KB/sec 49 KB/sec 500
Port: 7499: 20 KB/sec 4 KB/sec 72 KB/sec 500
Port: 80: 21 KB/sec 4 KB/sec 65 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 27 KB/sec
Your Net Test throughput indicates you're suffering from severe packet drop. And the Trace Route hints that its occurring on the Road Runner gateway to Cogent Communications backbone.
(It could very well be that this gateway is being chocked by Netflix traffic and Road Runner hasn't expanded the gateway bandwidth enough to meet demand...)
And what kind of background task do you have running that is sending/receiving at 2KB/27KB while the Net Test itself was idle???
If I was to guess at that point I still hadat least 1 active webpage continually sending information requests, dropbox, pandora and maybe something else running in the background, killing every process that I knew was talking out and running nettest again reduced that to 0/0.
Having dug up a copy of wireshark and watching it while the patcher was running, I can now see that yes, there is a large scale packet drop going on as a large number of packets were being marked out for various reasons. I can assume that complaining to the isp over this will be a fruitless gesture? From the looks of it the proxy also routes through the cogent trunk, so thats not a way to avoid it either
C:\Users\Alex K>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 13 ms 9 ms 7 ms ten0-0-0-7.orld38-ser1.bhn.net [72.31.194.148]
4 24 ms 16 ms 20 ms ten0-1-0-5.orld71-car1.bhn.net [71.44.60.30]
5 10 ms 15 ms 15 ms hun0-0-0-0.orld71-cbr3.bhn.net [72.31.193.18]
6 11 ms 11 ms 10 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
7 21 ms 19 ms 27 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
8 19 ms 19 ms 19 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 * 91 ms 92 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
10 92 ms * 91 ms be2051.ccr22.atl01.atlas.cogentco.com [154.54.0.161]
11 97 ms 97 ms 97 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
12 102 ms 100 ms * be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
13 105 ms 106 ms 107 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
14 106 ms 107 ms 104 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
15 118 ms * 112 ms 38.111.40.114
16 105 ms 105 ms 105 ms 208.95.185.41
Trace complete.
C:\Users\Alex K>
the only things that may have slow me down is one computer on Hulu in the house, I do have a 20mb line, so I dont know if it will cause such a slow down.
Tracert is as follows -
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms telstra.gateway [10.0.0.138]
2 32 ms 33 ms 31 ms lns02.sydnmtc.syd.iprimus.net.au
3 32 ms 31 ms 31 ms 50.72-134-203.static.sydnmtc.iprimus.net.au [203
.134.72.50]
4 31 ms 30 ms 31 ms xe-0-2-0.csr02.sydnmtc.nsw.iprimus.net.au [203.1
34.72.41]
5 80 ms 82 ms 87 ms xe-1-2-0.csr02.equ.iprimus.net.au [203.134.2.130
]
6 32 ms 31 ms 85 ms xe-1-0-0.bsr01.equ.iprimus.net.au [203.134.2.254
]
7 168 ms 168 ms 205 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138
]
8 168 ms 169 ms 169 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
9 254 ms 254 ms 254 ms xe-2-0-0.bos10.ip4.tinet.net [89.149.182.170]
10 256 ms 256 ms 257 ms internap-gw.ip4.tinet.net [77.67.77.54]
11 264 ms 256 ms 256 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
12 261 ms 269 ms 267 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
13 265 ms 264 ms 265 ms 208.95.185.41
Trace complete.
nettest result -
contacting nettest server..
Local IP:
Ping: 230.9 msec
Port: 80: 252 KB/sec 204 KB/sec 270 KB/sec 500
Port: 80: 249 KB/sec 290 KB/sec 270 KB/sec 500
Port: 443: 222 KB/sec 225 KB/sec 245 KB/sec 500
Port: 443: 231 KB/sec 317 KB/sec 249 KB/sec 500
Port: 7255: 270 KB/sec 291 KB/sec 290 KB/sec 500
Port: 7255: 229 KB/sec 200 KB/sec 245 KB/sec 500
Port: 7003: 232 KB/sec 287 KB/sec 249 KB/sec 500
Port: 7003: 242 KB/sec 153 KB/sec 260 KB/sec 500
Port: 7202: 253 KB/sec 227 KB/sec 276 KB/sec 500
Port: 7202: 232 KB/sec 126 KB/sec 249 KB/sec 500
Port: 7499: 233 KB/sec 273 KB/sec 250 KB/sec 500
Port: 7499: 224 KB/sec 410 KB/sec 245 KB/sec 500
Port: 80: 96 KB/sec 344 KB/sec 673 KB/sec 500
Idle NIC bandwidth Send: 315 KB/sec Recv: 2 KB/sec
hit return to exit
Any help would be greatly appreciated, haven't really had to fiddle with this stuff before, all my other MMOs work just fine, but I am a die hard trekkie nerd and can't bring myself to give up on it haha
This explains the problem... Your ISP (iprimus.net.au) is having problems pushing traffic onto the tinet.net backbone (Trans-Pacific link?)
Only the ISP can correct this problem. The only thing you can do is complain to your ISP to fix the problem...
While playing earlier, the game was getting particularly flaky so I took these while it was happening, hoping someone could point me in the right direction.
Did a tracert, the nettest, and a ping test, all following:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.209.64.1
2 9 ms 8 ms 8 ms ten0-0-0-7.orld13-ser1.bhn.net [72.31.239.196]
3 11 ms 11 ms 11 ms ten0-3-0-5.orld48-car1.bhn.net [71.44.60.24]
4 13 ms 24 ms 11 ms ten0-10-0-5.orld71-car1.bhn.net [71.44.61.40]
5 15 ms 23 ms 16 ms 72-31-193-133.net.bhntampa.com [72.31.193.133]
6 16 ms 15 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66
.109.6.98]
7 23 ms 23 ms 23 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.10
9.1.72]
8 26 ms 21 ms 21 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 91 ms * 92 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
10 93 ms 92 ms 92 ms be2053.mpd22.atl01.atlas.cogentco.com [154.54.3.
145]
11 99 ms * 101 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
12 100 ms 101 ms * be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
13 110 ms 110 ms * be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
14 109 ms 150 ms 110 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
15 120 ms 109 ms * 38.111.40.114
16 * 107 ms 107 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP:
Ping: 107.2 msec
Port: 80: 17 KB/sec 1 KB/sec 18 KB/sec 500
Port: 80: timed out
Port: 443: 15 KB/sec 3 KB/sec 28 KB/sec 500
Port: 443: 13 KB/sec 4 KB/sec 40 KB/sec 500
Port: 7255: 14 KB/sec 2 KB/sec 20 KB/sec 500
Port: 7255: timed out
Port: 7003: timed out
Port: 7003: 18 KB/sec 2 KB/sec 28 KB/sec 500
Port: 7202: timed out
Port: 7202: 17 KB/sec 3 KB/sec 36 KB/sec 500
Port: 7499: 12 KB/sec 3 KB/sec 27 KB/sec 500
Port: 7499: 9 KB/sec 2 KB/sec 15 KB/sec 500
Port: 80: 14 KB/sec 2 KB/sec 20 KB/sec 500
Idle NIC bandwidth Send: 3 KB/sec Recv: 4 KB/sec
hit return to exit
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 106ms, Average = 106ms
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=104ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=105ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=113ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=110ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=110ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Request timed out.
Reply from 208.95.185.41: bytes=32 time=108ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=109ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Reply from 208.95.185.41: bytes=32 time=106ms TTL=46
Reply from 208.95.185.41: bytes=32 time=107ms TTL=46
Ping statistics for 208.95.185.41:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 113ms, Average = 106ms
Looks like the dropped packets is occurring on the gateway between the Road Runner Backbone and the Cogent Backbone. You are also suffering from a greater packet drop then what the ping statistics indicate, as ping uses multiple independent IP packets, while the TCP/IP connection needs a streamed sequence of packets which is easier to break.. (as your Net Test results show...)
This is strictly a ISP issue. The only thing you can really do is to complain to your ISP, so they can complain to Road Runner to get their act together...
I found my way to this thread after already having problems running the game. Whenever I try to load up the launcher for STO, I get a window saying "Trying to update the launcher. Please be patient." It tries for about 5 times and then I get an error window saying "Unable to establish connection to Patch Server. Please check your Internet connection. If problem persists, please contact Technical Support."
I've already tried some of the other suggestions I've seen, such as flushing my DNS cache and renewing my IP address, to no avail. The most frustrating thing is I was just playing the game mere hours ago, took a break, and then had this suddenly crop up when I tried to play again.
If you want to be technical, it means that 'Net Test' and the diagnostic server on the STO network could not complete the TCP/IP three way handshake used to establish a connection...
In simpler layman terms, it can't connect...
And this is a connection to a much simpler diagnostic server, so any additional overhead and load on the STO Servers are out of the picture here. So if you can't connect to the Net Test Server, its highly unlikely you can connect to the STO Server, showing that this is a Internet connection issue and not a STO Server issue...
Now why it can't connect, it could be router issues, firewall misconfiguration, ISP blocking or throttling, excessive network congestion, etc. etc. Thats what the other network diagnostics are for, to rule out other causes and try to pinpoint what the exact issue is. The 'Trace Route' diagnostic is useful for looking at ISP issues and network congestion on the route to the STO servers....
I think it may have been an "etc." on my computer's end. I had some theories as to what may have been causing the problem, and did a system restore just to see. That seems to have fixed the problem: I was able to log on and play.
Thanks for all that info though. If I have problems of a similar nature, next time I'll try posting what my Trace Route diagnostic came up with, too.
Your showing the same symptoms as other players who connect via the Road Runner service. The 'Net Test' results shows degraded performance, most likely from excessive packet drop. And the Trace Route hints that this is occurring on the gateway between the Road Runner and Cogent backbone. This is a ISP issue as only the ISP involved can correct this problem. Looks like its time to contact your ISP... (complain about severe packet drop on your connection to the STO Servers)
So what does your 'Net Test' and 'Trace Route' results look like??? No one will be able to help you unless you provide some information...
I have been keeping a close eye on threads such as this one after last Thursday's update. Ever since then I have had the same symptoms as many other people are reporting, the Lag, rubber banding ETC. I have tried using both a static IP and a dynamic IP and there has been no difference. The Traceroute looks to be ok but my Nettest results seem terrible when compared with the good results marked in the first post. Any advice would be greatly appreciated! I managed to get through a CCE mission without any problems when I tried at 07:30GMT which I have been unable to do since Thursday night!
Traceroute Results:
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 36 ms 36 ms 35 ms 62.72.148.128
3 34 ms 35 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
4 37 ms 34 ms 35 ms te0-2-0-5.cr01.ts1.bb.daisyplc.net [62.72.137.161]
5 69 ms 60 ms 57 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
6 37 ms 35 ms 36 ms te2-2.cr05.tn5.bb.gxn.net [62.72.137.126]
7 36 ms 35 ms 34 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
8 36 ms 37 ms 35 ms ge-7-0-0.mpr1.lhr2.uk.above.net [64.125.28.25]
9 108 ms 107 ms 108 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
10 108 ms 109 ms 108 ms xe-0-0-0.cr2.dca2.us.above.net [64.125.28.242]
11 120 ms 119 ms 119 ms xe-1-1-0.mpr4.bos2.us.above.net [64.125.24.117]
12 118 ms 119 ms 119 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
13 117 ms 116 ms 116 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
14 129 ms 115 ms 116 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
15 116 ms 124 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 116 ms 115 ms 115 ms 208.95.185.41
Trace complete.
Nettest Results:
contacting nettest server..
Local IP: 95.172.231.84
Ping: 115.4 msec
Port: 80: 34 KB/sec 1 KB/sec 36 KB/sec 500
Port: 80: 34 KB/sec 11 KB/sec 83 KB/sec 500
Port: 443: 41 KB/sec 6 KB/sec 51 KB/sec 500
Port: 443: 42 KB/sec 3 KB/sec 57 KB/sec 500
Port: 7255: 46 KB/sec 3 KB/sec 64 KB/sec 500
Port: 7255: 36 KB/sec 6 KB/sec 54 KB/sec 500
Port: 7003: 50 KB/sec 3 KB/sec 58 KB/sec 500
Port: 7003: 44 KB/sec 2 KB/sec 56 KB/sec 500
Port: 7202: 94 KB/sec 5 KB/sec 148 KB/sec 500
Port: 7202: 45 KB/sec 5 KB/sec 142 KB/sec 500
Port: 7499: 103 KB/sec 5 KB/sec 133 KB/sec 500
Port: 7499: 34 KB/sec 2 KB/sec 37 KB/sec 500
Port: 80: 36 KB/sec 2 KB/sec 49 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
I am based in the UK if that helps... It would seem everyone else having the problem who has taken to the forums is Stateside...
Many thanks in advance!
D
Looks like the above.net Trans-Atlantic link (uk - us) is suffering from network congestion issues, and most likely is the source of the severe packet drop that is causing your poor Net Test results....
This is a ISP issue, as only above.net can correct the problem with their Trans-Atlantic cable connection...
Many thanks Grouchy! I will get on them straight away!
Do a pathping -n instead of tracert and this will help you understand it - http://technet.microsoft.com/en-us/library/cc958876.aspx
A good read on tracert - http://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf
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 28 ms 24 ms 25 ms albq-dsl-gw48.albq.qwest.net [67.42.200.48]
3 103 ms 128 ms 123 ms albq-agw1.inet.qwest.net [71.222.249.121]
4 48 ms 48 ms 59 ms lap-brdr-04.inet.qwest.net [67.14.22.158]
5 76 ms 79 ms 82 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.54.11.125]
6 86 ms 88 ms 90 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
7 116 ms 112 ms 116 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.157]
8 128 ms 124 ms 138 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 125 ms 131 ms 134 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
10 100 ms 102 ms 101 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 107 ms 105 ms 107 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
12 183 ms 104 ms 105 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
13 112 ms 107 ms 107 ms 38.111.40.114
14 105 ms 111 ms 114 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP: 97.119.165.10
Ping: 103.5 msec
Port: 80: 321 KB/sec 13 KB/sec 348 KB/sec 500
Port: 80: 307 KB/sec 11 KB/sec 327 KB/sec 500
Port: 443: 334 KB/sec 13 KB/sec 356 KB/sec 500
Port: 443: 322 KB/sec 12 KB/sec 343 KB/sec 500
Port: 7255: 283 KB/sec 11 KB/sec 303 KB/sec 500
Port: 7255: 282 KB/sec 13 KB/sec 318 KB/sec 500
Port: 7003: 296 KB/sec 12 KB/sec 323 KB/sec 500
Port: 7003: 304 KB/sec 12 KB/sec 331 KB/sec 500
Port: 7202: 338 KB/sec 12 KB/sec 357 KB/sec 500
Port: 7202: 555 KB/sec 21 KB/sec 588 KB/sec 500
Port: 7499: 283 KB/sec 13 KB/sec 320 KB/sec 500
Port: 7499: 336 KB/sec 12 KB/sec 355 KB/sec 500
Port: 80: 255 KB/sec 11 KB/sec 282 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit