I can't seem to upload a photo of my traceroute. But I did run one, and I seem to be encountering the SAME issue MOST seem to be running into. There is a massive bottleneck between 209.200.184.192 and 209.200.184.197 where "request timed out" I'm no expert by any means...but when I've read numerous people complaining about this "akamaitechnologies" and then seeing for myself...I kinda have to think that WHERE the problem is, seems pretty obvious. So if Cryptic REALLY wants to help, seems THAT'S where they need to look.
In response to 'how do I perform a traceroute' and 'I couldn't upload a photo' -
Open a command prompt and enter this: tracert patchserver.crypticstudios.com
You can highlight the text in the command prompt box, press CTRL + C to copy, and paste it into your post here or onto notepad. Feel free to edit out any of your own IP related info to taste.
I don't believe they're requiring a photo for this thread but if you encounter something that concerns you it wouldn't hurt to save some screen shots and of course the option is yours if you prefer to post a photo.
A image hosting service similar to imgur.com is needed to upload the photo to and then get a link from your photo hosting site for that photo.
Next select the 'image' function found at the top of your post window in this forum (4th from the right among the tools - looks like some mountains) and paste the link into the box that appears.
Edit (photos added):
Enter this: tracert patchserver.crypticstudios.com
To get your traceroute info:
*** If posting a photo please remove your full name from your user folder ***
In response to 'how do I perform a traceroute' and 'I couldn't upload a photo' -
Open a command prompt and enter this: tracert patchserver.crypticstudios.com
You can highlight the text in the command prompt box, press CTRL + C to copy, and paste it into your post here or onto notepad. Feel free to edit out any of your own IP related info to taste.
I don't believe they're requiring a photo for this thread but if you encounter something that concerns you it wouldn't hurt to save some screen shots and of course the option is yours if you prefer to post a photo.
A image hosting service similar to imgur.com is needed to upload the photo to and then get a link from your photo hosting site for that photo.
Next select the 'image' function found at the top of your post window in this forum (4th from the right among the tools - looks like some mountains) and paste the link into the box that appears.
*** If posting a photo please remove your full name from your user folder ***
AHH Thank you! In that case, here's my tracert:
C:\Users\ tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms 10.0.0.1
2 15 ms 11 ms 31 ms 96.120.90.113
3 12 ms 11 ms 9 ms po-302-1221-rur01.napa.ca.sfba.comcast.net [162.151.31.29]
4 22 ms 20 ms 12 ms be-201-rar01.rohnertpr.ca.sfba.comcast.net [68.85.57.249]
5 14 ms 15 ms 16 ms be-297-ar01.santaclara.ca.sfba.comcast.net [96.108.99.13]
6 17 ms 17 ms 18 ms be-33651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.90.93]
7 22 ms 13 ms 15 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14]
8 15 ms 14 ms 21 ms ix-xe-1-3-0-0.tcore1.pdi-palo-alto.as6453.net [66.198.127.13]
9 15 ms 15 ms 16 ms if-ae-2-2.tcore2.pdi-palo-alto.as6453.net [66.198.127.2]
10 15 ms 17 ms 16 ms if-ae-5-2.tcore2.sqn-san-jose.as6453.net [64.86.21.1]
11 23 ms 16 ms 23 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243.205.1]
12 22 ms 15 ms 25 ms 63.243.205.58
13 17 ms 17 ms 15 ms po110.bs-a.sech-sjc.netarch.akamai.com [209.200.184.192]
14 * * * Request timed out.
15 19 ms 18 ms 17 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
16 87 ms 90 ms 87 ms a72-52-28-178.deploy.static.akamaitechnologies.com [72.52.28.178]
17 100 ms 99 ms 94 ms 198.49.243.237
18 90 ms 90 ms 85 ms patchserver.crypticstudios.com [208.95.184.200]
I get the most rubber banding when I am doing something on the ground. Space isn't as noticeable unless there is a ton of ships present.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 9 ms 8 ms 142.254.157.25
3 120 ms 22 ms 16 ms ae60.yntwohnx02h.midwest.rr.com [24.164.117.13]
4 17 ms 14 ms 15 ms be25.pltsohae01r.midwest.rr.com [24.33.103.230]
5 21 ms 14 ms 15 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
6 26 ms 30 ms 30 ms 107.14.17.252
7 27 ms 30 ms 30 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
8 * 35 ms 23 ms 66.109.5.225
9 24 ms 23 ms 23 ms 24.27.236.145
10 * * * Request timed out.
11 23 ms 23 ms 23 ms ae11.er6.ord7.us.zip.zayo.com [64.125.28.179]
12 28 ms 29 ms 31 ms 209.133.7.66.IPYX-143212-002-ZYO.zip.zayo.com [209.133.7.66]
13 23 ms 24 ms 24 ms po110.bs-b.sech-ord.netarch.akamai.com [23.57.98.245]
14 * * * Request timed out.
15 25 ms 24 ms 24 ms ae121.access-a.sech-ord.netarch.akamai.com [23.57.98.251]
16 * * * Request timed out.
17 48 ms 45 ms 46 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
18 63 ms 53 ms 52 ms 198.49.243.237
19 45 ms 45 ms 45 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 <1 ms <1 ms <1 ms 192.168.50.1
2 12 ms 8 ms 10 ms 10.32.72.1
3 10 ms 7 ms 9 ms 100.127.75.20
4 9 ms 9 ms 9 ms 100.120.100.76
5 20 ms 19 ms 28 ms 68.1.4.252
6 20 ms 21 ms 20 ms ae20.mpr1.lax12.us.zip.zayo.com [64.125.13.97]
7 20 ms 21 ms 21 ms 128.177.68.30
8 22 ms 20 ms 19 ms po110.bs-b.sech-lax.netarch.akamai.com [23.57.96.245]
9 20 ms 21 ms 20 ms a72-52-1-157.deploy.static.akamaitechnologies.com [72.52.1.157]
10 19 ms 20 ms 21 ms ae121.access-a.sech-lax.netarch.akamai.com [23.57.96.251]
11 27 ms 28 ms 29 ms 93.191.173.105
12 91 ms 93 ms 91 ms a72-52-39-76.deploy.static.akamaitechnologies.com [72.52.39.76]
13 112 ms 99 ms 93 ms 198.49.243.237
14 94 ms 91 ms 90 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 4 ms 3 ms 3 ms SkyRouter.Home [192.168.0.1]
2 43 ms 10 ms 9 ms 97e7fe04.skybroadband.com [151.231.254.4]
3 51 ms 17 ms 15 ms be364.pr2.enlba.isp.sky.com [89.200.132.162]
4 43 ms 17 ms 18 ms 5.57.81.220
5 16 ms 79 ms 18 ms po111.bs-a.sech-lon2.netarch.akamai.com [72.52.6
0.194]
6 48 ms 16 ms 17 ms a72-52-1-181.deploy.static.akamaitechnologies.co
m [72.52.1.181]
7 18 ms 17 ms 60 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.
52.60.197]
8 114 ms 119 ms 119 ms 93.191.173.69
9 100 ms 100 ms 101 ms a209-200-171-102.deploy.static.akamaitechnologie
s.com [209.200.171.102]
10 139 ms 119 ms 119 ms 198.49.243.237
11 98 ms 98 ms 98 ms 208.95.184.200
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [10.0.0.1]
2 24 ms 23 ms 24 ms 184-102-103-254.cltn.qwest.net [184.102.103.254]
3 24 ms 23 ms 23 ms cltn-agw1.inet.qwest.net [75.160.94.1]
4 46 ms 45 ms 44 ms cer-brdr-02.inet.qwest.net [67.14.8.73]
5 45 ms 44 ms 44 ms 4.68.74.145
6 45 ms 44 ms 45 ms XO-level3-60G.Chicago2.Level3.net [4.68.127.246]
7 66 ms 71 ms 66 ms 207.88.13.47.ptr.us.xo.net [207.88.13.47]
8 67 ms 66 ms 67 ms 207.86.208.6
9 67 ms 67 ms 65 ms po110.bs-b.sech-dfw.netarch.akamai.com [23.57.102.245]
10 66 ms 67 ms 65 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
11 68 ms 67 ms 67 ms ae121.access-a.sech-dfw.netarch.akamai.com [23.57.102.251]
12 97 ms 97 ms 96 ms 93.191.173.201
13 105 ms 104 ms 103 ms a72-52-39-76.deploy.static.akamaitechnologies.com [72.52.39.76]
14 110 ms 106 ms 111 ms 198.49.243.237
15 104 ms 104 ms 104 ms patchserver.crypticstudios.com [208.95.184.200]
Thing is, unless Cryptic can persuade their ISP to discontinue using Akamai, there really isn't much they can do about it. It's occurring before the traffic hits their servers.
Thing is, unless Cryptic can persuade their ISP to discontinue using Akamai, there really isn't much they can do about it. It's occurring before the traffic hits their servers.
That's not something I believe as Cryptic are big enough to have pull and its a major problem that has a large impact on player retention. Which is why most MMORPG's make it a priority and get lag/rubberbadning like this fixed. If you look at other smaller online space games like Eve Online they wouldn't allow lag like this to go on for this long not just Eve but the other even smaller space MMO's as well.
If it truly cannot be fixed then Cryptic should be honest with us and tell us.
Folks need to consider that the internet is still largely wired. There's hundreds of thousands of miles of wire sometimes between your rig and the game servers. Any little thing that goes wrong along that route can cause lag and is almost always outside the control of Cryptic. It's also not a straight jump to the server either and several jumps occur to get from your rig to the servers and back. Having the tracerts help to narrow down the issue. If only one internet provider was having issues with lag, then it's conceivable the ISP is at fault and not Akami. The more tracerts from people with different ISPs and such that show Akami as the place where the slowdown starts, the easier it is for Cryptic when they take up the issue with Akami. Cryptic can then show the tracerts to them and say "here's a bunch of different tracerts showing your systems are treating regular traffic as a DDoS and it's a false positive." Cryptic can then potentially change services and/or get them to adjust settings to alleviate the issues. When dealing with stuff technical you have to be extremely precise. I can assure you guys the devs and Cryptic as a company don't like it either. It's not just the technical aspects, but potential contract and business aspects as well depending on what agreements Cryptic has in place and such.
"Someone once told me that time was a predator that stalked us all our lives. I rather believe that time is a companion who goes with us on the journey and reminds us to cherish every moment, because it will never come again." - Jean Luc Picard in Star Trek Generations
1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 3 ms 2 ms 192.168.0.1
3 12 ms 13 ms 13 ms 10.196.48.1
4 12 ms 25 ms 11 ms 72-31-218-234.net.bhntampa.com [72.31.218.234]
5 22 ms 43 ms 18 ms bundle-ether21.orld11-car2.bhn.net [71.44.60.122]
6 21 ms 18 ms 18 ms 72-31-220-176.net.bhntampa.com [72.31.220.176]
7 25 ms 18 ms 18 ms 72-31-188-176.net.bhntampa.com [72.31.188.176]
8 33 ms 33 ms 33 ms 216.156.105.65.ptr.us.xo.net [216.156.105.65]
9 34 ms 35 ms 31 ms 216.156.16.101.ptr.us.xo.net [216.156.16.101]
10 49 ms 48 ms 48 ms 216.156.104.22.ptr.us.xo.net [216.156.104.22]
11 47 ms 43 ms 57 ms po110.bs-a.sech-mia4.netarch.akamai.com [23.57.103.243]
12 * * * Request timed out.
13 48 ms 43 ms 46 ms ae120.access-a.sech-mia4.netarch.akamai.com [23.57.103.249]
14 * * * Request timed out.
15 57 ms 58 ms 58 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
16 72 ms 68 ms 68 ms 198.49.243.237
17 57 ms 58 ms 58 ms patchserver.crypticstudios.com [208.95.184.200]
3 11 ms 15 ms 12 ms ip1f1167fe.dynamic.kabel-deutschland.de [31.17.103.254]
4 17 ms 9 ms 13 ms 83-169-172-126-isp.superkabel.de [83.169.172.126]
5 18 ms 18 ms 18 ms ip5886c140.static.kabel-deutschland.de [88.134.193.64]
6 13 ms 18 ms 18 ms 145.254.3.88
7 23 ms 30 ms 25 ms 145.254.2.195
8 23 ms 28 ms 23 ms 145.254.2.195
9 24 ms 53 ms 24 ms akamai.prolexic.com [80.81.193.70]
10 22 ms 25 ms 22 ms po110.bs-b.sech-fra.netarch.akamai.com [72.52.48.200]
11 23 ms 21 ms 26 ms a72-52-1-191.deploy.static.akamaitechnologies.com [72.52.1.191]
12 25 ms 21 ms 21 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
13 * 320 ms 318 ms 93.191.173.63
14 118 ms 115 ms 115 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
15 119 ms 112 ms 115 ms 198.49.243.237
16 122 ms 117 ms 118 ms patchserver.crypticstudios.com [208.95.184.200]
> @pottsey5g said:
> (Quote)
> That's not something I believe as Cryptic are big enough to have pull and its a major problem that has a large impact on player retention. Which is why most MMORPG's make it a priority and get lag/rubberbadning like this fixed. If you look at other smaller online space games like Eve Online they wouldn't allow lag like this to go on for this long not just Eve but the other even smaller space MMO's as well.
>
> If it truly cannot be fixed then Cryptic should be honest with us and tell us.
Think so huh? Maybe you should look at their forums before making claims.
In the past 14 years they have had an overall good track record in finding and fixing lag problems. They used to put out blogs about it with tech details on what they did to solve problems. Although saying that Eve does seem to have gone downhill big time in recent years and its only got worse with the new owners. They did in the past have a good record and kept that record up for a good 10+years even if its not as good now it shows that it can be done.
I don't need some technical jargon to notice there's been more lag over the last few months, more than the normal laggy times at least, but luckily it has only impaired my game-play a few times. But if Cryptic did do something a few months ago from my experience it wasn't a positive in reducing lag, but it hasn't added a terrible amount neither, just annoying.
Arguing about whose "fault" it is, is not productive to identifying the problem.
Star Trek Online Volunteer Community Moderator and Resident She-Wolf
Community Moderators are Unpaid Volunteers and NOT Employees of Gearbox/Cryptic
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 * 3 ms 27 ms 192.168.1.1
2 12 ms 13 ms 11 ms 10.119.32.1
3 16 ms 18 ms 14 ms 192.168.30.89
4 32 ms 32 ms 34 ms 10.224.252.221
5 30 ms 42 ms 34 ms dls-b21-link.telia.net [62.115.48.122]
6 32 ms 31 ms 30 ms dls-b21-link.telia.net [62.115.113.85]
7 56 ms 52 ms 52 ms atl-b22-link.telia.net [80.91.246.74]
8 67 ms 72 ms 69 ms ash-bb4-link.telia.net [62.115.125.129]
9 75 ms 72 ms 66 ms ash-b1-link.telia.net [213.155.136.39]
10 66 ms 70 ms 72 ms akamai-ic-317118-ash-b1.c.telia.net [62.115.146.135]
11 69 ms 64 ms 64 ms po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
12 81 ms 74 ms 66 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
13 118 ms 167 ms 155 ms ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]
14 87 ms 80 ms 80 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
15 93 ms 89 ms 92 ms 198.49.243.237
16 73 ms 76 ms 74 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
#13 is pretty bad
Now a LTS and loving it.
Just because you spend money on this game, it does not entitle you to be a jerk if things don't go your way.
I have come to the conclusion that I have a memory like Etch-A-Sketch. I shake my head and forget everything.
Rubberbanding all over the place tonight, to the point the game is unplayable, it is like cryptic at this point doesn't want us to play STO anymore... How much more evidence do you need that akamai is the problem!
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 4 ms 3 ms 4 ms 192.168.0.1
2 9 ms 3 ms 4 ms 172.168.1.254
3 6 ms 9 ms 10 ms 10.31.168.1
4 8 ms 7 ms 7 ms 154.11.10.159
5 9 ms 9 ms 7 ms 64.125.15.12
6 38 ms 42 ms 37 ms ae7.cs2.sea1.us.zip.zayo.com [64.125.26.4]
7 38 ms 44 ms 57 ms ae3.cs2.sjc2.us.eth.zayo.com [64.125.29.40]
8 40 ms 39 ms 55 ms ae2.cs2.lax112.us.eth.zayo.com [64.125.28.197]
9 40 ms 37 ms 37 ms ae14.mpr1.lax12.us.zip.zayo.com [64.125.27.39]
10 39 ms 38 ms 38 ms 128.177.68.30
11 39 ms 39 ms 38 ms po110.bs-a.sech-lax.netarch.akamai.com [23.57.96.243]
12 * * * Request timed out.
13 43 ms 39 ms 38 ms ae120.access-a.sech-lax.netarch.akamai.com [23.57.96.249]
14 * * * Request timed out.
15 104 ms 103 ms 104 ms a209-200-186-212.deploy.static.akamaitechnologies.com [209.200.186.212]
16 116 ms 108 ms 112 ms 198.49.243.237
17 105 ms 103 ms 104 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 <1 ms <1 ms <1 ms ttrouter [192.168.1.1]
2 * * * Request timed out.
3 9 ms 9 ms 9 ms host-78-151-230-227.as13285.net [78.151.230.227]
4 9 ms 16 ms 9 ms host-78-151-230-240.as13285.net [78.151.230.240]
5 12 ms 12 ms 12 ms host-78-144-0-69.as13285.net [78.144.0.69]
6 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
7 13 ms 13 ms 13 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
8 13 ms 13 ms 13 ms a72-52-1-189.deploy.static.akamaitechnologies.com [72.52.1.189]
9 16 ms 14 ms 13 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
10 91 ms 90 ms 90 ms 93.191.173.11
11 92 ms 92 ms 92 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 106 ms 97 ms 99 ms 198.49.243.237
13 92 ms 92 ms 92 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete. This morning around 7:07am
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 host-78-151-230-227.as13285.net [78.151.230.227]
4 9 ms 9 ms 8 ms host-78-151-230-240.as13285.net [78.151.230.240]
5 11 ms 12 ms 13 ms host-78-144-0-69.as13285.net [78.144.0.69]
6 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
7 14 ms 12 ms 13 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
8 13 ms 13 ms 13 ms a72-52-1-189.deploy.static.akamaitechnologies.com [72.52.1.189]
9 13 ms 14 ms 30 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
10 253 ms 330 ms 264 ms 93.191.173.11
11 92 ms 92 ms 92 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 103 ms 97 ms 98 ms 198.49.243.237
13 92 ms 93 ms 91 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete. This afternoon 13:56
No wonder I couldn't walk from DS9 bank to Security without bouncing around like a superball
Post edited by ussvaliant#6064 on
Hello rubber banding my old friend, time to bounce around the battlezone again, where are all my bug reports going?, out of love with this game I am falling, As Cryptic fail to acknowledge a problem exists, Shakes an angry fist, And from Support all I'm hearing are the sounds of silence.
Yerp been getting some serious lag myself for a few months. Wasn't sure if it was just me as my real life peeps have quit. Rubber banding, and server drops. If they have put out help files for this I would be interested.
Comments
Open a command prompt and enter this: tracert patchserver.crypticstudios.com
You can highlight the text in the command prompt box, press CTRL + C to copy, and paste it into your post here or onto notepad. Feel free to edit out any of your own IP related info to taste.
I don't believe they're requiring a photo for this thread but if you encounter something that concerns you it wouldn't hurt to save some screen shots and of course the option is yours if you prefer to post a photo.
A image hosting service similar to imgur.com is needed to upload the photo to and then get a link from your photo hosting site for that photo.
Next select the 'image' function found at the top of your post window in this forum (4th from the right among the tools - looks like some mountains) and paste the link into the box that appears.
Edit (photos added):
Enter this: tracert patchserver.crypticstudios.com
To get your traceroute info:
*** If posting a photo please remove your full name from your user folder ***
AHH Thank you! In that case, here's my tracert:
C:\Users\ tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms 10.0.0.1
2 15 ms 11 ms 31 ms 96.120.90.113
3 12 ms 11 ms 9 ms po-302-1221-rur01.napa.ca.sfba.comcast.net [162.151.31.29]
4 22 ms 20 ms 12 ms be-201-rar01.rohnertpr.ca.sfba.comcast.net [68.85.57.249]
5 14 ms 15 ms 16 ms be-297-ar01.santaclara.ca.sfba.comcast.net [96.108.99.13]
6 17 ms 17 ms 18 ms be-33651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.90.93]
7 22 ms 13 ms 15 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14]
8 15 ms 14 ms 21 ms ix-xe-1-3-0-0.tcore1.pdi-palo-alto.as6453.net [66.198.127.13]
9 15 ms 15 ms 16 ms if-ae-2-2.tcore2.pdi-palo-alto.as6453.net [66.198.127.2]
10 15 ms 17 ms 16 ms if-ae-5-2.tcore2.sqn-san-jose.as6453.net [64.86.21.1]
11 23 ms 16 ms 23 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243.205.1]
12 22 ms 15 ms 25 ms 63.243.205.58
13 17 ms 17 ms 15 ms po110.bs-a.sech-sjc.netarch.akamai.com [209.200.184.192]
14 * * * Request timed out.
15 19 ms 18 ms 17 ms ae120.access-a.sech-sjc.netarch.akamai.com [209.200.184.197]
16 87 ms 90 ms 87 ms a72-52-28-178.deploy.static.akamaitechnologies.com [72.52.28.178]
17 100 ms 99 ms 94 ms 198.49.243.237
18 90 ms 90 ms 85 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 9 ms 8 ms 142.254.157.25
3 120 ms 22 ms 16 ms ae60.yntwohnx02h.midwest.rr.com [24.164.117.13]
4 17 ms 14 ms 15 ms be25.pltsohae01r.midwest.rr.com [24.33.103.230]
5 21 ms 14 ms 15 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
6 26 ms 30 ms 30 ms 107.14.17.252
7 27 ms 30 ms 30 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
8 * 35 ms 23 ms 66.109.5.225
9 24 ms 23 ms 23 ms 24.27.236.145
10 * * * Request timed out.
11 23 ms 23 ms 23 ms ae11.er6.ord7.us.zip.zayo.com [64.125.28.179]
12 28 ms 29 ms 31 ms 209.133.7.66.IPYX-143212-002-ZYO.zip.zayo.com [209.133.7.66]
13 23 ms 24 ms 24 ms po110.bs-b.sech-ord.netarch.akamai.com [23.57.98.245]
14 * * * Request timed out.
15 25 ms 24 ms 24 ms ae121.access-a.sech-ord.netarch.akamai.com [23.57.98.251]
16 * * * Request timed out.
17 48 ms 45 ms 46 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
18 63 ms 53 ms 52 ms 198.49.243.237
19 45 ms 45 ms 45 ms patchserver.crypticstudios.com [208.95.184.200]
=
Right click on the Windows logo on the bottom left of your desktop.
Select Command Prompt or Command Prompt (Admin) from the menu.
Sometimes right clicking doesn't work for me either, but ctrl-v does.
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.50.1
2 12 ms 8 ms 10 ms 10.32.72.1
3 10 ms 7 ms 9 ms 100.127.75.20
4 9 ms 9 ms 9 ms 100.120.100.76
5 20 ms 19 ms 28 ms 68.1.4.252
6 20 ms 21 ms 20 ms ae20.mpr1.lax12.us.zip.zayo.com [64.125.13.97]
7 20 ms 21 ms 21 ms 128.177.68.30
8 22 ms 20 ms 19 ms po110.bs-b.sech-lax.netarch.akamai.com [23.57.96.245]
9 20 ms 21 ms 20 ms a72-52-1-157.deploy.static.akamaitechnologies.com [72.52.1.157]
10 19 ms 20 ms 21 ms ae121.access-a.sech-lax.netarch.akamai.com [23.57.96.251]
11 27 ms 28 ms 29 ms 93.191.173.105
12 91 ms 93 ms 91 ms a72-52-39-76.deploy.static.akamaitechnologies.com [72.52.39.76]
13 112 ms 99 ms 93 ms 198.49.243.237
14 94 ms 91 ms 90 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
Ugg.. those last few don't look so good.
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms SkyRouter.Home [192.168.0.1]
2 43 ms 10 ms 9 ms 97e7fe04.skybroadband.com [151.231.254.4]
3 51 ms 17 ms 15 ms be364.pr2.enlba.isp.sky.com [89.200.132.162]
4 43 ms 17 ms 18 ms 5.57.81.220
5 16 ms 79 ms 18 ms po111.bs-a.sech-lon2.netarch.akamai.com [72.52.6
0.194]
6 48 ms 16 ms 17 ms a72-52-1-181.deploy.static.akamaitechnologies.co
m [72.52.1.181]
7 18 ms 17 ms 60 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.
52.60.197]
8 114 ms 119 ms 119 ms 93.191.173.69
9 100 ms 100 ms 101 ms a209-200-171-102.deploy.static.akamaitechnologie
s.com [209.200.171.102]
10 139 ms 119 ms 119 ms 198.49.243.237
11 98 ms 98 ms 98 ms 208.95.184.200
Trace complete.
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [10.0.0.1]
2 24 ms 23 ms 24 ms 184-102-103-254.cltn.qwest.net [184.102.103.254]
3 24 ms 23 ms 23 ms cltn-agw1.inet.qwest.net [75.160.94.1]
4 46 ms 45 ms 44 ms cer-brdr-02.inet.qwest.net [67.14.8.73]
5 45 ms 44 ms 44 ms 4.68.74.145
6 45 ms 44 ms 45 ms XO-level3-60G.Chicago2.Level3.net [4.68.127.246]
7 66 ms 71 ms 66 ms 207.88.13.47.ptr.us.xo.net [207.88.13.47]
8 67 ms 66 ms 67 ms 207.86.208.6
9 67 ms 67 ms 65 ms po110.bs-b.sech-dfw.netarch.akamai.com [23.57.102.245]
10 66 ms 67 ms 65 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
11 68 ms 67 ms 67 ms ae121.access-a.sech-dfw.netarch.akamai.com [23.57.102.251]
12 97 ms 97 ms 96 ms 93.191.173.201
13 105 ms 104 ms 103 ms a72-52-39-76.deploy.static.akamaitechnologies.com [72.52.39.76]
14 110 ms 106 ms 111 ms 198.49.243.237
15 104 ms 104 ms 104 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
If it truly cannot be fixed then Cryptic should be honest with us and tell us.
Star Trek Online volunteer Community Moderator
2 3 ms 3 ms 2 ms 192.168.0.1
3 12 ms 13 ms 13 ms 10.196.48.1
4 12 ms 25 ms 11 ms 72-31-218-234.net.bhntampa.com [72.31.218.234]
5 22 ms 43 ms 18 ms bundle-ether21.orld11-car2.bhn.net [71.44.60.122]
6 21 ms 18 ms 18 ms 72-31-220-176.net.bhntampa.com [72.31.220.176]
7 25 ms 18 ms 18 ms 72-31-188-176.net.bhntampa.com [72.31.188.176]
8 33 ms 33 ms 33 ms 216.156.105.65.ptr.us.xo.net [216.156.105.65]
9 34 ms 35 ms 31 ms 216.156.16.101.ptr.us.xo.net [216.156.16.101]
10 49 ms 48 ms 48 ms 216.156.104.22.ptr.us.xo.net [216.156.104.22]
11 47 ms 43 ms 57 ms po110.bs-a.sech-mia4.netarch.akamai.com [23.57.103.243]
12 * * * Request timed out.
13 48 ms 43 ms 46 ms ae120.access-a.sech-mia4.netarch.akamai.com [23.57.103.249]
14 * * * Request timed out.
15 57 ms 58 ms 58 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
16 72 ms 68 ms 68 ms 198.49.243.237
17 57 ms 58 ms 58 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
3 11 ms 15 ms 12 ms ip1f1167fe.dynamic.kabel-deutschland.de [31.17.103.254]
4 17 ms 9 ms 13 ms 83-169-172-126-isp.superkabel.de [83.169.172.126]
5 18 ms 18 ms 18 ms ip5886c140.static.kabel-deutschland.de [88.134.193.64]
6 13 ms 18 ms 18 ms 145.254.3.88
7 23 ms 30 ms 25 ms 145.254.2.195
8 23 ms 28 ms 23 ms 145.254.2.195
9 24 ms 53 ms 24 ms akamai.prolexic.com [80.81.193.70]
10 22 ms 25 ms 22 ms po110.bs-b.sech-fra.netarch.akamai.com [72.52.48.200]
11 23 ms 21 ms 26 ms a72-52-1-191.deploy.static.akamaitechnologies.com [72.52.1.191]
12 25 ms 21 ms 21 ms ae121.access-a.sech-fra.netarch.akamai.com [72.52.48.205]
13 * 320 ms 318 ms 93.191.173.63
14 118 ms 115 ms 115 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
15 119 ms 112 ms 115 ms 198.49.243.237
16 122 ms 117 ms 118 ms patchserver.crypticstudios.com [208.95.184.200]
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Moderation Problems/Issues? Please contact the Community Manager
Terms of Service / Community Rules and Policies / FCT
Facebook / Twitter / Twitch
It's like a fwinger pointing to the mwoon.
over a maximum of 30 hops:
1 * 3 ms 27 ms 192.168.1.1
2 12 ms 13 ms 11 ms 10.119.32.1
3 16 ms 18 ms 14 ms 192.168.30.89
4 32 ms 32 ms 34 ms 10.224.252.221
5 30 ms 42 ms 34 ms dls-b21-link.telia.net [62.115.48.122]
6 32 ms 31 ms 30 ms dls-b21-link.telia.net [62.115.113.85]
7 56 ms 52 ms 52 ms atl-b22-link.telia.net [80.91.246.74]
8 67 ms 72 ms 69 ms ash-bb4-link.telia.net [62.115.125.129]
9 75 ms 72 ms 66 ms ash-b1-link.telia.net [213.155.136.39]
10 66 ms 70 ms 72 ms akamai-ic-317118-ash-b1.c.telia.net [62.115.146.135]
11 69 ms 64 ms 64 ms po110.bs-a.sech-iad.netarch.akamai.com [209.200.144.192]
12 81 ms 74 ms 66 ms a72-52-1-155.deploy.static.akamaitechnologies.com [72.52.1.155]
13 118 ms 167 ms 155 ms ae120.access-a.sech-iad.netarch.akamai.com [209.200.144.197]
14 87 ms 80 ms 80 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
15 93 ms 89 ms 92 ms 198.49.243.237
16 73 ms 76 ms 74 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
#13 is pretty bad
over a maximum of 30 hops:
1 4 ms 3 ms 4 ms 192.168.0.1
2 9 ms 3 ms 4 ms 172.168.1.254
3 6 ms 9 ms 10 ms 10.31.168.1
4 8 ms 7 ms 7 ms 154.11.10.159
5 9 ms 9 ms 7 ms 64.125.15.12
6 38 ms 42 ms 37 ms ae7.cs2.sea1.us.zip.zayo.com [64.125.26.4]
7 38 ms 44 ms 57 ms ae3.cs2.sjc2.us.eth.zayo.com [64.125.29.40]
8 40 ms 39 ms 55 ms ae2.cs2.lax112.us.eth.zayo.com [64.125.28.197]
9 40 ms 37 ms 37 ms ae14.mpr1.lax12.us.zip.zayo.com [64.125.27.39]
10 39 ms 38 ms 38 ms 128.177.68.30
11 39 ms 39 ms 38 ms po110.bs-a.sech-lax.netarch.akamai.com [23.57.96.243]
12 * * * Request timed out.
13 43 ms 39 ms 38 ms ae120.access-a.sech-lax.netarch.akamai.com [23.57.96.249]
14 * * * Request timed out.
15 104 ms 103 ms 104 ms a209-200-186-212.deploy.static.akamaitechnologies.com [209.200.186.212]
16 116 ms 108 ms 112 ms 198.49.243.237
17 105 ms 103 ms 104 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
#postyourtracert
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 host-78-151-230-227.as13285.net [78.151.230.227]
4 9 ms 16 ms 9 ms host-78-151-230-240.as13285.net [78.151.230.240]
5 12 ms 12 ms 12 ms host-78-144-0-69.as13285.net [78.144.0.69]
6 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
7 13 ms 13 ms 13 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
8 13 ms 13 ms 13 ms a72-52-1-189.deploy.static.akamaitechnologies.com [72.52.1.189]
9 16 ms 14 ms 13 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
10 91 ms 90 ms 90 ms 93.191.173.11
11 92 ms 92 ms 92 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 106 ms 97 ms 99 ms 198.49.243.237
13 92 ms 92 ms 92 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete. This morning around 7:07am
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 host-78-151-230-227.as13285.net [78.151.230.227]
4 9 ms 9 ms 8 ms host-78-151-230-240.as13285.net [78.151.230.240]
5 11 ms 12 ms 13 ms host-78-144-0-69.as13285.net [78.144.0.69]
6 13 ms 13 ms 13 ms akamai.prolexic.com [195.66.224.31]
7 14 ms 12 ms 13 ms po110.bs-a.sech-lon2.netarch.akamai.com [72.52.60.192]
8 13 ms 13 ms 13 ms a72-52-1-189.deploy.static.akamaitechnologies.com [72.52.1.189]
9 13 ms 14 ms 30 ms ae120.access-a.sech-lon2.netarch.akamai.com [72.52.60.197]
10 253 ms 330 ms 264 ms 93.191.173.11
11 92 ms 92 ms 92 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 103 ms 97 ms 98 ms 198.49.243.237
13 92 ms 93 ms 91 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete. This afternoon 13:56
No wonder I couldn't walk from DS9 bank to Security without bouncing around like a superball
Hello rubber banding my old friend, time to bounce around the battlezone again, where are all my bug reports going?, out of love with this game I am falling, As Cryptic fail to acknowledge a problem exists, Shakes an angry fist, And from Support all I'm hearing are the sounds of silence.
Nerco above. But considering the subject matter would something different occur?