I (and several of my fleet members) have started receiving intermittent instances of lag including
SNR's and DC's. I, personally, haven't had a single DC or SNR before this week. Most of the time it plays fine and then randomly whammo... SNR for 5-20 seconds and chance to DC. I've released my IP and refreshed it and tried using a proxy to no avail.
It is broken... make it go
tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms dsldevice.att.net [192.168.1.254]
2 1110 ms 1147 ms 1320 ms 104-50-164-3.lightspeed.jcsnms.sbcglobal.net [104.50.164.3]
3 * * 28 ms 99.183.77.80
4 31 ms 26 ms 25 ms 12.83.102.21
5 44 ms 30 ms 37 ms 12.122.157.34
6 31 ms 34 ms 37 ms ggr3.dlstx.ip.att.net [12.122.138.17]
7 32 ms 31 ms 32 ms 192.205.36.222
8 46 ms 31 ms 32 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
9 42 ms 41 ms 42 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.113]
10 58 ms 57 ms 59 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
11 71 ms 71 ms 73 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
12 72 ms 72 ms 73 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 84 ms 70 ms 71 ms 38.111.40.114
14 71 ms 74 ms 71 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: None of your business
Ping: 71.7 msec
Port: 80: 237 KB/sec 9 KB/sec 251 KB/sec 500
Port: 80: 124 KB/sec 5 KB/sec 135 KB/sec 500
Port: 443: 159 KB/sec 8 KB/sec 175 KB/sec 500
Port: 443: 59 KB/sec 2 KB/sec 64 KB/sec 500
Port: 7255: 129 KB/sec 5 KB/sec 138 KB/sec 500
Port: 7255: 62 KB/sec 4 KB/sec 76 KB/sec 500
Port: 7003: 156 KB/sec 18 KB/sec 213 KB/sec 500
Port: 7003: 204 KB/sec 9 KB/sec 218 KB/sec 500
Port: 7202: 103 KB/sec 12 KB/sec 131 KB/sec 500
Port: 7202: 153 KB/sec 8 KB/sec 167 KB/sec 500
Port: 7499: 193 KB/sec 9 KB/sec 214 KB/sec 500
Port: 7499: 169 KB/sec 8 KB/sec 186 KB/sec 500
Port: 80: 136 KB/sec 5 KB/sec 146 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
pathping patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 REDACTED.att.net [192.168.1.246]
1 dsldevice.att.net [192.168.1.254]
2 104-50-164-3.lightspeed.jcsnms.sbcglobal.net [104.50.164.3]
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 REDACTED.att.net [192.168.1.246]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.att.net [192.168.1.254]
0/ 100 = 0% |
2 61ms 0/ 100 = 0% 0/ 100 = 0% 104-50-164-3.lightspeed.jcsnms.sbcglobal.net [104.50.164.3]
Trace complete.
also I'll include the pathping to the proxy... which...is a horribly mangled piece of festering data... yeah...
pathping us1.proxy.crypticstudios.com
Tracing route to us1.proxy.crypticstudios.com [208.95.184.152]
over a maximum of 30 hops:
0 REDACTED.att.net [192.168.1.246]
1 dsldevice.att.net [192.168.1.254]
2 104-50-164-3.lightspeed.jcsnms.sbcglobal.net [104.50.164.3]
3 * 99.183.77.80
4 12.83.102.13
5 12.122.157.34
6 ggr3.dlstx.ip.att.net [12.122.138.17]
7 192.205.36.222
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 208.95.185.226
15 us1.proxy.crypticstudios.com [208.95.184.152]
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 REDACTED.att.net [192.168.1.246]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.att.net [192.168.1.254]
0/ 100 = 0% |
2 78ms 0/ 100 = 0% 0/ 100 = 0% 104-50-164-3.lightspeed.jcsnms.sbcglobal.net [104.50.164.3]
0/ 100 = 0% |
3 69ms 0/ 100 = 0% 0/ 100 = 0% 99.183.77.80
0/ 100 = 0% |
4 82ms 20/ 100 = 20% 20/ 100 = 20% 12.83.102.13
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 12.122.157.34
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% ggr3.dlstx.ip.att.net [12.122.138.17]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 192.205.36.222
0/ 100 = 0% |
8 92ms 0/ 100 = 0% 0/ 100 = 0% be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.53]
0/ 100 = 0% |
9 107ms 0/ 100 = 0% 0/ 100 = 0% be2010.ccr22.mci01.atlas.cogentco.com [154.54.46.217]
0/ 100 = 0% |
10 126ms 0/ 100 = 0% 0/ 100 = 0% be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.118]
0/ 100 = 0% |
11 129ms 2/ 100 = 2% 2/ 100 = 2% be2138.ccr22.bos01.atlas.cogentco.com [154.54.43.202]
0/ 100 = 0% |
12 185ms 0/ 100 = 0% 0/ 100 = 0% te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
0/ 100 = 0% |
13 161ms 1/ 100 = 1% 1/ 100 = 1% 38.111.40.114
0/ 100 = 0% |
14 152ms 0/ 100 = 0% 0/ 100 = 0% 208.95.185.226
0/ 100 = 0% |
15 131ms 0/ 100 = 0% 0/ 100 = 0% us1.proxy.crypticstudios.com [208.95.184.152]
Trace complete.
Yeah, I don't really know what's all going on here but what I do know is that 1.) This didn't start until this week. 2.)Other fleet members are experiencing the same troubles (where there weren't any before 3.)The other fleet members who are experiencing these sudden troubles as I am are not even remotely in the same area or using the same ISP as I am. 4. I was (supposedly) recently upgraded to a low tier fiber optic internet service (much prior to this and without incident)
Comments
Now with 'Path Ping', a 100% packet loss could be a false positive, with the node simply not configured to support the network protocol that 'Path Ping' uses. But a 20% where some of the packets get processed, but others are lost, is a very real measurement... Looks like its time to contact your ISP Tech Support, and ask them why this is occurring, as you should have ZERO PACKET LOSS to maintain a reliable connection to the STO Servers...
edit
And again.
I really do believe that the 20% packet loss is also telling a story, as I wasn't experiencing a hint of lag at the time I posted. It also doesn't explain why other members of my fleet are experiencing the same problems out of the blue when just last week we were all lag free.
Also, that's the path ping of the proxy server. I don't use proxy, I used that because the path ping to the patch server timed out on the third hop and gave up...
Different problems can result in the same symptoms. Unless your other Fleet members post their network diagnostic results, its anyone's guess as to what is causing their problem. Obviously, this issue isn't effecting everyone, as the 'Winter Wonderland' is well stocked with active players...
And the fact that the third hop failed during the 'Path Ping' diagnostics is also indicative that there is a problem of some kind there...
I never mentioned winter wonderland. To date I have never had a problem with that map.
the strange thing is it seems to effect my TeamSpeak as well. i will get kicked off my net connection entirely and then reconnect.
can this be a bad program interaction STO client is causing in my system?
Random disconnects all day. Timed disconnects from exactly 8pm till 11 pm (ETC). Server online, but cannot connect to login server, while my friend 300km away can play perfectly. Or it is the other way around, I can play, but he is just waiting for the laucher to connect.
What is this? Everybody knows by now that this problems is the ISP of Arc (or cryptic or perfect world, I dont get it anymore who runs this game). Usually we germans are used to ****ty connections from US-Servers. But we have Netflix now too! Why dont we get the bandwidth we deserve?
I like STO really much. If it doesnt work..., well, there are numerous other space pew pew games to kill the 2-3 hours until connection is possible again.
BUT, I have one (or two) crucial question(s):
Why should I spend my precious money on a game, which doesnt let me play or connect or kicks me without warning? Why should I put money in a game which is not working properly?
Come on you cryptic ARC worlders! Even the 5 guys from Robocraft got their server issues ironed out after two weeks. Are you that lazy or are the guys from Robocraft that much more capable than you?
I am really astonished and disappointed about the network problems all the STO-players around the world experience...
We are the customers! Make us happy! Let us play!
Delta lagging is the best expansion ever and the players love rubberbanding, server not responding and connection issues
players don't need more than 2 playable pve elite space q's. they can throw snowballs
who cares about about broken pvp or missing ise, cse, kse or even, i risk mentioning it, new stf's.
we can open lockboxes and try getting to the exchange during extreme rubberbanding to buy more key's to open even more boxes. Maybe we're lucky and don't even have to walk the way more the twice
who needs endgamecontent? challenge is to even be able to end one of the few working elite space q's like borg disconnected without rubberbanding or forced logout which probably ruins the match for the rest teams cause at least another one got the same issues.
Also been getting a lot of rubber banding and very slow loadings. 0-3 percent loading is just crawling 0.1 percent at a time. Sometimes it takes 30 seconds or more to get a level 3 percent loaded. Then it slow down again around 40-50%. This is an issue that had been gone for me for over a month and just recently returned with the last patch.