Latency Report as suggested

granitechaos

Cryptic Report:
I have been having massive rubber banding issues in STO. Which is making combat unplayable. So I decided to give you a latency data. The only spot I see trouble I have underlined. But I might be missing something as Networking is a hobby not my occupation lol.
See anything, or suggest anything that maybe causing lag or a way to fix it?

Internet Speed test Results: http://www.speedtest.net/my-result/4005848111
Connecting Via the ISP: Comcast In Colorado

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Frederick>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 10.0.0.1
2 9 ms 8 ms 8 ms c-50-155-234-1.hsd1.co.comcast.net [50.155.234.1]
3 9 ms 16 ms 10 ms xe-9-2-2-0-sur03.cosprings.co.denver.comcast.net [68.85.107.145]
4 8 ms 8 ms 8 ms ae-10-0-sur02.cosprings.co.denver.comcast.net [162.151.50.58]
5 12 ms 16 ms 12 ms ae-23-0-ar01.aurora.co.denver.comcast.net [68.86.103.54]
6 14 ms 14 ms 15 ms he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21]
7 13 ms 13 ms 13 ms xe-1-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.114]
8 32 ms 31 ms 32 ms te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
9 31 ms 31 ms 32 ms te0-6-0-3.ccr22.den01.atlas.cogentco.com [154.54.45.185]
10 31 ms 31 ms 31 ms be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
11 37 ms 37 ms 37 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
12 61 ms 61 ms 61 ms be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202]
13 196 ms 232 ms 227 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 78 ms 71 ms 70 ms 38.111.40.114
15 65 ms 65 ms 70 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete
C:\Users\Frederick>


Nettest:
contacting nettest server..
Local IP: 50.155.234.50
Ping: 65.2 msec
Port: 80: 447 KB/sec 9 KB/sec 471 KB/sec 500
Port: 80: 550 KB/sec 13 KB/sec 579 KB/sec 500
Port: 443: 415 KB/sec 10 KB/sec 436 KB/sec 500
Port: 443: 417 KB/sec 10 KB/sec 439 KB/sec 500
Port: 7255: 463 KB/sec 9 KB/sec 486 KB/sec 500
Port: 7255: 416 KB/sec 9 KB/sec 438 KB/sec 500
Port: 7003: 450 KB/sec 8 KB/sec 472 KB/sec 500
Port: 7003: 404 KB/sec 8 KB/sec 424 KB/sec 500
Port: 7202: 447 KB/sec 8 KB/sec 469 KB/sec 500
Port: 7202: 391 KB/sec 9 KB/sec 411 KB/sec 500
Port: 7499: 432 KB/sec 8 KB/sec 454 KB/sec 500
Port: 7499: 432 KB/sec 7 KB/sec 454 KB/sec 500
Port: 80: 433 KB/sec 10 KB/sec 456 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit



pathping patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 Bender [10.0.0.21]
1 10.0.0.1
2 c-50-155-234-1.hsd1.co.comcast.net [50.155.234.1]
3 xe-9-2-2-0-sur03.cosprings.co.denver.comcast.net [68.85.107.145]
4 ae-10-0-sur02.cosprings.co.denver.comcast.net [162.151.50.58]
5 ae-23-0-ar01.aurora.co.denver.comcast.net [68.86.103.54]
6 he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21]
7 xe-1-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.114]
8 te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
9 te0-6-0-3.ccr22.den01.atlas.cogentco.com [154.54.45.185]
10 be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122]
11 be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
12 be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202]
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]

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bender [10.0.0.21] 0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.10/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% c-50-155-234-1.hsd1.co.comcast.net [50.155.234.1] 0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% xe-9-2-2-0-sur03.cosprings.co.denver.comcast.net [68.85.107.145] 0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% ae-10-0-sur02.cosprings.co.denver.comcast.net [162.151.50.58] 0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% ae-23-0-ar01.aurora.co.denver.comcast.net [68.86.103.54] 0/ 100 = 0%
6 14ms 0/ 100 = 0% 0/ 100 = 0% he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21] 0/ 100 = 0%
7 15ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.114]
0/ 100 = 0% |
8 31ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-0.rcr11.b006467-1.den01.atlas.cogentco.com [154.54.10.33]
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% te0-6-0-3.ccr22.den01.atlas.cogentco.com [154.54.45.185] 0/ 100 = 0%
10 31ms 0/ 100 = 0% 0/ 100 = 0% be2130.ccr22.mci01.atlas.cogentco.com [154.54.26.122] 0/ 100 = 0% |
11 36ms 0/ 100 = 0% 0/ 100 = 0% be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118] 0/ 100 = 0% |
12 61ms 0/ 100 = 0% 0/ 100 = 0% be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202] 0/ 100 = 0% |
13 98ms 0/ 100 = 0% 0/ 100 = 0% te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254] 0/ 100 = 0% |
14 70ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.1140/ 100 = 0% |
15 65ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [208.95.185.41]

