today I have had issues with the server either rubber-banding and disconnecting. Here is my tracert and ping to the patchserver;
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\>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 [192.168.1.1]
2 11 ms 14 ms 11 ms ***.***.***.***
3 15 ms 10 ms 12 ms te-9-1-ur01.nlittlerock.ar.lrock.comcast.net [68
.85.132.13]
4 18 ms 11 ms 17 ms te-9-1-ar02.littlerock.ar.lrock.comcast.net [68.
87.223.173]
5 21 ms 21 ms 28 ms te-0-0-0-6-cr01.dallas.tx.ibone.comcast.net [68.
86.91.41]
6 23 ms 23 ms 21 ms he-0-11-0-1-pe03.1950stemmons.tx.ibone.comcast.n
et [68.86.86.130]
7 17 ms 37 ms 18 ms 173-167-56-166-static.hfc.comcastbusiness.net [1
73.167.56.166]
8 28 ms 23 ms 20 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
9 74 ms 29 ms 34 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46
.217]
10 52 ms 41 ms 43 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
11 116 ms 64 ms 58 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43
.202]
12 57 ms 57 ms 61 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 74 ms 70 ms 70 ms 38.111.40.114
14 62 ms 57 ms 111 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\>ping patchserver.crypticstudios.com
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=69ms TTL=45
Reply from 208.95.185.41: bytes=32 time=57ms TTL=45
Reply from 208.95.185.41: bytes=32 time=110ms TTL=45
Reply from 208.95.185.41: bytes=32 time=132ms TTL=45
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 132ms, Average = 92ms
C:\>
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
today I have had issues with the server either rubber-banding and disconnecting. Here is my tracert and ping to the patchserver;
....
Now your 'Ping' and 'Trace Route' results are under the recommended upper limit of 180ms for network latency, but they look suspicious just on their spread of response time...
What we need here is the 'Net Test' results, which measures sustained connection throughput, as well as the 'Path Ping' results (use the command 'pathping' which uses the same syntax as the 'tracert' command...) and post those diagnostic results to provide further information on what is causing your problem...
net test results I have a feeling I'm going to have a few words with Comcast.
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
net test results I have a feeling I'm going to have a few words with Comcast.
The 'Net Test' results do show that you have a connection quality issue. Now the next question to ask is who is causing this ... Comcast or Cogent ??? This is what the 'Path Ping' diagnostics will show...
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
just now realized auto correct kicked in on the title lol meant for it to say Rubber-Banding. XD not underbidding lol.
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
ohh goody... haven't gotten on to Comcast in a long time
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
thanks for helping with this grouchyotaku, I've submitted a ticket to Cryptic, to be honest I've never used the Path Ping command before. Some things they never teach you in CCNA. Hopefully I can get all this fixed up soon.
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
Трассировка маршрута к patchserver.crypticstudios.com [208.95.185.41]
с максимальным числом прыжков 30:
1 <1 мс <1 мс <1 мс 192.168.1.1
2 1 ms <1 мс <1 мс comp35-46.2day.kz [80.241.35.46]
3 1 ms 1 ms 1 ms 172.30.31.177
4 1 ms 1 ms 1 ms CRT01.KRG.tnsplus.kz [80.241.35.197]
5 1 ms 1 ms 1 ms 46.227.189.37
6 67 ms 67 ms 67 ms 77.41.151.61
7 84 ms 84 ms 84 ms xe-1-0-1-beeline1.skt.cw.net [166.63.220.181]
8 108 ms 107 ms 107 ms ae10-xcr1.amt.cw.net [195.2.30.162]
9 108 ms 109 ms 108 ms te0-7-0-8.rcr21.ams05.atlas.cogentco.com [130.117.15.197]
10 110 ms 110 ms 110 ms be2039.ccr42.ams03.atlas.cogentco.com [154.54.36.145]
11 122 ms 121 ms 122 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
12 192 ms 191 ms 191 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
13 244 ms 206 ms 203 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 193 ms 197 ms 197 ms 38.111.40.114
15 193 ms 195 ms 193 ms patchserver2.crypticstudios.com [208.95.185.41]
Now in addition to bad packet drop along the Cogent backbone, (which you should issue a ticket for with Cogent/PWE), the 'Path Ping' diagnostic is also showing packet drop in the local network that modem/gateway plugs into, which is a problem with your local ISP, whom you should contact to get fixed...
I am having major disconnection problems and I am not sure what the issue is
Here is my Traceroute:
1 22 ms 16 ms 14 ms 10.138.128.1
2 36 ms 229 ms 98 ms 172.30.16.1
3 36 ms 38 ms 70 ms 172.30.12.57
4 38 ms 39 ms 37 ms 12.249.197.9
5 42 ms 42 ms 51 ms cr81.sj2ca.ip.att.net [12.122.110.110]
6 43 ms 45 ms 49 ms cr1.sffca.ip.att.net [12.122.1.117]
7 166 ms 80 ms 172 ms ggr4.sffca.ip.att.net [12.122.86.197]
8 53 ms 54 ms 53 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11
.45]
9 53 ms 55 ms 52 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
10 53 ms 59 ms 54 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
.33]
11 88 ms 88 ms 87 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
.54]
12 108 ms 106 ms 113 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 121 ms 166 ms 124 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
14 121 ms 122 ms 123 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 122 ms 125 ms 125 ms 38.111.40.114
16 123 ms 125 ms 120 ms patchserver2.crypticstudios.com [208.95.185.41]
I'm also having major lag/connection problems for the first time since I'm playing STO. I've played it on the same system in the UK in France and now in Bulgaria and I've never had problems until that very moment. Here is my trace:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 3 ms **.***.***.*
3 * * 6 ms 212.39.69.209
4 2 ms 1 ms 4 ms sfia-b2-link.telia.net [213.248.85.217]
5 31 ms 65 ms 29 ms prag-bb1-link.telia.net [80.91.247.82]
6 52 ms 50 ms 51 ms ffm-bb1-link.telia.net [62.115.139.219]
7 62 ms 46 ms 47 ms ffm-b12-link.telia.net [80.91.246.103]
8 49 ms 51 ms 49 ms be100.agr21.fra03.atlas.cogentco.com [130.117.14
.89]
9 49 ms 49 ms 49 ms be2188.ccr42.fra03.atlas.cogentco.com [130.117.4
8.114]
10 54 ms 55 ms 53 ms be2262.ccr42.ams03.atlas.cogentco.com [154.54.37
.33]
11 53 ms 53 ms 52 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
12 128 ms 127 ms 130 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
.165]
13 179 ms 217 ms 218 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 132 ms 128 ms * 38.111.40.114
15 123 ms 128 ms 123 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Here's a ping:
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=125ms TTL=53
Reply from 208.95.185.41: bytes=32 time=123ms TTL=53
Reply from 208.95.185.41: bytes=32 time=123ms TTL=53
Reply from 208.95.185.41: bytes=32 time=125ms TTL=53
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 125ms, Average = 124ms
I am having major disconnection problems and I am not sure what the issue is
Here is my Traceroute:
1 22 ms 16 ms 14 ms 10.138.128.1
2 36 ms 229 ms 98 ms 172.30.16.1
3 36 ms 38 ms 70 ms 172.30.12.57
4 38 ms 39 ms 37 ms 12.249.197.9
5 42 ms 42 ms 51 ms cr81.sj2ca.ip.att.net [12.122.110.110]
6 43 ms 45 ms 49 ms cr1.sffca.ip.att.net [12.122.1.117]
7 166 ms 80 ms 172 ms ggr4.sffca.ip.att.net [12.122.86.197]
8 53 ms 54 ms 53 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11
.45]
9 53 ms 55 ms 52 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
10 53 ms 59 ms 54 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
.33]
11 88 ms 88 ms 87 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
.54]
12 108 ms 106 ms 113 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 121 ms 166 ms 124 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
14 121 ms 122 ms 123 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 122 ms 125 ms 125 ms 38.111.40.114
16 123 ms 125 ms 120 ms patchserver2.crypticstudios.com [208.95.185.41]
If someone can help me figure out what is wrong I would appreciate it
Your 'Trace Route' results are all under the recommended upper limit of 180ms for network latency, so network latency is not the issue here...
And your 'Net Test' results show that you can't maintain the 300 - 500 KB/sec (or better) sustained network throughput on your connections, which indicates you have a connection quality issue of some kind. And since 'Net Test' talks to a simple diagnostic server located on the same local network as the STO servers, this shows that the connection quality issue is unrelated to the STO servers, since their out of the picture with this diagnostics...
To find out what is causing the connection quality issue, we need the 'Path Ping' diagnostic results... (use the Windows command 'pathping' which has the same syntax as the 'tracert' command...)
I'm also having major lag/connection problems for the first time since I'm playing STO. I've played it on the same system in the UK in France and now in Bulgaria and I've never had problems until that very moment. Here is my trace:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 3 ms **.***.***.*
3 * * 6 ms 212.39.69.209
4 2 ms 1 ms 4 ms sfia-b2-link.telia.net [213.248.85.217]
5 31 ms 65 ms 29 ms prag-bb1-link.telia.net [80.91.247.82]
6 52 ms 50 ms 51 ms ffm-bb1-link.telia.net [62.115.139.219]
7 62 ms 46 ms 47 ms ffm-b12-link.telia.net [80.91.246.103]
8 49 ms 51 ms 49 ms be100.agr21.fra03.atlas.cogentco.com [130.117.14
.89]
9 49 ms 49 ms 49 ms be2188.ccr42.fra03.atlas.cogentco.com [130.117.4
8.114]
10 54 ms 55 ms 53 ms be2262.ccr42.ams03.atlas.cogentco.com [154.54.37
.33]
11 53 ms 53 ms 52 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
12 128 ms 127 ms 130 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
.165]
13 179 ms 217 ms 218 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 132 ms 128 ms * 38.111.40.114
15 123 ms 128 ms 123 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
...
Looks like you have an issue with the Cogent Boston Hub (which appears to be a common problem for EU connections at the moment... 180ms is the recommended upper limit for network latency) There could be other problems, but we would need the 'Path Ping' result to spot them (use the Windows command 'pathping' which has the same syntax as the 'tracert' command)
Other then filing a ticket so the Cryptic/PWE can kick Cogent a few more times to get the problems fixed, the only other thing you could try is to use the US Proxy setting in the Launcher Options menu, but doing this is really an act of desperation, and is not guaranteed to work...
Looks like you have an issue with the Cogent Boston Hub (which appears to be a common problem for EU connections at the moment... 180ms is the recommended upper limit for network latency) There could be other problems, but we would need the 'Path Ping' result to spot them (use the Windows command 'pathping' which has the same syntax as the 'tracert' command)
Other then filing a ticket so the Cryptic/PWE can kick Cogent a few more times to get the problems fixed, the only other thing you could try is to use the US Proxy setting in the Launcher Options menu, but doing this is really an act of desperation, and is not guaranteed to work...
I'll also file a ticket, but what's the thing with the proxy? How can I set it up?
Again, this looks like a issue that starts with the Cogent Boston Hub, (a ongoing theme the past few days...)
in the 'Options' Menu of the Launcher, there are settings for both the 'Patch' and 'Gameplay' Proxy setting, (you will need to scroll down the menu to see both...)
Comments
Now your 'Ping' and 'Trace Route' results are under the recommended upper limit of 180ms for network latency, but they look suspicious just on their spread of response time...
What we need here is the 'Net Test' results, which measures sustained connection throughput, as well as the 'Path Ping' results (use the command 'pathping' which uses the same syntax as the 'tracert' command...) and post those diagnostic results to provide further information on what is causing your problem...
'Net Test' diagnostics are described in this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
The 'Net Test' results do show that you have a connection quality issue. Now the next question to ask is who is causing this ... Comcast or Cogent ??? This is what the 'Path Ping' diagnostics will show...
(c) 2013 Microsoft Corporation. All rights reserved.
C:\>pathping patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 My Computer.hsd1.ar.comcast.net. [192.168.1.112]
1 CISCO17529 [192.168.1.1]
2 ***.***.***.***
3 te-9-1-ur01.nlittlerock.ar.lrock.comcast.net [68.85.132.13]
4 te-9-1-ar02.littlerock.ar.lrock.comcast.net [68.87.223.173]
5 te-0-0-0-6-cr01.dallas.tx.ibone.comcast.net [68.86.91.41]
6 he-0-11-0-1-pe03.1950stemmons.tx.ibone.comcast.net [68.86.86.130]
7 as174-pe01.1950stemmons.tx.ibone.comcast.net [75.149.230.150]
8 be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.53]
9 be2010.ccr22.mci01.atlas.cogentco.com [154.54.46.217]
10 be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
11 be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202]
12 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
13 38.111.40.114
14 patchserver2.crypticstudios.com [208.95.185.41]
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 My Computer.hsd1.ar.comcast.net.
[192.168.1.112]
0/ 100 = 0% |
1 18ms 0/ 100 = 0% 0/ 100 = 0% CISCO17529 [192.168.1.1]
0/ 100 = 0% |
2 32ms 0/ 100 = 0% 0/ 100 = 0% ***.***.***.***
0/ 100 = 0% |
3 34ms 2/ 100 = 2% 2/ 100 = 2% te-9-1-ur01.nlittlerock.ar.lrock.c
omcast.net [68.85.132.13]
0/ 100 = 0% |
4 43ms 1/ 100 = 1% 1/ 100 = 1% te-9-1-ar02.littlerock.ar.lrock.co
mcast.net [68.87.223.173]
0/ 100 = 0% |
5 47ms 0/ 100 = 0% 0/ 100 = 0% te-0-0-0-6-cr01.dallas.tx.ibone.co
mcast.net [68.86.91.41]
0/ 100 = 0% |
6 52ms 0/ 100 = 0% 0/ 100 = 0% he-0-11-0-1-pe03.1950stemmons.tx.i
bone.comcast.net [68.86.86.130]
0/ 100 = 0% |
7 48ms 0/ 100 = 0% 0/ 100 = 0% as174-pe01.1950stemmons.tx.ibone.c
omcast.net [75.149.230.150]
0/ 100 = 0% |
8 46ms 1/ 100 = 1% 1/ 100 = 1% be2032.ccr22.dfw01.atlas.cogentco.
com [154.54.6.53]
0/ 100 = 0% |
9 53ms 2/ 100 = 2% 2/ 100 = 2% be2010.ccr22.mci01.atlas.cogentco.
com [154.54.46.217]
0/ 100 = 0% |
10 72ms 0/ 100 = 0% 0/ 100 = 0% be2157.ccr42.ord01.atlas.cogentco.
com [154.54.6.118]
0/ 100 = 0% |
11 106ms 0/ 100 = 0% 0/ 100 = 0% be2138.ccr22.bos01.atlas.cogentco.
com [154.54.43.202]
0/ 100 = 0% |
12 130ms 1/ 100 = 1% 1/ 100 = 1% te3-2.ccr01.bos06.atlas.cogentco.c
om [154.54.46.130]
0/ 100 = 0% |
13 102ms 1/ 100 = 1% 1/ 100 = 1% 38.111.40.114
0/ 100 = 0% |
14 110ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
08.95.185.41]
Trace complete.
C:\>
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
All right, 'Path Ping' says that BOTH Comcast and Cogent are causing the problem.
Contact the Comcast Tech Support, as you should not be having ANY 'dropped packets' in the local network your Cable Modem plugs into...
And open a ticket with Cryptic/PWE so they can kick Cogent a few more times to get their connections looked into...
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
10 --- 100/ 100 =100% 100/ 100 =100% be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
Greywolf Taskforce - Officer of the Fleet
"I rather believe that time is a companion who goes with us on the journey, and reminds us to cherish every moment... because they'll never come again. What we leave behind is not as important as how we lived" Picard to Riker
Трассировка маршрута к patchserver.crypticstudios.com [208.95.185.41]
с максимальным числом прыжков 30:
1 <1 мс <1 мс <1 мс 192.168.1.1
2 1 ms <1 мс <1 мс comp35-46.2day.kz [80.241.35.46]
3 1 ms 1 ms 1 ms 172.30.31.177
4 1 ms 1 ms 1 ms CRT01.KRG.tnsplus.kz [80.241.35.197]
5 1 ms 1 ms 1 ms 46.227.189.37
6 67 ms 67 ms 67 ms 77.41.151.61
7 84 ms 84 ms 84 ms xe-1-0-1-beeline1.skt.cw.net [166.63.220.181]
8 108 ms 107 ms 107 ms ae10-xcr1.amt.cw.net [195.2.30.162]
9 108 ms 109 ms 108 ms te0-7-0-8.rcr21.ams05.atlas.cogentco.com [130.117.15.197]
10 110 ms 110 ms 110 ms be2039.ccr42.ams03.atlas.cogentco.com [154.54.36.145]
11 122 ms 121 ms 122 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
12 192 ms 191 ms 191 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
13 244 ms 206 ms 203 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 193 ms 197 ms 197 ms 38.111.40.114
15 193 ms 195 ms 193 ms patchserver2.crypticstudios.com [208.95.185.41]
Трассировка завершена.
Трассировка маршрута к patchserver.crypticstudios.com [208.95.185.41]
с максимальным числом прыжков 30:
0 Warriorx-PC [192.168.1.102]
1 192.168.1.1
2 comp35-46.2day.kz [80.241.35.46]
3 172.30.31.177
4 CRT01.KRG.tnsplus.kz [80.241.35.197]
5 46.227.189.37
6 77.41.151.61
7 xe-1-0-1-beeline1.skt.cw.net [166.63.220.181]
8 ae10-xcr1.amt.cw.net [195.2.30.162]
9 te0-7-0-8.rcr21.ams05.atlas.cogentco.com [130.117.15.197]
10 be2039.ccr42.ams03.atlas.cogentco.com [154.54.36.145]
11 be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
12 be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
13 te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 38.111.40.114
15 patchserver2.crypticstudios.com [208.95.185.41]
Подсчет статистики за: 375 сек. ...
Исходный узел Маршрутный узел
Прыжок RTT Утер./Отпр. % Утер./Отпр. % Адрес
0 Warriorx-PC [192.168.1.102]
0/ 100 = 0% |
1 0мс 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 0мс 0/ 100 = 0% 0/ 100 = 0% comp35-46.2day.kz [80.241.35.46]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 172.30.31.177
0/ 100 = 0% |
4 1мс 0/ 100 = 0% 0/ 100 = 0% CRT01.KRG.tnsplus.kz [80.241.35.197]
0/ 100 = 0% |
5 2мс 0/ 100 = 0% 0/ 100 = 0% 46.227.189.37
0/ 100 = 0% |
6 68мс 0/ 100 = 0% 0/ 100 = 0% 77.41.151.61
0/ 100 = 0% |
7 88мс 0/ 100 = 0% 0/ 100 = 0% xe-1-0-1-beeline1.skt.cw.net [166.63.220.181]
0/ 100 = 0% |
8 108мс 0/ 100 = 0% 0/ 100 = 0% ae10-xcr1.amt.cw.net [195.2.30.162]
1/ 100 = 1% |
9 --- 100/ 100 =100% 99/ 100 = 99% te0-7-0-8.rcr21.ams05.atlas.cogentco.com [130.117.15.
197]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% be2039.ccr42.ams03.atlas.cogentco.com [154.54.36.145]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% 38.111.40.114
0/ 100 = 0% |
15 193мс 1/ 100 = 1% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]
Трассировка завершена.
Nettest
unable to allocate performance buffer
contacting nettest server..
Local IP: 85.29.187.197
Ping: 200.0 msec
Port: 80: 4 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 27 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 31 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 30 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 5 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 6 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 76 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 93 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 80 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 4 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 5 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 5 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 37 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
DNS hostname clearly shows that this belongs to Cogent Communications...
Now in addition to bad packet drop along the Cogent backbone, (which you should issue a ticket for with Cogent/PWE), the 'Path Ping' diagnostic is also showing packet drop in the local network that modem/gateway plugs into, which is a problem with your local ISP, whom you should contact to get fixed...
Here is my Traceroute:
1 22 ms 16 ms 14 ms 10.138.128.1
2 36 ms 229 ms 98 ms 172.30.16.1
3 36 ms 38 ms 70 ms 172.30.12.57
4 38 ms 39 ms 37 ms 12.249.197.9
5 42 ms 42 ms 51 ms cr81.sj2ca.ip.att.net [12.122.110.110]
6 43 ms 45 ms 49 ms cr1.sffca.ip.att.net [12.122.1.117]
7 166 ms 80 ms 172 ms ggr4.sffca.ip.att.net [12.122.86.197]
8 53 ms 54 ms 53 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11
.45]
9 53 ms 55 ms 52 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
10 53 ms 59 ms 54 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
.33]
11 88 ms 88 ms 87 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
.54]
12 108 ms 106 ms 113 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 121 ms 166 ms 124 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
14 121 ms 122 ms 123 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 122 ms 125 ms 125 ms 38.111.40.114
16 123 ms 125 ms 120 ms patchserver2.crypticstudios.com [208.95.185.41]
And Here is the results of the nettest
Local IP: 173.25.4.129
Ping: 136.4 msec
Port: 80: 590 KB/sec 22 KB/sec 620 KB/sec 500
Port: 80: 125 KB/sec 7 KB/sec 133 KB/sec 500
Port: 443: 550 KB/sec 22 KB/sec 580 KB/sec 500
Port: 443: 563 KB/sec 20 KB/sec 592 KB/sec 500
Port: 7255: 562 KB/sec 21 KB/sec 594 KB/sec 500
Port: 7255: 569 KB/sec 21 KB/sec 599 KB/sec 500
Port: 7003: 151 KB/sec 8 KB/sec 161 KB/sec 500
Port: 7003: 342 KB/sec 14 KB/sec 361 KB/sec 500
Port: 7202: 532 KB/sec 19 KB/sec 561 KB/sec 500
Port: 7202: 570 KB/sec 20 KB/sec 599 KB/sec 500
Port: 7499: 550 KB/sec 19 KB/sec 579 KB/sec 500
Port: 7499: 213 KB/sec 9 KB/sec 225 KB/sec 500
Port: 80: 606 KB/sec 22 KB/sec 638 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 1 KB/sec
If someone can help me figure out what is wrong I would appreciate it
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.1
2 3 ms 2 ms 3 ms **.***.***.*
3 * * 6 ms 212.39.69.209
4 2 ms 1 ms 4 ms sfia-b2-link.telia.net [213.248.85.217]
5 31 ms 65 ms 29 ms prag-bb1-link.telia.net [80.91.247.82]
6 52 ms 50 ms 51 ms ffm-bb1-link.telia.net [62.115.139.219]
7 62 ms 46 ms 47 ms ffm-b12-link.telia.net [80.91.246.103]
8 49 ms 51 ms 49 ms be100.agr21.fra03.atlas.cogentco.com [130.117.14
.89]
9 49 ms 49 ms 49 ms be2188.ccr42.fra03.atlas.cogentco.com [130.117.4
8.114]
10 54 ms 55 ms 53 ms be2262.ccr42.ams03.atlas.cogentco.com [154.54.37
.33]
11 53 ms 53 ms 52 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
12 128 ms 127 ms 130 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
.165]
13 179 ms 217 ms 218 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 132 ms 128 ms * 38.111.40.114
15 123 ms 128 ms 123 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Here's a ping:
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=125ms TTL=53
Reply from 208.95.185.41: bytes=32 time=123ms TTL=53
Reply from 208.95.185.41: bytes=32 time=123ms TTL=53
Reply from 208.95.185.41: bytes=32 time=125ms TTL=53
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 125ms, Average = 124ms
Any suggestions?
Your 'Trace Route' results are all under the recommended upper limit of 180ms for network latency, so network latency is not the issue here...
And your 'Net Test' results show that you can't maintain the 300 - 500 KB/sec (or better) sustained network throughput on your connections, which indicates you have a connection quality issue of some kind. And since 'Net Test' talks to a simple diagnostic server located on the same local network as the STO servers, this shows that the connection quality issue is unrelated to the STO servers, since their out of the picture with this diagnostics...
To find out what is causing the connection quality issue, we need the 'Path Ping' diagnostic results... (use the Windows command 'pathping' which has the same syntax as the 'tracert' command...)
Looks like you have an issue with the Cogent Boston Hub (which appears to be a common problem for EU connections at the moment... 180ms is the recommended upper limit for network latency) There could be other problems, but we would need the 'Path Ping' result to spot them (use the Windows command 'pathping' which has the same syntax as the 'tracert' command)
Other then filing a ticket so the Cryptic/PWE can kick Cogent a few more times to get the problems fixed, the only other thing you could try is to use the US Proxy setting in the Launcher Options menu, but doing this is really an act of desperation, and is not guaranteed to work...
Here's the 'Path Ping':
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 dek-PC [192.168.0.100]
1 192.168.0.1
2 82.137.110.1
3 212.39.69.209
4 sfia-b2-link.telia.net [213.248.85.217]
5 prag-bb1-link.telia.net [80.91.247.82]
6 ffm-bb1-link.telia.net [62.115.139.219]
7 ffm-b12-link.telia.net [213.155.136.197]
8 be100.agr21.fra03.atlas.cogentco.com [130.117.14.89]
9 be2188.ccr42.fra03.atlas.cogentco.com [130.117.48.114]
10 be2262.ccr42.ams03.atlas.cogentco.com [154.54.37.33]
11 be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
12 be2387.ccr22.bos01.atlas.cogentco.com [154.54.44.165]
13 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
14 38.111.40.114
15 patchserver2.crypticstudios.com [208.95.185.41]
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 dek-PC [192.168.0.100]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 82.137.110.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% 212.39.69.209
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% sfia-b2-link.telia.net [213.248.85
.217]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% prag-bb1-link.telia.net [80.91.247
.82]
0/ 100 = 0% |
6 57ms 0/ 100 = 0% 0/ 100 = 0% ffm-bb1-link.telia.net [62.115.139
.219]
0/ 100 = 0% |
7 49ms 0/ 100 = 0% 0/ 100 = 0% ffm-b12-link.telia.net [213.155.13
6.197]
0/ 100 = 0% |
8 41ms 0/ 100 = 0% 0/ 100 = 0% be100.agr21.fra03.atlas.cogentco.c
om [130.117.14.89]
0/ 100 = 0% |
9 45ms 0/ 100 = 0% 0/ 100 = 0% be2188.ccr42.fra03.atlas.cogentco.
com [130.117.48.114]
0/ 100 = 0% |
10 60ms 0/ 100 = 0% 0/ 100 = 0% be2262.ccr42.ams03.atlas.cogentco.
com [154.54.37.33]
0/ 100 = 0% |
11 56ms 0/ 100 = 0% 0/ 100 = 0% be2183.ccr22.lpl01.atlas.cogentco.
com [154.54.58.69]
1/ 100 = 1% |
12 125ms 3/ 100 = 3% 2/ 100 = 2% be2387.ccr22.bos01.atlas.cogentco.
com [154.54.44.165]
0/ 100 = 0% |
13 165ms 1/ 100 = 1% 0/ 100 = 0% te3-2.ccr01.bos06.atlas.cogentco.c
om [154.54.46.130]
2/ 100 = 2% |
14 130ms 3/ 100 = 3% 0/ 100 = 0% 38.111.40.114
0/ 100 = 0% |
15 125ms 3/ 100 = 3% 0/ 100 = 0% patchserver2.crypticstudios.com [2
08.95.185.41]
Trace complete.
I'll also file a ticket, but what's the thing with the proxy? How can I set it up?
Again, this looks like a issue that starts with the Cogent Boston Hub, (a ongoing theme the past few days...)
in the 'Options' Menu of the Launcher, there are settings for both the 'Patch' and 'Gameplay' Proxy setting, (you will need to scroll down the menu to see both...)