Hey in the launcher pop up box,look for the options tab and scroll down where it says something like gameplay proxy and select EU, I had to do that this past weekend and I was able to play,when I used auto and US the game was unplayable.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 12 ms 13 ms 172.30.76.209
4 41 ms 14 ms 20 ms 172.30.32.65
5 74 ms 51 ms 73 ms 12.94.104.73
6 25 ms 27 ms 27 ms cr2.attga.ip.att.net [12.122.140.170]
7 26 ms 25 ms 23 ms 12.122.140.245
8 24 ms 26 ms 24 ms te0-7-0-7.ccr21.atl02.atlas.cogentco.com [154.54
.13.41]
9 46 ms 38 ms 39 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.
161]
10 45 ms 43 ms 43 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
11 50 ms 49 ms 50 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
12 47 ms 49 ms 50 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 52 ms 53 ms 52 ms 38.111.40.114
14 49 ms 49 ms 51 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.NYCMNY-VFTTP-236.verizon-gni.net [108.6.14.
1]
3 4 ms 3 ms 3 ms G0-14-2-4.NYCMNY-LCR-22.verizon-gni.net [130.81.
180.96]
4 7 ms 28 ms 2 ms ae4-0.NY5030-BB-RTR2.verizon-gni.net [130.81.163
.232]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 10 ms 10 ms 0.ae1.XL4.BOS4.ALTER.NET [140.222.226.15]
8 9 ms 10 ms 10 ms 0.ge-9-1-0.GW15.BOS4.ALTER.NET [152.63.24.46]
9 10 ms 9 ms 9 ms internap-gw.customer.alter.net [152.179.134.214]
10 11 ms 9 ms 9 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 21 ms 17 ms 17 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 10 ms 9 ms 9 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 5 ms 4 ms 192.168.1.1
2 12 ms 11 ms 13 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53.
0.1]
3 13 ms 11 ms 13 ms 50.126.112.37
4 17 ms 17 ms 17 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2
17]
5 17 ms 17 ms 17 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2
21]
6 17 ms 38 ms 17 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
22]
7 17 ms 17 ms 18 ms 206.111.7.149.ptr.us.xo.net [206.111.7.149]
8 101 ms 101 ms 103 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 106 ms 105 ms 104 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 106 ms 107 ms 102 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 100 ms 97 ms 97 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
12 107 ms 106 ms 110 ms 209.117.103.10
13 107 ms 107 ms 107 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 118 ms * 998 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 110 ms 108 ms 107 ms patchserver2.crypticstudios.com [208.95.185.41]
I can't believe the people would post their own IP address on a public website! You know these are crawled by bots every day looking for this information? You'd better hope to God your firewall is working properly and you don't have any open ports that someone could hack you with! People, don't put your public IP addresses in plain sight! This should be a warning in the original thread!
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 22 ms 22 ms 51 ms ptld-dsl-gw50.ptld.qwest.net [207.225.84.50]
3 22 ms 23 ms 24 ms ptld-agw1.inet.qwest.net [207.225.86.137]
4 104 ms 103 ms 106 ms bst-edge-05.inet.qwest.net [67.14.30.130]
5 104 ms 105 ms 105 ms 65.120.117.250
6 105 ms 105 ms 105 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
7 121 ms 108 ms 111 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
8 110 ms 109 ms 109 ms patchserver2.crypticstudios.com [208.95.185.41]
I can't believe the people would post their own IP address on a public website! You know these are crawled by bots every day looking for this information? You'd better hope to God your firewall is working properly and you don't have any open ports that someone could hack you with! People, don't put your public IP addresses in plain sight! This should be a warning in the original thread!
They really should. But people are desperate for advice and as ever, are kept hanging with no help. Several of us have been told to post in here with concrete info in order to get things resolved and despite doing so, are still left hanging.
Im having horrid rubber banding. The game plays perfect for about 5-10 seconds and then stops for 3-5 seconds. Ive reinstalled the game, updated graphics drivers, used ethernet cables instead of wifi and its always the same. Heres my results..............
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms
3 8 ms 14 ms 5 ms c13-access-vlan.so.fastcom.ie [77.95.164.1]
4 4 ms 9 ms 8 ms c11-v6-nb-c13.fastcom.ie [77.95.165.117]
5 12 ms 19 ms 11 ms c3-v4-m5-so.fastcom.ie [83.245.74.9]
6 22 ms 11 ms 11 ms c6-v6-so.fastcom.ie [83.245.74.58]
7 11 ms 22 ms 15 ms c1-v7-so.fastcom.ie [83.245.74.41]
8 13 ms 10 ms 12 ms s1-v9-so.fastcom.ie [83.245.74.5]
9 23 ms 39 ms 21 ms r1-v8-so.fastcom.ie [83.245.74.1]
10 30 ms 19 ms 16 ms 149.11.37.49
11 * 22 ms 18 ms te2-6.ccr01.dub02.atlas.cogentco.com [154.25.1.2
45]
12 20 ms 21 ms 25 ms te7-7.ccr01.dub01.atlas.cogentco.com [154.54.56.
49]
13 29 ms 31 ms * te0-5-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.45.226]
14 89 ms 93 ms 93 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
15 171 ms 216 ms 209 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 97 ms 88 ms 91 ms 38.111.40.114
17 * 142 ms 87 ms patchserver2.crypticstudios.com [208.95.185.41]
Im having horrid rubber banding. The game plays perfect for about 5-10 seconds and then stops for 3-5 seconds. Ive reinstalled the game, updated graphics drivers, used ethernet cables instead of wifi and its always the same. Heres my results..............
Please help!!!
Its most likely that the problem is being caused by network congestion in one of the Internet Backbone providers (e.g. most likely Cogent Communications..)
Have you tried using the 'Proxy' options in the Launcher Option Menu, as this may, or may not help relieve the problem...
Its most likely that the problem is being caused by network congestion in one of the Internet Backbone providers (e.g. most likely Cogent Communications..)
Have you tried using the 'Proxy' options in the Launcher Option Menu, as this may, or may not help relieve the problem...
Thanks for the response. I switched from the EU server to the US server. I actually thought it done the trick but the lag returned worst than ever after about 10 minutes
Been having major lag the past couple of days. Now I can't get even past the character selection screen. I have no problem playing other online games like Guild Wars 2 but having major issue with STO. Here is the info requested.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 9 ms 11 ms 8 ms cm1.zeta184.maxonline.com.sg [TRIBBLE.xx.TRIBBLE.x]
3 9 ms 8 ms 7 ms cm1.zeta184.maxonline.com.sg [TRIBBLE.xx.TRIBBLE.x]
4 6 ms 7 ms 6 ms 172.20.52.69
5 8 ms 13 ms 11 ms 172.26.52.5
6 10 ms 11 ms 11 ms 172.20.7.98
7 15 ms 15 ms 14 ms 203.117.34.73
8 11 ms 11 ms 11 ms six2asr9kts01.starhub.net.sg [203.117.34.9]
9 12 ms 11 ms 12 ms 203.117.34.38
10 12 ms 32 ms 14 ms 203.116.61.118
11 * * * Request timed out.
12 263 ms 280 ms 265 ms 65.120.117.250
13 268 ms 266 ms 265 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 272 ms 269 ms 269 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 268 ms 265 ms 267 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 8 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 4 ms 4 ms 4 ms 174.251.40.189.isp.timbrasil.com.br [189.40.251.
3 4 ms 4 ms 4 ms 10.223.10.33
4 8 ms 11 ms 11 ms 10.223.238.225
5 10 ms 6 ms 6 ms 10.223.238.46
6 8 ms 6 ms 6 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.144
7 106 ms 106 ms 106 ms xe-0-0-1.miami15.mia.seabone.net [195.22.199.101
8 107 ms 107 ms 107 ms te0-0-0-4.ccr21.mia03.atlas.cogentco.com [154.54
9 107 ms 107 ms 107 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80
10 149 ms 148 ms 148 ms be2122.ccr21.atl01.atlas.cogentco.com [154.54.24
11 138 ms 138 ms 138 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
12 138 ms 138 ms 138 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
13 145 ms 145 ms 145 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
14 145 ms 146 ms 145 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
15 147 ms 144 ms 157 ms 38.111.40.114
16 145 ms 145 ms 145 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 10 ms 4 ms 4 ms 174.251.40.189.isp.timbrasil.com.br [189.40.25
3 4 ms 4 ms 4 ms 10.223.10.33
4 8 ms 11 ms 11 ms 10.223.229.49
5 4 ms 6 ms 6 ms 10.223.238.50
6 7 ms 6 ms 7 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.1
7 106 ms 106 ms 106 ms xe-0-0-1.miami15.mia.seabone.net [195.22.199.1
8 107 ms 109 ms 107 ms te0-7-0-34.ccr21.mia03.atlas.cogentco.com [154
9 107 ms 107 ms 107 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.
10 151 ms 151 ms 151 ms be2124.mpd21.atl01.atlas.cogentco.com [154.54.
11 139 ms 139 ms 139 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.
12 139 ms 139 ms 139 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.
13 144 ms 144 ms 144 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.
14 145 ms 145 ms 145 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.
15 150 ms 144 ms 157 ms 38.111.40.114
16 145 ms 145 ms 145 ms us1.proxy.crypticstudios.com [208.95.184.152]
Setting the game proxy for Europe. The game is more stable, but I get ping of 450ms.
Tracing route to eu1.proxy.crypticstudios.com [79.125.3.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 6 ms 82 ms 29 ms 174.251.40.189.isp.timbrasil.com.br [189.40.251.174]
3 4 ms 4 ms 4 ms 10.223.10.34
4 12 ms 11 ms 11 ms 10.223.238.217
5 11 ms 7 ms 7 ms 10.223.238.50
6 6 ms 7 ms 7 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.144.160.41]
7 213 ms 213 ms 213 ms xe-7-1-0.londra32.lon.seabone.net [195.22.209.105]
8 217 ms 217 ms 217 ms amazon.londra32.lon.seabone.net [89.221.43.103]
9 240 ms 242 ms 240 ms 176.32.106.6
10 231 ms 231 ms 231 ms 176.32.106.16
11 242 ms 242 ms 242 ms 178.236.0.99
12 247 ms 247 ms 247 ms 178.236.0.128
13 269 ms 233 ms 233 ms 178.236.0.125
14 239 ms 239 ms 242 ms ec2-79-125-0-137.eu-west-1.compute.amazonaws.com [79.125.0.137]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 244 ms 239 ms 240 ms ec2-79-125-3-30.eu-west-1.compute.amazonaws.com [79.125.3.30]
What does it mean when tracert reports an * instead of a number? I'm getting that for some.
Also, nettest starts with "unable to allocate performance buffer", reports only 0 for the second and third columns, and becomes unresponsive at port 7003.
What does it mean when tracert reports an * instead of a number? I'm getting that for some.
Also, nettest starts with "unable to allocate performance buffer", reports only 0 for the second and third columns, and becomes unresponsive at port 7003.
A '*' means the router node is not responding, which could be caused by a variety of reasons, such as the node is not configured to support ICMP/IP Diagnostic packets, or too much network traffic to respond...
Now if 'Net Test' can't allocate a buffer, this means there is something wrong with your own computer, such as running out of memory due to memory leaks, too many networked applications and processes running, etc. Try rebooting your computer, then run Nettest with nothing else running...
This one is from south africa, pietermaritzburg via one computer, ill post the other one later
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 19 ms 14 ms 8 ms ti-224-164-01.telkomadsl.co.za [105.224.164.1]
3 17 ms 24 ms 16 ms 105.229.0.6
4 17 ms 16 ms 21 ms 105.229.0.29
5 47 ms 55 ms 44 ms tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.2
35.173]
6 181 ms 193 ms 242 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 211 ms 211 ms 203 ms te3-7.ccr01.lon09.atlas.cogentco.com [149.6.98.7
3]
8 206 ms 216 ms 258 ms te0-7-0-32.ccr22.lon01.atlas.cogentco.com [154.5
4.36.169]
9 206 ms 206 ms 209 ms be2315.ccr22.lon13.atlas.cogentco.com [154.54.73
.109]
10 289 ms 275 ms 291 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
11 276 ms 296 ms 407 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
12 281 ms 293 ms 325 ms 38.111.40.114
13 367 ms 395 ms 303 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Documents and Settings\Admin>
My home pc
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 162 ms 116 ms 117 ms 10.220.229.171
3 65 ms 127 ms 80 ms 10.220.231.70
4 102 ms 117 ms 67 ms 41.50.16.63
5 121 ms 76 ms 77 ms 41.50.0.3
6 92 ms 238 ms 86 ms 41.50.1.5
7 249 ms 248 ms 258 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
8 282 ms 287 ms 293 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 339 ms 407 ms 322 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 346 ms 318 ms 327 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 350 ms 347 ms 327 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 350 ms 345 ms 358 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 364 ms * 336 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31
.9]
14 360 ms 337 ms 387 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
15 529 ms 412 ms 418 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 368 ms 377 ms 38.111.40.114
17 360 ms 388 ms 337 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
Whether you think you are right or wrong, either way you are RIGHT.
This one is from south africa, pietermaritzburg via one computer, ill post the other one later
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 19 ms 14 ms 8 ms ti-224-164-01.telkomadsl.co.za [105.224.164.1]
3 17 ms 24 ms 16 ms 105.229.0.6
4 17 ms 16 ms 21 ms 105.229.0.29
5 47 ms 55 ms 44 ms tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.2
35.173]
6 181 ms 193 ms 242 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 162 ms 116 ms 117 ms 10.220.229.171
3 65 ms 127 ms 80 ms 10.220.231.70
4 102 ms 117 ms 67 ms 41.50.16.63
5 121 ms 76 ms 77 ms 41.50.0.3
6 92 ms 238 ms 86 ms 41.50.1.5
7 249 ms 248 ms 258 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
Now the recommended upper limit for network latency to the STO Servers is 180ms... You're above this before even hitting the Cogent backbone... And in the first 'Trace Route' the congestion appears to be happening on a node that belongs to your ISP, so you might want to contact them and ask what is happening....
You could try using the Euro Proxy Options in the Launcher Option Menu, as this may or may not put you on a different connection path that goes around the congestion, but there is no guarantee that it would work
Was playing undine battleground fine, then hit crystaline entity,
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=348ms TTL=49
Reply from 208.95.185.41: bytes=32 time=519ms TTL=49
Reply from 208.95.185.41: bytes=32 time=422ms TTL=49
Reply from 208.95.185.41: bytes=32 time=333ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 519ms, Average = 405ms
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 107 ms 190 ms 138 ms 10.228.221.178
3 223 ms 108 ms 89 ms 10.228.223.70
4 308 ms 353 ms 93 ms 41.48.16.15
5 122 ms 85 ms 89 ms 41.48.0.3
6 90 ms 119 ms 528 ms 41.48.1.5
7 508 ms 338 ms 329 ms 83.231.233.141
8 301 ms 271 ms 355 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 345 ms 509 ms 436 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 603 ms 328 ms 388 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 364 ms 336 ms 375 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 583 ms 333 ms 357 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 424 ms 483 ms 340 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
14 383 ms 351 ms 476 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 451 ms 439 ms 407 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 414 ms 367 ms 340 ms 38.111.40.114
17 370 ms 372 ms 381 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 118 ms 138 ms 98 ms 10.228.221.178
3 282 ms 98 ms 328 ms 10.228.223.70
4 73 ms 146 ms 78 ms 41.48.16.15
5 112 ms 104 ms 78 ms 41.48.0.3
6 181 ms 208 ms 108 ms 41.48.1.5
7 262 ms 350 ms 588 ms 83.231.233.141
8 460 ms 310 ms 323 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 461 ms 399 ms 428 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 414 ms 341 ms 514 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 474 ms 428 ms 488 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 344 ms 418 ms 578 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 555 ms 418 ms 705 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
14 574 ms 398 ms 488 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 371 ms 608 ms 956 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 396 ms 464 ms 459 ms 38.111.40.114
17 396 ms 447 ms 391 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=355ms TTL=49
Reply from 208.95.185.41: bytes=32 time=335ms TTL=49
Reply from 208.95.185.41: bytes=32 time=377ms TTL=49
Reply from 208.95.185.41: bytes=32 time=498ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 335ms, Maximum = 498ms, Average = 391ms
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=1506ms TTL=49
Reply from 208.95.185.41: bytes=32 time=388ms TTL=49
Reply from 208.95.185.41: bytes=32 time=1590ms TTL=49
Reply from 208.95.185.41: bytes=32 time=797ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 388ms, Maximum = 1590ms, Average = 1070ms
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 110 ms 90 ms 86 ms 41.50.20.33
3 123 ms 71 ms 115 ms 10.220.229.234
4 165 ms 168 ms 87 ms 10.220.231.70
5 383 ms 100 ms 111 ms 41.50.16.63
6 109 ms 90 ms 188 ms 41.50.0.3
7 241 ms 176 ms 145 ms 41.50.1.5
8 283 ms 538 ms 264 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 330 ms 345 ms 256 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 491 ms 328 ms 358 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 401 ms 524 ms 412 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 366 ms 381 ms 348 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 681 ms 437 ms 367 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 407 ms 336 ms 320 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 461 ms 378 ms 366 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 612 ms 358 ms 436 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 438 ms 398 ms 340 ms 38.111.40.114
18 358 ms 393 ms 345 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 225 ms 172 ms 97 ms 41.50.20.33
3 182 ms 99 ms 98 ms 10.220.229.234
4 1343 ms 1635 ms 1005 ms 10.220.231.70
5 452 ms 1506 ms 1688 ms 41.50.16.63
6 * * 2466 ms 41.50.0.3
7 * * * Request timed out.
8 3122 ms 929 ms 295 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 719 ms 498 ms 833 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 566 ms 945 ms 623 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 505 ms 761 ms 1592 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 590 ms 525 ms 501 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 553 ms 468 ms 657 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 613 ms 538 ms 728 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 768 ms 728 ms 468 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 592 ms 609 ms 398 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 508 ms 948 ms 338 ms 38.111.40.114
18 396 ms 352 ms 1008 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 1799 ms 2170 ms 1977 ms 41.50.20.33
3 96 ms 197 ms 357 ms 10.220.229.234
4 84 ms 209 ms 97 ms 10.220.231.70
5 502 ms 141 ms 437 ms 41.50.16.63
6 138 ms 377 ms 128 ms 41.50.0.3
7 99 ms 178 ms 317 ms 41.50.1.5
8 291 ms 258 ms 267 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 375 ms 308 ms 317 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 335 ms 338 ms 327 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 337 ms 337 ms 338 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 349 ms 358 ms 427 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 414 ms 348 ms 447 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 349 ms 347 ms 388 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 349 ms 367 ms 348 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 340 ms 398 ms 528 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 527 ms 358 ms 367 ms 38.111.40.114
18 398 ms 438 ms 354 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
Whether you think you are right or wrong, either way you are RIGHT.
Was playing undine battleground fine, then hit crystaline entity,
...
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 1799 ms 2170 ms 1977 ms 41.50.20.33
3 96 ms 197 ms 357 ms 10.220.229.234
4 84 ms 209 ms 97 ms 10.220.231.70
5 502 ms 141 ms 437 ms 41.50.16.63
6 138 ms 377 ms 128 ms 41.50.0.3
7 99 ms 178 ms 317 ms 41.50.1.5
8 291 ms 258 ms 267 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 375 ms 308 ms 317 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 335 ms 338 ms 327 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 337 ms 337 ms 338 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 349 ms 358 ms 427 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 414 ms 348 ms 447 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 349 ms 347 ms 388 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 349 ms 367 ms 348 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 340 ms 398 ms 528 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 527 ms 358 ms 367 ms 38.111.40.114
18 398 ms 438 ms 354 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
The second hop should have a latency of 15ms - 20ms. Yours seems to indicate a issue with your Router/Gateway/Modem unit. If rebooting it doesn't help, then you will need to contact your ISP and have them send someone out to take a look at the unit...
...I'm not seeing anything out of the ordinary for my connection, yes I know hops 5 and 6 shot themselves but thats normal for me and hasnt really affected my gameplay..its verizon and the backbone hub, who are playing point the finger and refusing to help..anyways..moving on, below's the trace route.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [CENSORED, PRIVATE IP ADDRESS]
2 12 ms 7 ms 8 ms L100.NWRKNJ-VFTTP-113.verizon-gni.net [98.109.36
.1]
3 15 ms 18 ms 19 ms G102-0-0-38.NWRKNJ-LCR-21.verizon-gni.net [100.4
1.205.184]
4 10 ms 18 ms 17 ms 130.81.162.64
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 18 ms 18 ms 0.ae1.XL3.BOS4.ALTER.NET [140.222.226.13]
8 21 ms 18 ms 19 ms 0.xe-10-1-0.GW15.BOS4.ALTER.NET [152.63.21.138]
9 23 ms 18 ms 18 ms internap-gw.customer.alter.net [152.179.134.214]
10 19 ms 18 ms 18 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 56 ms 52 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 40 ms 48 ms 48 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
advice?
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
...I'm not seeing anything out of the ordinary for my connection, yes I know hops 5 and 6 shot themselves but thats normal for me and hasnt really affected my gameplay..its verizon and the backbone hub, who are playing point the finger and refusing to help..anyways..moving on, below's the trace route.
...
advice?
Your network latency looks fine, but latency isn't everything... What about connection quality? (which is what the 'Net Test' diagnostic shows, as it tests sustained throughput on the connection...)
You can also try using the 'pathping' command, which uses the same syntax as the 'tracert' command to see if data packets are being lost are thrown away on your connection path...
There are still reports that Verizon is throttling bandwidth with connections to Cogent Communications (which hosts STO) as part of their dispute with Netflix, so this may explain the lack of support from Verizon...
before I forget...the loading please wait thing? is before I even get to enter my login credentials..
also, nettest? how do I do that?
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Your network latency looks fine, but latency isn't everything... What about connection quality? (which is what the 'Net Test' diagnostic shows, as it tests sustained throughput on the connection...)
You can also try using the 'pathping' command, which uses the same syntax as the 'tracert' command to see if data packets are being lost are thrown away on your connection path...
There are still reports that Verizon is throttling bandwidth with connections to Cogent Communications (which hosts STO) as part of their dispute with Netflix, so this may explain the lack of support from Verizon...
about the throttling thing..that doesnt surprise me in the least, it'd explain the grief I've been getting with swtor's launcher stuffing itself after I enter my credentials and click login. (it sits there with that stupid busy swirly..doing jack)
I will however note that back in the tail end of may..I wasnt having these issues with sto, it was after one of the last few updates that it started.
Murphy's laws:
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
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.11.1
2 1 ms 1 ms 1 ms 192.168.88.1
3 14 ms 3 ms 3 ms c13-access-vlan.so.fastcom.ie [77.95.164.1]
4 5 ms 7 ms 6 ms c11-v6-nb-c13.fastcom.ie [77.95.165.117]
5 19 ms 9 ms 12 ms c3-v4-m5-so.fastcom.ie [83.245.74.9]
6 30 ms 33 ms 26 ms c6-v6-so.fastcom.ie [83.245.74.58]
7 32 ms 73 ms 36 ms c1-v7-so.fastcom.ie [83.245.74.41]
8 23 ms 23 ms 54 ms s1-v9-so.fastcom.ie [83.245.74.5]
9 18 ms 34 ms 28 ms r1-v8-so.fastcom.ie [83.245.74.1]
10 16 ms 28 ms 29 ms 149.11.37.49
11 * 25 ms 21 ms te0-0-0-5.rcr21.dub02.atlas.cogentco.com [154.25
.1.245]
12 * * 15 ms te3-5.ccr01.dub01.atlas.cogentco.com [154.54.38.
150]
13 25 ms 28 ms 33 ms te0-5-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.45.226]
14 95 ms 89 ms 95 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
15 100 ms 113 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 102 ms 104 ms 38.111.40.114
17 86 ms 91 ms 89 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Can anyone tell me what could be going on here. Im using a VoiP connection. Usually get good speed but it just doesn't seem stable.
Comments
Sp
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 12 ms 13 ms 172.30.76.209
4 41 ms 14 ms 20 ms 172.30.32.65
5 74 ms 51 ms 73 ms 12.94.104.73
6 25 ms 27 ms 27 ms cr2.attga.ip.att.net [12.122.140.170]
7 26 ms 25 ms 23 ms 12.122.140.245
8 24 ms 26 ms 24 ms te0-7-0-7.ccr21.atl02.atlas.cogentco.com [154.54
.13.41]
9 46 ms 38 ms 39 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.
161]
10 45 ms 43 ms 43 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
11 50 ms 49 ms 50 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
12 47 ms 49 ms 50 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
13 52 ms 53 ms 52 ms 38.111.40.114
14 49 ms 49 ms 51 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP:
Ping: 53.6 msec
Port: 80: 1020 KB/sec 33 KB/sec 1078 KB/sec 500
Port: 80: 750 KB/sec 23 KB/sec 792 KB/sec 500
Port: 443: 1055 KB/sec 32 KB/sec 1113 KB/sec 500
Port: 443: 761 KB/sec 25 KB/sec 804 KB/sec 500
Port: 7255: 441 KB/sec 14 KB/sec 466 KB/sec 500
Port: 7255: 393 KB/sec 12 KB/sec 415 KB/sec 500
Port: 7003: 955 KB/sec 32 KB/sec 1009 KB/sec 500
Port: 7003: 935 KB/sec 37 KB/sec 987 KB/sec 500
Port: 7202: 496 KB/sec 25 KB/sec 524 KB/sec 500
Port: 7202: 513 KB/sec 18 KB/sec 542 KB/sec 500
Port: 7499: 875 KB/sec 28 KB/sec 923 KB/sec 500
Port: 7499: 767 KB/sec 23 KB/sec 809 KB/sec 500
Port: 80: 992 KB/sec 29 KB/sec 1047 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Isp mediacom
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.NYCMNY-VFTTP-236.verizon-gni.net [108.6.14.
1]
3 4 ms 3 ms 3 ms G0-14-2-4.NYCMNY-LCR-22.verizon-gni.net [130.81.
180.96]
4 7 ms 28 ms 2 ms ae4-0.NY5030-BB-RTR2.verizon-gni.net [130.81.163
.232]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 10 ms 10 ms 0.ae1.XL4.BOS4.ALTER.NET [140.222.226.15]
8 9 ms 10 ms 10 ms 0.ge-9-1-0.GW15.BOS4.ALTER.NET [152.63.24.46]
9 10 ms 9 ms 9 ms internap-gw.customer.alter.net [152.179.134.214]
10 11 ms 9 ms 9 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
11 21 ms 17 ms 17 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 10 ms 9 ms 9 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
I'm in Fios in New York.
10Chrs
Note: I have blanked out my own IP address.
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 5 ms 4 ms 192.168.1.1
2 12 ms 11 ms 13 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53.
0.1]
3 13 ms 11 ms 13 ms 50.126.112.37
4 17 ms 17 ms 17 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2
17]
5 17 ms 17 ms 17 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2
21]
6 17 ms 38 ms 17 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
22]
7 17 ms 17 ms 18 ms 206.111.7.149.ptr.us.xo.net [206.111.7.149]
8 101 ms 101 ms 103 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 106 ms 105 ms 104 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 106 ms 107 ms 102 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 100 ms 97 ms 97 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]
12 107 ms 106 ms 110 ms 209.117.103.10
13 107 ms 107 ms 107 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 118 ms * 998 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 110 ms 108 ms 107 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Nettest:
contacting nettest server..
Local IP: TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
Ping: 100.0 msec
Port: 80: 606 KB/sec 22 KB/sec 644 KB/sec 500
Port: 80: 159 KB/sec 7 KB/sec 170 KB/sec 500
Port: 443: 610 KB/sec 24 KB/sec 649 KB/sec 500
Port: 443: 645 KB/sec 24 KB/sec 686 KB/sec 500
Port: 7255: 616 KB/sec 23 KB/sec 657 KB/sec 500
Port: 7255: 610 KB/sec 23 KB/sec 650 KB/sec 500
Port: 7003: 589 KB/sec 22 KB/sec 627 KB/sec 500
Port: 7003: 598 KB/sec 23 KB/sec 636 KB/sec 500
Port: 7202: 608 KB/sec 23 KB/sec 646 KB/sec 500
Port: 7202: 607 KB/sec 23 KB/sec 646 KB/sec 500
Port: 7499: 603 KB/sec 23 KB/sec 642 KB/sec 500
Port: 7499: 602 KB/sec 22 KB/sec 641 KB/sec 500
Port: 80: 591 KB/sec 22 KB/sec 628 KB/sec 500
Idle NIC bandwidth Send: 3 KB/sec Recv: 2 KB/sec
hit return to exit
Thank you in advance for fixing this!
They really should. But people are desperate for advice and as ever, are kept hanging with no help. Several of us have been told to post in here with concrete info in order to get things resolved and despite doing so, are still left hanging.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Brian>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
2 1 ms 1 ms 1 ms
3 8 ms 14 ms 5 ms c13-access-vlan.so.fastcom.ie [77.95.164.1]
4 4 ms 9 ms 8 ms c11-v6-nb-c13.fastcom.ie [77.95.165.117]
5 12 ms 19 ms 11 ms c3-v4-m5-so.fastcom.ie [83.245.74.9]
6 22 ms 11 ms 11 ms c6-v6-so.fastcom.ie [83.245.74.58]
7 11 ms 22 ms 15 ms c1-v7-so.fastcom.ie [83.245.74.41]
8 13 ms 10 ms 12 ms s1-v9-so.fastcom.ie [83.245.74.5]
9 23 ms 39 ms 21 ms r1-v8-so.fastcom.ie [83.245.74.1]
10 30 ms 19 ms 16 ms 149.11.37.49
11 * 22 ms 18 ms te2-6.ccr01.dub02.atlas.cogentco.com [154.25.1.2
45]
12 20 ms 21 ms 25 ms te7-7.ccr01.dub01.atlas.cogentco.com [154.54.56.
49]
13 29 ms 31 ms * te0-5-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.45.226]
14 89 ms 93 ms 93 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
15 171 ms 216 ms 209 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 97 ms 88 ms 91 ms 38.111.40.114
17 * 142 ms 87 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP:
Ping: 100.0 msec
Port: 80: 72 KB/sec 3 KB/sec 76 KB/sec 500
Port: 80: 502 KB/sec 17 KB/sec 531 KB/sec 500
Port: 443: 133 KB/sec 6 KB/sec 142 KB/sec 500
Port: 443: 58 KB/sec 2 KB/sec 62 KB/sec 500
Port: 7255: 195 KB/sec 9 KB/sec 207 KB/sec 500
Port: 7255: 61 KB/sec 2 KB/sec 65 KB/sec 500
Port: 7003: 90 KB/sec 5 KB/sec 96 KB/sec 500
Port: 7003: 98 KB/sec 4 KB/sec 103 KB/sec 500
Port: 7202: 60 KB/sec 2 KB/sec 64 KB/sec 500
Port: 7202: 61 KB/sec 3 KB/sec 66 KB/sec 500
Port: 7499: 172 KB/sec 7 KB/sec 182 KB/sec 500
Port: 7499: 400 KB/sec 15 KB/sec 421 KB/sec 500
Port: 80: 177 KB/sec 7 KB/sec 188 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Please help!!!
Its most likely that the problem is being caused by network congestion in one of the Internet Backbone providers (e.g. most likely Cogent Communications..)
Have you tried using the 'Proxy' options in the Launcher Option Menu, as this may, or may not help relieve the problem...
Thanks for the response. I switched from the EU server to the US server. I actually thought it done the trick but the lag returned worst than ever after about 10 minutes
Been having major lag the past couple of days. Now I can't get even past the character selection screen. I have no problem playing other online games like Guild Wars 2 but having major issue with STO. Here is the info requested.
Microsoft Windows [Version 6.1.7601]
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 192.168.1.1
2 9 ms 11 ms 8 ms cm1.zeta184.maxonline.com.sg [TRIBBLE.xx.TRIBBLE.x]
3 9 ms 8 ms 7 ms cm1.zeta184.maxonline.com.sg [TRIBBLE.xx.TRIBBLE.x]
4 6 ms 7 ms 6 ms 172.20.52.69
5 8 ms 13 ms 11 ms 172.26.52.5
6 10 ms 11 ms 11 ms 172.20.7.98
7 15 ms 15 ms 14 ms 203.117.34.73
8 11 ms 11 ms 11 ms six2asr9kts01.starhub.net.sg [203.117.34.9]
9 12 ms 11 ms 12 ms 203.117.34.38
10 12 ms 32 ms 14 ms 203.116.61.118
11 * * * Request timed out.
12 263 ms 280 ms 265 ms 65.120.117.250
13 268 ms 266 ms 265 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 272 ms 269 ms 269 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 268 ms 265 ms 267 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Windows\system32>
contacting nettest server..
Local IP: TRIBBLE.TRIBBLE.TRIBBLE.TRIBBLE
Ping: 250.1 msec
Port: 80: 58 KB/sec 5 KB/sec 62 KB/sec 500
Port: 80: 7 KB/sec 2 KB/sec 11 KB/sec 500
Port: 443: 5 KB/sec 1 KB/sec 6 KB/sec 500
Port: 443: 5 KB/sec 1 KB/sec 6 KB/sec 500
Port: 7255: 29 KB/sec 2 KB/sec 32 KB/sec 500
Port: 7255: 3 KB/sec 1 KB/sec 5 KB/sec 500
Port: 7003: 7 KB/sec 1 KB/sec 9 KB/sec 500
Port: 7003: 28 KB/sec 2 KB/sec 31 KB/sec 500
Port: 7202: 29 KB/sec 2 KB/sec 34 KB/sec 500
Port: 7202: 37 KB/sec 4 KB/sec 42 KB/sec 500
Port: 7499: 5 KB/sec 1 KB/sec 7 KB/sec 500
Port: 7499: 27 KB/sec 2 KB/sec 32 KB/sec 500
Port: 80: 3 KB/sec 1 KB/sec 5 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 1 KB/sec
hit return to exit
ISP: Starhub Maxonline
Location: Singapore
Any help would be appreciated.
Each day the problem is getting worse. And all this problems happen after ending of april, start of may.
C:\Windows\System32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 8 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 4 ms 4 ms 4 ms 174.251.40.189.isp.timbrasil.com.br [189.40.251.
3 4 ms 4 ms 4 ms 10.223.10.33
4 8 ms 11 ms 11 ms 10.223.238.225
5 10 ms 6 ms 6 ms 10.223.238.46
6 8 ms 6 ms 6 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.144
7 106 ms 106 ms 106 ms xe-0-0-1.miami15.mia.seabone.net [195.22.199.101
8 107 ms 107 ms 107 ms te0-0-0-4.ccr21.mia03.atlas.cogentco.com [154.54
9 107 ms 107 ms 107 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80
10 149 ms 148 ms 148 ms be2122.ccr21.atl01.atlas.cogentco.com [154.54.24
11 138 ms 138 ms 138 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
12 138 ms 138 ms 138 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
13 145 ms 145 ms 145 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
14 145 ms 146 ms 145 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
15 147 ms 144 ms 157 ms 38.111.40.114
16 145 ms 145 ms 145 ms patchserver2.crypticstudios.com [208.95.185.41]
Setting the game proxy to US :
C:\Windows\System32>tracert us1.proxy.crypticstudios.com
Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 10 ms 4 ms 4 ms 174.251.40.189.isp.timbrasil.com.br [189.40.25
3 4 ms 4 ms 4 ms 10.223.10.33
4 8 ms 11 ms 11 ms 10.223.229.49
5 4 ms 6 ms 6 ms 10.223.238.50
6 7 ms 6 ms 7 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.1
7 106 ms 106 ms 106 ms xe-0-0-1.miami15.mia.seabone.net [195.22.199.1
8 107 ms 109 ms 107 ms te0-7-0-34.ccr21.mia03.atlas.cogentco.com [154
9 107 ms 107 ms 107 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.
10 151 ms 151 ms 151 ms be2124.mpd21.atl01.atlas.cogentco.com [154.54.
11 139 ms 139 ms 139 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.
12 139 ms 139 ms 139 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.
13 144 ms 144 ms 144 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.
14 145 ms 145 ms 145 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.
15 150 ms 144 ms 157 ms 38.111.40.114
16 145 ms 145 ms 145 ms us1.proxy.crypticstudios.com [208.95.184.152]
Setting the game proxy for Europe. The game is more stable, but I get ping of 450ms.
C:\Windows\System32>tracert eu1.proxy.crypticstudios.com
Tracing route to eu1.proxy.crypticstudios.com [79.125.3.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.10.1]
2 6 ms 82 ms 29 ms 174.251.40.189.isp.timbrasil.com.br [189.40.251.174]
3 4 ms 4 ms 4 ms 10.223.10.34
4 12 ms 11 ms 11 ms 10.223.238.217
5 11 ms 7 ms 7 ms 10.223.238.50
6 6 ms 7 ms 7 ms te0-0-0-2.riodejaneiro2.rio.seabone.net [213.144.160.41]
7 213 ms 213 ms 213 ms xe-7-1-0.londra32.lon.seabone.net [195.22.209.105]
8 217 ms 217 ms 217 ms amazon.londra32.lon.seabone.net [89.221.43.103]
9 240 ms 242 ms 240 ms 176.32.106.6
10 231 ms 231 ms 231 ms 176.32.106.16
11 242 ms 242 ms 242 ms 178.236.0.99
12 247 ms 247 ms 247 ms 178.236.0.128
13 269 ms 233 ms 233 ms 178.236.0.125
14 239 ms 239 ms 242 ms ec2-79-125-0-137.eu-west-1.compute.amazonaws.com [79.125.0.137]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 244 ms 239 ms 240 ms ec2-79-125-3-30.eu-west-1.compute.amazonaws.com [79.125.3.30]
Trace complete.
Nettest
contacting nettest server..
Local IP: 189.40.6.50
Ping: 142.9 msec
Port: 80: 485 KB/sec 13 KB/sec 511 KB/sec 500
Port: 80: 2 KB/sec 0 KB/sec 4 KB/sec 500
Port: 443: 4 KB/sec 0 KB/sec 4 KB/sec 500
Port: 443: 2 KB/sec 2 KB/sec 16 KB/sec 500
Port: 7255: 3 KB/sec 1 KB/sec 11 KB/sec 500
Port: 7255: 494 KB/sec 12 KB/sec 528 KB/sec 500
Port: 7003: 3 KB/sec 0 KB/sec 5 KB/sec 500
Port: 7003: 3 KB/sec 0 KB/sec 4 KB/sec 500
Port: 7202: 492 KB/sec 11 KB/sec 519 KB/sec 500
Port: 7202: 2 KB/sec 1 KB/sec 8 KB/sec 500
Port: 7499: 495 KB/sec 14 KB/sec 522 KB/sec 500
Port: 7499: 2 KB/sec 3 KB/sec 16 KB/sec 500
Port: 80: 3 KB/sec 4 KB/sec 41 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 8 KB/sec
hit return to exit
Also, nettest starts with "unable to allocate performance buffer", reports only 0 for the second and third columns, and becomes unresponsive at port 7003.
A '*' means the router node is not responding, which could be caused by a variety of reasons, such as the node is not configured to support ICMP/IP Diagnostic packets, or too much network traffic to respond...
Now if 'Net Test' can't allocate a buffer, this means there is something wrong with your own computer, such as running out of memory due to memory leaks, too many networked applications and processes running, etc. Try rebooting your computer, then run Nettest with nothing else running...
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 19 ms 14 ms 8 ms ti-224-164-01.telkomadsl.co.za [105.224.164.1]
3 17 ms 24 ms 16 ms 105.229.0.6
4 17 ms 16 ms 21 ms 105.229.0.29
5 47 ms 55 ms 44 ms tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.2
35.173]
6 181 ms 193 ms 242 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 211 ms 211 ms 203 ms te3-7.ccr01.lon09.atlas.cogentco.com [149.6.98.7
3]
8 206 ms 216 ms 258 ms te0-7-0-32.ccr22.lon01.atlas.cogentco.com [154.5
4.36.169]
9 206 ms 206 ms 209 ms be2315.ccr22.lon13.atlas.cogentco.com [154.54.73
.109]
10 289 ms 275 ms 291 ms be2389.ccr22.bos01.atlas.cogentco.com [154.54.44
.181]
11 276 ms 296 ms 407 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
12 281 ms 293 ms 325 ms 38.111.40.114
13 367 ms 395 ms 303 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\Documents and Settings\Admin>
My home pc
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 162 ms 116 ms 117 ms 10.220.229.171
3 65 ms 127 ms 80 ms 10.220.231.70
4 102 ms 117 ms 67 ms 41.50.16.63
5 121 ms 76 ms 77 ms 41.50.0.3
6 92 ms 238 ms 86 ms 41.50.1.5
7 249 ms 248 ms 258 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
8 282 ms 287 ms 293 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 339 ms 407 ms 322 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 346 ms 318 ms 327 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 350 ms 347 ms 327 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 350 ms 345 ms 358 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 364 ms * 336 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31
.9]
14 360 ms 337 ms 387 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
15 529 ms 412 ms 418 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 368 ms 377 ms 38.111.40.114
17 360 ms 388 ms 337 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
Now the recommended upper limit for network latency to the STO Servers is 180ms... You're above this before even hitting the Cogent backbone... And in the first 'Trace Route' the congestion appears to be happening on a node that belongs to your ISP, so you might want to contact them and ask what is happening....
You could try using the Euro Proxy Options in the Launcher Option Menu, as this may or may not put you on a different connection path that goes around the congestion, but there is no guarantee that it would work
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=348ms TTL=49
Reply from 208.95.185.41: bytes=32 time=519ms TTL=49
Reply from 208.95.185.41: bytes=32 time=422ms TTL=49
Reply from 208.95.185.41: bytes=32 time=333ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 519ms, Average = 405ms
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 107 ms 190 ms 138 ms 10.228.221.178
3 223 ms 108 ms 89 ms 10.228.223.70
4 308 ms 353 ms 93 ms 41.48.16.15
5 122 ms 85 ms 89 ms 41.48.0.3
6 90 ms 119 ms 528 ms 41.48.1.5
7 508 ms 338 ms 329 ms 83.231.233.141
8 301 ms 271 ms 355 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 345 ms 509 ms 436 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 603 ms 328 ms 388 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 364 ms 336 ms 375 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 583 ms 333 ms 357 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 424 ms 483 ms 340 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
14 383 ms 351 ms 476 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 451 ms 439 ms 407 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 414 ms 367 ms 340 ms 38.111.40.114
17 370 ms 372 ms 381 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 118 ms 138 ms 98 ms 10.228.221.178
3 282 ms 98 ms 328 ms 10.228.223.70
4 73 ms 146 ms 78 ms 41.48.16.15
5 112 ms 104 ms 78 ms 41.48.0.3
6 181 ms 208 ms 108 ms 41.48.1.5
7 262 ms 350 ms 588 ms 83.231.233.141
8 460 ms 310 ms 323 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
9 461 ms 399 ms 428 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
10 414 ms 341 ms 514 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
11 474 ms 428 ms 488 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
12 344 ms 418 ms 578 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
13 555 ms 418 ms 705 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
14 574 ms 398 ms 488 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
15 371 ms 608 ms 956 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
16 396 ms 464 ms 459 ms 38.111.40.114
17 396 ms 447 ms 391 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=355ms TTL=49
Reply from 208.95.185.41: bytes=32 time=335ms TTL=49
Reply from 208.95.185.41: bytes=32 time=377ms TTL=49
Reply from 208.95.185.41: bytes=32 time=498ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 335ms, Maximum = 498ms, Average = 391ms
C:\WINDOWS\system32>ping 208.95.185.41
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=1506ms TTL=49
Reply from 208.95.185.41: bytes=32 time=388ms TTL=49
Reply from 208.95.185.41: bytes=32 time=1590ms TTL=49
Reply from 208.95.185.41: bytes=32 time=797ms TTL=49
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 388ms, Maximum = 1590ms, Average = 1070ms
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 110 ms 90 ms 86 ms 41.50.20.33
3 123 ms 71 ms 115 ms 10.220.229.234
4 165 ms 168 ms 87 ms 10.220.231.70
5 383 ms 100 ms 111 ms 41.50.16.63
6 109 ms 90 ms 188 ms 41.50.0.3
7 241 ms 176 ms 145 ms 41.50.1.5
8 283 ms 538 ms 264 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 330 ms 345 ms 256 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 491 ms 328 ms 358 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 401 ms 524 ms 412 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 366 ms 381 ms 348 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 681 ms 437 ms 367 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 407 ms 336 ms 320 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 461 ms 378 ms 366 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 612 ms 358 ms 436 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 438 ms 398 ms 340 ms 38.111.40.114
18 358 ms 393 ms 345 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 225 ms 172 ms 97 ms 41.50.20.33
3 182 ms 99 ms 98 ms 10.220.229.234
4 1343 ms 1635 ms 1005 ms 10.220.231.70
5 452 ms 1506 ms 1688 ms 41.50.16.63
6 * * 2466 ms 41.50.0.3
7 * * * Request timed out.
8 3122 ms 929 ms 295 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 719 ms 498 ms 833 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 566 ms 945 ms 623 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 505 ms 761 ms 1592 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 590 ms 525 ms 501 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 553 ms 468 ms 657 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 613 ms 538 ms 728 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 768 ms 728 ms 468 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 592 ms 609 ms 398 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 508 ms 948 ms 338 ms 38.111.40.114
18 396 ms 352 ms 1008 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 1799 ms 2170 ms 1977 ms 41.50.20.33
3 96 ms 197 ms 357 ms 10.220.229.234
4 84 ms 209 ms 97 ms 10.220.231.70
5 502 ms 141 ms 437 ms 41.50.16.63
6 138 ms 377 ms 128 ms 41.50.0.3
7 99 ms 178 ms 317 ms 41.50.1.5
8 291 ms 258 ms 267 ms e1-4-1-0.a00.londen03.uk.ra.gin.ntt.net [213.130
.48.125]
9 375 ms 308 ms 317 ms xe-1-0-9.r22.londen03.uk.bb.gin.ntt.net [129.250
.4.189]
10 335 ms 338 ms 327 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1
26]
11 337 ms 337 ms 338 ms ae-2.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.1
75]
12 349 ms 358 ms 427 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
13 414 ms 348 ms 447 ms be2073.ccr21.jfk05.atlas.cogentco.com [154.54.0.
229]
14 349 ms 347 ms 388 ms be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.
13]
15 349 ms 367 ms 348 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
16 340 ms 398 ms 528 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
17 527 ms 358 ms 367 ms 38.111.40.114
18 398 ms 438 ms 354 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
C:\WINDOWS\system32>
The second hop should have a latency of 15ms - 20ms. Yours seems to indicate a issue with your Router/Gateway/Modem unit. If rebooting it doesn't help, then you will need to contact your ISP and have them send someone out to take a look at the unit...
I posted here http://sto-forum.perfectworld.com/showthread.php?t=1151761 and asked advice, was told to do a trace route.
so I went and did a trace route.
...I'm not seeing anything out of the ordinary for my connection, yes I know hops 5 and 6 shot themselves but thats normal for me and hasnt really affected my gameplay..its verizon and the backbone hub, who are playing point the finger and refusing to help..anyways..moving on, below's the trace route.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\XRaiderV1>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 Wireless_Broadband_Router.home [CENSORED, PRIVATE IP ADDRESS]
2 12 ms 7 ms 8 ms L100.NWRKNJ-VFTTP-113.verizon-gni.net [98.109.36
.1]
3 15 ms 18 ms 19 ms G102-0-0-38.NWRKNJ-LCR-21.verizon-gni.net [100.4
1.205.184]
4 10 ms 18 ms 17 ms 130.81.162.64
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 18 ms 18 ms 0.ae1.XL3.BOS4.ALTER.NET [140.222.226.13]
8 21 ms 18 ms 19 ms 0.xe-10-1-0.GW15.BOS4.ALTER.NET [152.63.21.138]
9 23 ms 18 ms 18 ms internap-gw.customer.alter.net [152.179.134.214]
10 19 ms 18 ms 18 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
11 56 ms 52 ms 53 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
12 40 ms 48 ms 48 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
advice?
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Your network latency looks fine, but latency isn't everything... What about connection quality? (which is what the 'Net Test' diagnostic shows, as it tests sustained throughput on the connection...)
You can also try using the 'pathping' command, which uses the same syntax as the 'tracert' command to see if data packets are being lost are thrown away on your connection path...
There are still reports that Verizon is throttling bandwidth with connections to Cogent Communications (which hosts STO) as part of their dispute with Netflix, so this may explain the lack of support from Verizon...
also, nettest? how do I do that?
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
about the throttling thing..that doesnt surprise me in the least, it'd explain the grief I've been getting with swtor's launcher stuffing itself after I enter my credentials and click login. (it sits there with that stupid busy swirly..doing jack)
I will however note that back in the tail end of may..I wasnt having these issues with sto, it was after one of the last few updates that it started.
1- Murphy’s Law tells us that anything that can go wrong will go wrong.
2- And anything that does go wrong will get progressively worse.
3- And if you survive the first two laws it’s time to panic.
Look at the first post of this thread for instruction on 'Net Test'....
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.11.1
2 1 ms 1 ms 1 ms 192.168.88.1
3 14 ms 3 ms 3 ms c13-access-vlan.so.fastcom.ie [77.95.164.1]
4 5 ms 7 ms 6 ms c11-v6-nb-c13.fastcom.ie [77.95.165.117]
5 19 ms 9 ms 12 ms c3-v4-m5-so.fastcom.ie [83.245.74.9]
6 30 ms 33 ms 26 ms c6-v6-so.fastcom.ie [83.245.74.58]
7 32 ms 73 ms 36 ms c1-v7-so.fastcom.ie [83.245.74.41]
8 23 ms 23 ms 54 ms s1-v9-so.fastcom.ie [83.245.74.5]
9 18 ms 34 ms 28 ms r1-v8-so.fastcom.ie [83.245.74.1]
10 16 ms 28 ms 29 ms 149.11.37.49
11 * 25 ms 21 ms te0-0-0-5.rcr21.dub02.atlas.cogentco.com [154.25
.1.245]
12 * * 15 ms te3-5.ccr01.dub01.atlas.cogentco.com [154.54.38.
150]
13 25 ms 28 ms 33 ms te0-5-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.45.226]
14 95 ms 89 ms 95 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
15 100 ms 113 ms 94 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 * 102 ms 104 ms 38.111.40.114
17 86 ms 91 ms 89 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Can anyone tell me what could be going on here. Im using a VoiP connection. Usually get good speed but it just doesn't seem stable.