Trace complete.

C:\Users\Frederick>

grouchyotaku

granitechaos wrote: »

Cryptic Report:
I have been having massive rubber banding issues in STO. Which is making combat unplayable. So I decided to give you a latency data. The only spot I see trouble I have underlined. But I might be missing something as Networking is a hobby not my occupation lol.
See anything, or suggest anything that maybe causing lag or a way to fix it?
...

Hard to say with this one... The 'Net Test' shows a wider range of sustained network throughput values then what should be expected, which hints at a intermittent connection quality issue...

The only thing that looks suspicious is hop #13 of the 'Trace Route' diagnostics, which is higher then the Cryptic recommended upper limit of 180 ms of network latency. However, hop #13 of the 'Path Ping' results shows a better network latency value, so this also indicates a intermittent problems, possibly network load based on the Cogent Boston Hub...

Have you tried using the US Proxy option in the Launcher Option Menu? As this may, or may not bypass the suspected network congestion on your connection route. At least, it doesn't hurt to try, as you can always change the settings back if it doesn't work...

granitechaos

Sadly Gameplay Proxy has no affect, no difference between Gamplay Proxy: None, US. or EU.

But thank you for the suggestion.

shadowwraith77

Here's my results, since the so called server stability update of today!

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 Home server
2 41 ms 39 ms 40 ms fl-76-2-104-1.dhcp.embarqhsd.net [76.2.104.1]
3 90 ms 52 ms 51 ms 184.7.223.14
4 39 ms 39 ms 44 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 42 ms 39 ms 40 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 45 ms 77 ms 44 ms 173-248-79-186.centurylink.net [173.248.79.186]

7 63 ms 63 ms 111 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 87 ms 84 ms 89 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 84 ms 92 ms 91 ms 65.120.117.250
13 80 ms 79 ms 79 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 91 ms 92 ms 105 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 * * * Request timed out.
16 82 ms 81 ms 82 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

C:\Windows\system32>

8-10 is always like this no matter who I route to so, don't pay any mind to it!
15 however has never timed out, unless I experience an issue Cryptic side.

contacting nettest server..
Local IP: 76.2.109.15
Ping: 79.2 msec
Port: 80: 413 KB/sec 15 KB/sec 437 KB/sec 500
Port: 80: 413 KB/sec 15 KB/sec 436 KB/sec 500
Port: 443: 70 KB/sec 3 KB/sec 75 KB/sec 500
Port: 443: 153 KB/sec 6 KB/sec 162 KB/sec 500
Port: 7255: 173 KB/sec 6 KB/sec 183 KB/sec 500
Port: 7255: 413 KB/sec 15 KB/sec 438 KB/sec 500
Port: 7003: 413 KB/sec 15 KB/sec 437 KB/sec 500
Port: 7003: 232 KB/sec 9 KB/sec 247 KB/sec 500
Port: 7202: 83 KB/sec 3 KB/sec 88 KB/sec 500
Port: 7202: 164 KB/sec 7 KB/sec 176 KB/sec 500
Port: 7499: 138 KB/sec 14 KB/sec 191 KB/sec 500
Port: 7499: 413 KB/sec 15 KB/sec 436 KB/sec 500
Port: 80: 53 KB/sec 2 KB/sec 57 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

Ports 80, 443, 7255, 7003, 7202, 7499 seem like they are a problem, when compared to good connection tested before server stability updates.

More tests below v

contacting nettest server..
Local IP: 71.3.222.159
Ping: 200.0 msec
Port: 80: 29 KB/sec 2 KB/sec 33 KB/sec 500
Port: 80: 33 KB/sec 2 KB/sec 38 KB/sec 500
Port: 443: 24 KB/sec 2 KB/sec 28 KB/sec 500
Port: 443: 33 KB/sec 2 KB/sec 37 KB/sec 500
Port: 7255: 40 KB/sec 3 KB/sec 45 KB/sec 500
Port: 7255: 41 KB/sec 2 KB/sec 46 KB/sec 500
Port: 7003: 32 KB/sec 2 KB/sec 36 KB/sec 500
Port: 7003: 27 KB/sec 2 KB/sec 31 KB/sec 500
Port: 7202: 24 KB/sec 2 KB/sec 28 KB/sec 500
Port: 7202: 28 KB/sec 2 KB/sec 33 KB/sec 500
Port: 7499: 35 KB/sec 2 KB/sec 39 KB/sec 500
Port: 7499: 30 KB/sec 2 KB/sec 34 KB/sec 500
Port: 80: 47 KB/sec 3 KB/sec 52 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 2 KB/sec
hit return to exit

