With such a route, Cryptic will most likely try to scapegoat node #9.
From my tracert it likes like node 9 has either been looted or burned down as it is missing 🤣 so you could be right
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 10 ms 10 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 13 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 13 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 94 ms 94 ms 90 ms 198.49.243.237
12 93 ms 88 ms 87 ms patchserver.crypticstudios.com [208.95.184.200]
With such a route, Cryptic will most likely try to scapegoat node #9.
From my tracert it likes like node 9 has either been looted or burned down as it is missing 🤣 so you could be right
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 10 ms 10 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 13 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 13 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 94 ms 94 ms 90 ms 198.49.243.237
12 93 ms 88 ms 87 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Or could be part of the state that doesn't have power because... taking a power plant offline before you have a suitable power generation replacement obviously makes sense. :P
Or could be part of the state that doesn't have power because... taking a power plant offline before you have a suitable power generation replacement obviously makes sense. :P
You obviously didn't think your asinine statement through before posting, did you?
With such a route, Cryptic will most likely try to scapegoat node #9.
From my tracert it likes like node 9 has either been looted or burned down as it is missing 🤣 so you could be right
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 10 ms 10 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 13 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 13 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 94 ms 94 ms 90 ms 198.49.243.237
12 93 ms 88 ms 87 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
That tracert looks just about reasonable as those speeds STO should be playable without rubberbanding. Although I say should I know what STO is like and that's assuming your node 9 ok.
Your node 9 is my node 14 and that is the node that 9 times out of 10 is the cause of the major lag and rubberbanding. node 9 is the one that spikes up to 300 or sometimes even 1000+ ms which match's when the lag/rubberbanding hits in STO.
"14 93 ms 94 ms 91 ms 93.191.173.69" is what your node 9 gives me today.
The two problems with tracert is it doesn't show a lot of game side lag that's triggered by actions in the game and the other major problem is the lag is often only a split second. Unless you time the tracert perfectly and start it seconds before the lag hits the node causing problems wont show if the node is only spiking badly briefly which seems to be what is happening for us. It can be done just its very difficult to get the timings right when the lag is random. When I did it I had to run tracert none stop for an while and match the timestamps to the tracert runs. Which painted a very different picture then just running the 1 or 2 tracert at random times.
For a change STO has been reasonably lag free the past 2 days for me. Not perfect but playable. Think that's about the 4 days total in 2 years playing daily where its been reasonable.
Well I take that back only managed 2 hours without lag. So back down to 2 lag free days in the past 2 years.
Starting getting rubberbanding. Not the normal problem node but still Akamai causing the problem.
11 459 ms * 67 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
11 502 ms 346 ms 159 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
12 302 ms 266 ms 105 ms a72-52-1-133.deploy.static.akamaitechnologies.com [72.52.1.133]
Well I take that back only managed 2 hours without lag. So back down to 2 lag free days in the past 2 years.
Starting getting rubberbanding. Not the normal problem node but still Akamai causing the problem.
11 459 ms * 67 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
I have turned off bloom and shadows the past week and it has improved for unknowns my rubberbanding. I'll still get random spikes but not every 30 secs or 2 mins. I even went on one character 2hrs without connection issues which is how the game should run and used to run. Then switched toons and the game made up for that it by having a fit on the new character
Well I take that back only managed 2 hours without lag. So back down to 2 lag free days in the past 2 years.
Starting getting rubberbanding. Not the normal problem node but still Akamai causing the problem.
11 459 ms * 67 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
I have turned off bloom and shadows the past week and it has improved for unknowns my rubberbanding. I'll still get random spikes but not every 30 secs or 2 mins. I even went on one character 2hrs without connection issues which is how the game should run and used to run. Then switched toons and the game made up for that it by having a fit on the new character
There do seem to be a lot of UI problems at the moment on top of all the other ones listed, I noticed when I open the powers page up while in ESD space very often the FPS go from 140fps down to 6fps. Soon as that powers UI page is closed the FPS jump right back up. Although not network lag 6fps feels the same as network lag though this was clearly a graphicly UI problem.
Lovely rubber banding spike and lag at the end of Crystal Entity I wonder where along the connection path the problem might be?
1 5 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 11 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 12 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 621 ms 425 ms 266 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 93 ms 94 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 104 ms 98 ms 99 ms 198.49.243.237
12 93 ms 93 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
So i don't post much on forums but i thought i might for this issues to find out if this lag and rubber banding is becuase of any recent issues as the game is acting like it did the the old Atari Cryptic days with just some awful lag and rubber banding, and it seem quite constant at the moment, and i am in the UK and have picked the EU server but that does not seem to have made any difference, so i wonder is there anything i can do on my end to solve this, or is this a game server issue thing that i have no control over.......thanks for any help.
Lord of the Rings Online is also based on Servers in Boston and has/is having lag issues as well. In fact they reported yesterday that there was some external issue affecting Server stability. Akamai is also in the picture there as well.
True (I play there as well), but the issues in STO have been around FAR longer than the recent LotRO problems.
Lovely rubber banding spike and lag at the end of Crystal Entity I wonder where along the connection path the problem might be?
1 5 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 11 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 12 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 621 ms 425 ms 266 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 93 ms 94 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 104 ms 98 ms 99 ms 198.49.243.237
12 93 ms 93 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
Yep and mine has four timeouts...
Not to mention 15 minutes just to get past login screen -I got a 3mb connection SUE me!
Forget calling it rubberbanding... for it so bad now that I going to call it LAG WARP!.... lot less to say than rubberbanding.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 12 ms 12 ms 12 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 14 ms 12 ms akamai.prolexic.com [195.66.224.31]
6 565 ms 504 ms 450 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 22 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 91 ms 89 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 98 ms 90 ms 90 ms 198.49.243.237
12 88 ms 88 ms 88 ms patchserver.crypticstudios.com [208.95.184.200]
Sat in Dyson Contested Space doing Admiralty
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 12 ms 12 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 14 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 14 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 321 ms 395 ms 78 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 89 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 98 ms 91 ms 91 ms 198.49.243.237
12 89 ms 88 ms 89 ms patchserver.crypticstudios.com [208.95.184.200]
so i wonder is there anything i can do on my end to solve this, or is this a game server issue thing that i have no control over.......thanks for any help.
its cryptic (some would argue no).
but suffice to say its not you.
Ok that is fine, at least its not on my end, thank you.
I been doing a lot of testing lately, with all the latest DC's.. and well, what i thik is that Akamai is giving priority connection to US based clients, as i'm connecting from south america, i have no priority and a lot of DC's (BTW i tested with SWTOR and no problem at al), but when i proxy from US, with a VPN, well, no DC's at all.. lag still.. less... but still. I just recoment to people that if you are having too much disconects use a VPN program like Windscribe or similar, you will get a better and stable connection.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 10 ms 7 ms 9 ms 96.120.90.113
3 9 ms 8 ms 9 ms po-302-1221-rur01.napa.ca.sfba.comcast.net [162.151.31.29]
4 10 ms 10 ms 11 ms be-201-rar01.rohnertpr.ca.sfba.comcast.net [68.85.57.249]
5 15 ms 16 ms 14 ms be-297-ar01.santaclara.ca.sfba.comcast.net [96.108.99.13]
6 17 ms 20 ms 14 ms be-36341-cs04.sunnyvale.ca.ibone.comcast.net [96.110.41.77]
7 22 ms 13 ms 15 ms be-3411-pe11.529bryant.ca.ibone.comcast.net [96.110.33.94]
8 16 ms 14 ms 21 ms 50.208.233.210
9 15 ms 15 ms 15 ms sjo-b21-link.telia.net [62.115.115.217]
10 14 ms 16 ms 13 ms akamai-ic-317096-sjo-b21.c.telia.net [62.115.146.119]
11 14 ms 24 ms 13 ms po110.bs-a.sech-sjc.netarch.akamai.com [209.200.184.192]
12 * * * Request timed out.
13 14 ms 17 ms 13 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
14 87 ms 86 ms 88 ms a72-52-28-178.deploy.static.akamaitechnologies.com [72.52.28.178]
15 99 ms 95 ms 88 ms 198.49.243.237
16 85 ms 86 ms 91 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Been in the Dyson ground battlezone for about 10 minutes, and I'm being rubberbanded at least three times EACH minute. In other words...I literally can't do much of ANYTHING in here.
I been doing a lot of testing lately, with all the latest DC's.. and well, what i thik is that Akamai is giving priority connection to US based clients, as i'm connecting from south america, i have no priority and a lot of DC's (BTW i tested with SWTOR and no problem at al), but when i proxy from US, with a VPN, well, no DC's at all.. lag still.. less... but still. I just recoment to people that if you are having too much disconects use a VPN program like Windscribe or similar, you will get a better and stable connection.
Glad the VPN works for you and I tested WTFast which was better but didn't eliminate all rubber banding but on principle I refuse to pay an additional subscription to the game when it was Cryptic/PWE who went and flurked up the connection with the ISP they chose. Before the network upgrades made back in 2016 I had little to no connection issues unless there was a real issue rather than some hatchet job 3rd party throttling or bottlenecking my connection to Cryptic/PWE servers like Akamai seem to be doing. It is Cryptic's/PWE reasonability to fix at no expense of mine if they wise to keep my business
I been doing a lot of testing lately, with all the latest DC's.. and well, what i thik is that Akamai is giving priority connection to US based clients, as i'm connecting from south america, i have no priority and a lot of DC's (BTW i tested with SWTOR and no problem at al), but when i proxy from US, with a VPN, well, no DC's at all.. lag still.. less... but still. I just recoment to people that if you are having too much disconects use a VPN program like Windscribe or similar, you will get a better and stable connection.
Glad the VPN works for you and I tested WTFast which was better but didn't eliminate all rubber banding but on principle I refuse to pay an additional subscription to the game when it was Cryptic/PWE who went and flurked up the connection with the ISP they chose.
I totally agree. I've already vowed to not dump any more REAL money into this game, and I'd encourage others to do the same. Once this starts hurting them financially, only THEN will something be done to remedy this issue. I normally enjoy the summer event...but not this year. Almost every single race, air or ground, I've been jacked out of first place, or just flat out DISQUALIFIED, because I get rubberbanded.
Last night, went on my Delta Recruit character on Risa. Did the Risian Scavenger Hunt on that character for the bonus dilithium. Then logged off that character and was preceding to the next one. When the game froze and stayed frozen for a long time. Then after a lot of minutes passed got to the picturesque character screen where it then crashed to desktop. I quit after that and went to bed.
Had rubberbanding on Risa up until the last update. After that there's no rubblerbanding cause there is 0% connectivity. The game gets to the House Divided screen with the Klingon symbol, "Loading" comes up, and then it crash.es
I think the foundations of this game were build with rubber banding and filled in with lag. Its not improving it's gradually appearing to be getting worse again.
Right I'm out I'm done with this game. Feeling attached to a bungee cord and being rubber banded back constantly has finally broke my resolve to continue playing this game I'm finished. I'll go find a another game and a better company that supports it's own product
Ok clamed down a bit now still very pissed at server performance and will not drop a single penny on this game again until it back to pre-2016 standards. Hell I had a better experience when this game had a iMac port, worked better on that platform than it has ever done on Windows it's primary platform.
Mood swings having to make a few lifestyle changes after hitting diabetes type 2 threshold and going sugar free.
This was beyond silly. Combat over just standing around looking at my power tray, no powers active. Suddenly rubberband forward into plasma fire die and get an injury. Res myself, walk out fire and heal only to again rubberband forward into Plasma fire dyeing again and another injury. Just how is this meant to be playable and how do you expect us to spend money on the game when this is what we experience.
12 21 ms 23 ms 19 ms a72-52-1-133.deploy.static.akamaitechnologies.com [72.52.1.133]
13 21 ms 20 ms 19 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197] 14 280 ms * * 93.191.173.69
15 * 102 ms 102 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
16 108 ms 99 ms 99 ms 198.49.243.237
17 98 ms 95 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
13 21 ms 20 ms 25 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197] 14 * 339 ms 281 ms 93.191.173.69
15 99 ms 95 ms 99 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
16 113 ms 102 ms 98 ms 198.49.243.237
17 96 ms 95 ms 92 ms patchserver.crypticstudios.com [208.95.184.200]
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 10 ms 11 ms renf-core-2a-xe-033-0.network.virginmedia.net [62.252.129.157]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 20 ms 21 ms 20 ms tclo-ic-3-ae0-0.network.virginmedia.net [212.250.25.62]
8 21 ms 22 ms 20 ms akamai.prolexic.com [195.66.224.31]
9 20 ms 21 ms 22 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
10 21 ms 21 ms 21 ms a72-52-1-169.deploy.static.akamaitechnologies.com [72.52.1.169]
11 21 ms 21 ms 22 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
12 96 ms 93 ms 92 ms 93.191.173.11
13 101 ms 101 ms 99 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
14 104 ms 102 ms 98 ms 198.49.243.237
15 100 ms 94 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
As I'm sure it's been reported elsewhere, how 'bout fixing the graphics for the Atrox Carrier. It currently looks like an amputee in space:
If you go to the tailor and select the Atrox Carrier skin, save, and leave the tailor then it should revert back to what it is supposed to be. Also, if you believe it is a bug please post it in the respective bug reports forum whether it be PC, PS4, or Xbox One and not here. Since this has nothing to do with performance issues. That has to do with the lag and rubberbanding in this game. Thanks.
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 13 ms 11 ms 12 ms 84.116.198.89
2 11 ms 12 ms 13 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 21 ms 14 ms 17 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 13 ms 11 ms 12 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 11 ms 12 ms ffm-bb2-link.telia.net [62.115.137.166]
6 13 ms 12 ms 11 ms ffm-b5-link.telia.net [62.115.114.91]
7 12 ms 13 ms 13 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 13 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 13 ms 12 ms 12 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 127 ms 130 ms 129 ms 93.191.173.63
13 142 ms 141 ms 144 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
14 153 ms 143 ms 147 ms 198.49.243.237
15 141 ms 140 ms 142 ms patchserver.crypticstudios.com [208.95.184.200]
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 23 ms 11 ms 12 ms 84.116.198.89
2 16 ms 14 ms 13 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 12 ms 13 ms 11 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 11 ms 11 ms 11 ms ffm-b1-link.telia.net [62.115.42.170]
5 14 ms 12 ms 13 ms ffm-bb2-link.telia.net [62.115.137.166]
6 12 ms 12 ms 13 ms ffm-b5-link.telia.net [62.115.114.91]
7 31 ms 13 ms 13 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 20 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 12 ms 14 ms 12 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 133 ms 128 ms 181 ms 93.191.173.63
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * 101 ms 101 ms patchserver.crypticstudios.com [208.95.184.200]
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 11 ms 11 ms 11 ms 84.116.198.89
2 11 ms 12 ms 12 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 12 ms 11 ms 12 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 13 ms 12 ms 15 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 13 ms 12 ms ffm-bb2-link.telia.net [62.115.137.166]
6 12 ms 12 ms 14 ms ffm-b5-link.telia.net [62.115.114.91]
7 11 ms 12 ms 12 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 13 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 13 ms 12 ms 13 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 154 ms 126 ms 124 ms 93.191.173.63
13 138 ms 138 ms 137 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
14 150 ms 143 ms 139 ms 198.49.243.237
15 141 ms 136 ms 137 ms patchserver.crypticstudios.com [208.95.184.200]
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 11 ms 11 ms 15 ms 84.116.198.89
2 14 ms 11 ms 11 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 11 ms 11 ms 12 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 46 ms 21 ms 15 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 12 ms 13 ms ffm-bb2-link.telia.net [62.115.137.166]
6 13 ms 12 ms 12 ms ffm-b5-link.telia.net [62.115.114.91]
7 12 ms 11 ms 12 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 12 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 12 ms 13 ms 13 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 124 ms 193 ms 126 ms 93.191.173.63
13 * * * Zeitüberschreitung der Anforderung.
14 144 ms 139 ms 140 ms 198.49.243.237
15 * * * Zeitüberschreitung der Anforderung.
16 * * 137 ms patchserver.crypticstudios.com [208.95.184.200]
Comments
From my tracert it likes like node 9 has either been looted or burned down as it is missing 🤣 so you could be right
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 10 ms 10 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 13 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 13 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 94 ms 94 ms 90 ms 198.49.243.237
12 93 ms 88 ms 87 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Or could be part of the state that doesn't have power because... taking a power plant offline before you have a suitable power generation replacement obviously makes sense. :P
You obviously didn't think your asinine statement through before posting, did you?
Your node 9 is my node 14 and that is the node that 9 times out of 10 is the cause of the major lag and rubberbanding. node 9 is the one that spikes up to 300 or sometimes even 1000+ ms which match's when the lag/rubberbanding hits in STO.
"14 93 ms 94 ms 91 ms 93.191.173.69" is what your node 9 gives me today.
The two problems with tracert is it doesn't show a lot of game side lag that's triggered by actions in the game and the other major problem is the lag is often only a split second. Unless you time the tracert perfectly and start it seconds before the lag hits the node causing problems wont show if the node is only spiking badly briefly which seems to be what is happening for us. It can be done just its very difficult to get the timings right when the lag is random. When I did it I had to run tracert none stop for an while and match the timestamps to the tracert runs. Which painted a very different picture then just running the 1 or 2 tracert at random times.
For a change STO has been reasonably lag free the past 2 days for me. Not perfect but playable. Think that's about the 4 days total in 2 years playing daily where its been reasonable.
Starting getting rubberbanding. Not the normal problem node but still Akamai causing the problem.
11 459 ms * 67 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
11 502 ms 346 ms 159 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
12 302 ms 266 ms 105 ms a72-52-1-133.deploy.static.akamaitechnologies.com [72.52.1.133]
I have turned off bloom and shadows the past week and it has improved for unknowns my rubberbanding. I'll still get random spikes but not every 30 secs or 2 mins. I even went on one character 2hrs without connection issues which is how the game should run and used to run. Then switched toons and the game made up for that it by having a fit on the new character
1 5 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 11 ms 11 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 12 ms 13 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 621 ms 425 ms 266 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 94 ms 93 ms 94 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 104 ms 98 ms 99 ms 198.49.243.237
12 93 ms 93 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
Yep and mine has four timeouts...
Not to mention 15 minutes just to get past login screen -I got a 3mb connection SUE me!
Forget calling it rubberbanding... for it so bad now that I going to call it LAG WARP!.... lot less to say than rubberbanding.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 12 ms 12 ms 12 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 14 ms 12 ms akamai.prolexic.com [195.66.224.31]
6 565 ms 504 ms 450 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 13 ms 13 ms 22 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 91 ms 89 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 98 ms 90 ms 90 ms 198.49.243.237
12 88 ms 88 ms 88 ms patchserver.crypticstudios.com [208.95.184.200]
Sat in Dyson Contested Space doing Admiralty
1 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ae54-ner002.csm.as13285.net [78.144.1.19]
4 11 ms 12 ms 12 ms ae54-scr101.loh.as13285.net [78.144.1.18]
5 13 ms 13 ms 14 ms akamai.prolexic.com [195.66.224.31]
6 13 ms 13 ms 14 ms po110.bs-b.sech-lon2.netarch.akamai.com [72.52.60.200]
7 321 ms 395 ms 78 ms a72-52-1-199.deploy.static.akamaitechnologies.com [72.52.1.199]
8 13 ms 13 ms 13 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 89 ms 88 ms 88 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
11 98 ms 91 ms 91 ms 198.49.243.237
12 89 ms 88 ms 89 ms patchserver.crypticstudios.com [208.95.184.200]
Ok that is fine, at least its not on my end, thank you.
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.1
2 10 ms 7 ms 9 ms 96.120.90.113
3 9 ms 8 ms 9 ms po-302-1221-rur01.napa.ca.sfba.comcast.net [162.151.31.29]
4 10 ms 10 ms 11 ms be-201-rar01.rohnertpr.ca.sfba.comcast.net [68.85.57.249]
5 15 ms 16 ms 14 ms be-297-ar01.santaclara.ca.sfba.comcast.net [96.108.99.13]
6 17 ms 20 ms 14 ms be-36341-cs04.sunnyvale.ca.ibone.comcast.net [96.110.41.77]
7 22 ms 13 ms 15 ms be-3411-pe11.529bryant.ca.ibone.comcast.net [96.110.33.94]
8 16 ms 14 ms 21 ms 50.208.233.210
9 15 ms 15 ms 15 ms sjo-b21-link.telia.net [62.115.115.217]
10 14 ms 16 ms 13 ms akamai-ic-317096-sjo-b21.c.telia.net [62.115.146.119]
11 14 ms 24 ms 13 ms po110.bs-a.sech-sjc.netarch.akamai.com [209.200.184.192]
12 * * * Request timed out.
13 14 ms 17 ms 13 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
14 87 ms 86 ms 88 ms a72-52-28-178.deploy.static.akamaitechnologies.com [72.52.28.178]
15 99 ms 95 ms 88 ms 198.49.243.237
16 85 ms 86 ms 91 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Been in the Dyson ground battlezone for about 10 minutes, and I'm being rubberbanded at least three times EACH minute. In other words...I literally can't do much of ANYTHING in here.
Glad the VPN works for you and I tested WTFast which was better but didn't eliminate all rubber banding but on principle I refuse to pay an additional subscription to the game when it was Cryptic/PWE who went and flurked up the connection with the ISP they chose. Before the network upgrades made back in 2016 I had little to no connection issues unless there was a real issue rather than some hatchet job 3rd party throttling or bottlenecking my connection to Cryptic/PWE servers like Akamai seem to be doing. It is Cryptic's/PWE reasonability to fix at no expense of mine if they wise to keep my business
I totally agree. I've already vowed to not dump any more REAL money into this game, and I'd encourage others to do the same. Once this starts hurting them financially, only THEN will something be done to remedy this issue. I normally enjoy the summer event...but not this year. Almost every single race, air or ground, I've been jacked out of first place, or just flat out DISQUALIFIED, because I get rubberbanded.
Ok clamed down a bit now still very pissed at server performance and will not drop a single penny on this game again until it back to pre-2016 standards. Hell I had a better experience when this game had a iMac port, worked better on that platform than it has ever done on Windows it's primary platform.
Mood swings having to make a few lifestyle changes after hitting diabetes type 2 threshold and going sugar free.
12 21 ms 23 ms 19 ms a72-52-1-133.deploy.static.akamaitechnologies.com [72.52.1.133]
13 21 ms 20 ms 19 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
14 280 ms * * 93.191.173.69
15 * 102 ms 102 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
16 108 ms 99 ms 99 ms 198.49.243.237
17 98 ms 95 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
13 21 ms 20 ms 25 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
14 * 339 ms 281 ms 93.191.173.69
15 99 ms 95 ms 99 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
16 113 ms 102 ms 98 ms 198.49.243.237
17 96 ms 95 ms 92 ms patchserver.crypticstudios.com [208.95.184.200]
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 10 ms 11 ms renf-core-2a-xe-033-0.network.virginmedia.net [62.252.129.157]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 20 ms 21 ms 20 ms tclo-ic-3-ae0-0.network.virginmedia.net [212.250.25.62]
8 21 ms 22 ms 20 ms akamai.prolexic.com [195.66.224.31]
9 20 ms 21 ms 22 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
10 21 ms 21 ms 21 ms a72-52-1-169.deploy.static.akamaitechnologies.com [72.52.1.169]
11 21 ms 21 ms 22 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
12 96 ms 93 ms 92 ms 93.191.173.11
13 101 ms 101 ms 99 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
14 104 ms 102 ms 98 ms 198.49.243.237
15 100 ms 94 ms 93 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
If you go to the tailor and select the Atrox Carrier skin, save, and leave the tailor then it should revert back to what it is supposed to be. Also, if you believe it is a bug please post it in the respective bug reports forum whether it be PC, PS4, or Xbox One and not here. Since this has nothing to do with performance issues. That has to do with the lag and rubberbanding in this game. Thanks.
C:\Windows\System32>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 13 ms 11 ms 12 ms 84.116.198.89
2 11 ms 12 ms 13 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 21 ms 14 ms 17 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 13 ms 11 ms 12 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 11 ms 12 ms ffm-bb2-link.telia.net [62.115.137.166]
6 13 ms 12 ms 11 ms ffm-b5-link.telia.net [62.115.114.91]
7 12 ms 13 ms 13 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 13 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 13 ms 12 ms 12 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 127 ms 130 ms 129 ms 93.191.173.63
13 142 ms 141 ms 144 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
14 153 ms 143 ms 147 ms 198.49.243.237
15 141 ms 140 ms 142 ms patchserver.crypticstudios.com [208.95.184.200]
Ablaufverfolgung beendet.
C:\Windows\System32>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 23 ms 11 ms 12 ms 84.116.198.89
2 16 ms 14 ms 13 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 12 ms 13 ms 11 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 11 ms 11 ms 11 ms ffm-b1-link.telia.net [62.115.42.170]
5 14 ms 12 ms 13 ms ffm-bb2-link.telia.net [62.115.137.166]
6 12 ms 12 ms 13 ms ffm-b5-link.telia.net [62.115.114.91]
7 31 ms 13 ms 13 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 20 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 12 ms 14 ms 12 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 133 ms 128 ms 181 ms 93.191.173.63
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * 101 ms 101 ms patchserver.crypticstudios.com [208.95.184.200]
Ablaufverfolgung beendet.
C:\Windows\System32>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 11 ms 11 ms 11 ms 84.116.198.89
2 11 ms 12 ms 12 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 12 ms 11 ms 12 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 13 ms 12 ms 15 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 13 ms 12 ms ffm-bb2-link.telia.net [62.115.137.166]
6 12 ms 12 ms 14 ms ffm-b5-link.telia.net [62.115.114.91]
7 11 ms 12 ms 12 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 13 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 13 ms 12 ms 13 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 154 ms 126 ms 124 ms 93.191.173.63
13 138 ms 138 ms 137 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
14 150 ms 143 ms 139 ms 198.49.243.237
15 141 ms 136 ms 137 ms patchserver.crypticstudios.com [208.95.184.200]
Ablaufverfolgung beendet.
C:\Windows\System32>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.184.200]
über maximal 30 Hops:
1 11 ms 11 ms 15 ms 84.116.198.89
2 14 ms 11 ms 11 ms de-fra04a-rc1-ae23.fra.unity-media.net [81.210.141.29]
3 11 ms 11 ms 12 ms de-fra11b-ri1-ae-5-0.aorta.net [84.116.134.217]
4 46 ms 21 ms 15 ms ffm-b1-link.telia.net [62.115.42.170]
5 12 ms 12 ms 13 ms ffm-bb2-link.telia.net [62.115.137.166]
6 13 ms 12 ms 12 ms ffm-b5-link.telia.net [62.115.114.91]
7 12 ms 11 ms 12 ms ffm-b4-link.telia.net [62.115.116.17]
8 12 ms 12 ms 12 ms akamai-ic-317168-ffm-b4.c.telia.net [62.115.149.29]
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 12 ms 13 ms 13 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
12 124 ms 193 ms 126 ms 93.191.173.63
13 * * * Zeitüberschreitung der Anforderung.
14 144 ms 139 ms 140 ms 198.49.243.237
15 * * * Zeitüberschreitung der Anforderung.
16 * * 137 ms patchserver.crypticstudios.com [208.95.184.200]
Ablaufverfolgung beendet.
YouTube: MitNaqt Facebook: STO Neuling