^ This is from a previous test, done some months ago!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\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 Home server
2 34 ms 36 ms 34 ms fl-71-3-216-1.dhcp.embarqhsd.net [71.3.216.1]
3 42 ms 35 ms 34 ms fl-184-7-223-26.sta.centurylinkservices.net [184
.7.223.26]
4 39 ms 35 ms 67 ms bb-ftmyflxa-jx9-02-ae0.core.centurytel.net [208.
110.248.86]
5 36 ms 39 ms 37 ms bb-ftmyflxa-jx9-01-ae0.core.centurytel.net [208.
110.248.85]
6 41 ms 44 ms 41 ms bb-wnpkflxe-jx9-01-xe-11-1-0.0.core.centurytel.n
et [208.110.248.185]
7 76 ms 97 ms 74 ms bb-rcmtncxa-jx9-02-xe-1-2-0.core.centurytel.net
[208.110.248.157]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 80 ms 76 ms 75 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 79 ms 79 ms 79 ms 65.120.117.250
13 232 ms 220 ms 210 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 215 ms 212 ms 208 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 201 ms 204 ms 197 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

^ As is this on the same day!

11 113 ms 106 ms 111 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 173 ms 116 ms 121 ms 65.120.117.250
13 142 ms 165 ms 125 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
14 297 ms 290 ms 312 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 198 ms 187 ms 179 ms 208.95.186.32

^Common bad and/or typical day

VS

11 77 ms 77 ms 77 ms bst-edge-05.inet.qwest.net [67.14.30.126]
12 80 ms 81 ms 81 ms 65.120.117.250
13 82 ms 81 ms 85 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 88 ms 89 ms 88 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 80 ms 79 ms 79 ms patchserver2.crypticstudios.com [208.95.185.41]

^Good day.

grouchyotaku

shadowwraith77 wrote: »

Here's my results, since the so called server stability update of today!

...

contacting nettest server..
Local IP: 76.2.109.15
Ping: 79.2 msec
Port: 80: 413 KB/sec 15 KB/sec 437 KB/sec 500
Port: 80: 413 KB/sec 15 KB/sec 436 KB/sec 500
Port: 443: 70 KB/sec 3 KB/sec 75 KB/sec 500
Port: 443: 153 KB/sec 6 KB/sec 162 KB/sec 500
Port: 7255: 173 KB/sec 6 KB/sec 183 KB/sec 500
Port: 7255: 413 KB/sec 15 KB/sec 438 KB/sec 500
Port: 7003: 413 KB/sec 15 KB/sec 437 KB/sec 500
Port: 7003: 232 KB/sec 9 KB/sec 247 KB/sec 500
Port: 7202: 83 KB/sec 3 KB/sec 88 KB/sec 500
Port: 7202: 164 KB/sec 7 KB/sec 176 KB/sec 500
Port: 7499: 138 KB/sec 14 KB/sec 191 KB/sec 500
Port: 7499: 413 KB/sec 15 KB/sec 436 KB/sec 500
Port: 80: 53 KB/sec 2 KB/sec 57 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

Ports 80, 443, 7255, 7003, 7202, 7499 seem like they are a problem, when compared to good connection tested before server stability updates.

....

Now this shows that your problems playing STO has nothing to do with the STO Servers. 'Net Test' does not connect to the STO Servers, it connects to a diagnostic server located on the same local network as the STO Servers, so the STO Servers are out of the picture with the 'Net Test' results. If you can't do a 300 KB/sec sustained network throughput to a simple diagnostic server, its unlikely you can do the same with the STO Servers...

It looks like you have the same issues with the Quest Communications backbone that other people are having...

shadowwraith77

grouchyotaku wrote: »

Now this shows that your problems playing STO has nothing to do with the STO Servers. 'Net Test' does not connect to the STO Servers, it connects to a diagnostic server located on the same local network as the STO Servers, so the STO Servers are out of the picture with the 'Net Test' results. If you can't do a 300 KB/sec sustained network throughput to a simple diagnostic server, its unlikely you can do the same with the STO Servers...

It looks like you have the same issues with the Quest Communications backbone that other people are having...

Here's the thing, running a nettest by pinging any # of California based servers, give me the expected latency as normal and, download/upload speeds as well.

All I had to do to stay connected, was actually use a proxy server in the launcher options tonight, something I have never had to do EVER.

Stable as can be going this route but, try and not use it and whammo DC + SNR out the whazoo, yet it takes no more than like I said 3-5secs to re-log in each and every time so, re-establishing a connection is super fast only it doesn't last at all.

ONLY does this issue EVER arise from this game server base/client, as I have never had this kind of issue with any other MMO server base, unless their actual server crashed.

No, network related problems, no connection issues all night, except when either connecting to STO and, trying to post on the STO forums.

Both, had problematic connection issues for me!

Now, granted Quest is one of the hops that cause my first set of latency but, after that it is usually from the long connection line to California and back but, is usually no greater than 110ms.

As you can see from tonight, it was decent except when 15 did not respond, which is something it has never done except when I have connection issue with the server as well.

grouchyotaku

shadowwraith77 wrote: »

Here's the thing, running a nettest by pinging any # of California based servers, give me the expected latency as normal and, download/upload speeds as well.

All I had to do to stay connected, was actually use a proxy server in the launcher options tonight, something I have never had to do EVER.

Stable as can be going this route but, try and not use it and whammo DC + SNR out the whazoo, yet it takes no more than like I said 3-5secs to re-log in each and every time so, re-establishing a connection is super fast only it doesn't last at all.
...

You have to keep in mind that 'Ping' and 'Trace Route' are incomplete network diagnostic tools, as they only check for network latency. What they don't check for is lost data packets and broken connections. The 'Net Test' diagnostics will show the effects of packet loss, as the TCP/IP request to resend a missing packet will take additional time and lowers the sustain network connection throughput that 'Net Test' measures...

The only listed network diagnostic that actually checks for 'packet loss' is the 'Path Ping' diagnostics, which you have not included in your postings...

shadowwraith77

grouchyotaku wrote: »

You have to keep in mind that 'Ping' and 'Trace Route' are incomplete network diagnostic tools, as they only check for network latency. What they don't check for is lost data packets and broken connections. The 'Net Test' diagnostics will show the effects of packet loss, as the TCP/IP request to resend a missing packet will take additional time and lowers the sustain network connection throughput that 'Net Test' measures...

The only listed network diagnostic that actually checks for 'packet loss' is the 'Path Ping' diagnostics, which you have not included in your postings...

I ran a packet loss nettest and, only 1 hop showed a loss of 1, count it 1 packet loss, whilst all others showed a loss of absolutely 0.

Yet, without the use of the proxy server for the night, I could not sustain a connection for more than maybe 3mins tops, than it was SNR and/or DC (boot).

I get that there are any # of factors that could have caused or, are causing this but, it remains a factor mostly involving Crytpic servers.

Seeing how they have only so many servers under 1 server name, to serve the entire world.

Other games I have played, seem to separate their servers, into multiple server worlds but, not all companies do this and, by far the worse of them are the ones that think using host based connections was the best idea. (yeah we know well that works, when someone else has to host a gamin session for others, when the U.S. intranet highway is so tightly regulated by ISP companies and, not the actual FCC.)

grouchyotaku

shadowwraith77 wrote: »

I ran a packet loss nettest and, only 1 hop showed a loss of 1, count it 1 packet loss, whilst all others showed a loss of absolutely 0.

Yet, without the use of the proxy server for the night, I could not sustain a connection for more than maybe 3mins tops, than it was SNR and/or DC (boot).

I get that there are any # of factors that could have caused or, are causing this but, it remains a factor mostly involving Crytpic servers.

...

Actually, the 1 means 1% packet loss, or 1 packet is lost for every 100 packets sent... For a reliable connection, you should be having ZERO PACKET LOSS, as even a 1% packet loss can cause lag and broken connections...

This also means that you can't be blaming the STO Servers for your connection problems until after you've eliminated all sources of of lost packets first, as a 1% packet loss can easily be responsible for the connection problems you're having...

shadowwraith77

grouchyotaku wrote: »

Actually, the 1 means 1% packet loss, or 1 packet is lost for every 100 packets sent... For a reliable connection, you should be having ZERO PACKET LOSS, as even a 1% packet loss can cause lag and broken connections...

This also means that you can't be blaming the STO Servers for your connection problems until after you've eliminated all sources of of lost packets first, as a 1% packet loss can easily be responsible for the connection problems you're having...

I've had far worse, than a 1% packet loss with a DDO server before (located in Boston) and, not lost connection nor, had SNR's + DC's anywhere near as bad as STO's server base!

Yes, that 1% can cause issues but, it seems funny that it would cause a hiccup just long enough to give me countless secs. of SNR (15+ or more per STF) + 1-10 DC's in the same freaking mission. And, this is all within the first 3-5mins. sometime but, takes me a mere 5secs to re-connect like nothing ever happened and, back into the mission right where I essentially left off?

Seems more like the account system fighting with me, by booting me constantly in favor for the next person logging in or, worse yet a gold account priority logging in.

It may not be the server as in hardware but, it could be the server software and/or even the ISP for those servers, that can be lending some of the issue as well.