True, but those numbers aren't completely problematic there, except in hop 14. I'll point out, though, that I'd run several traces over a period of time when I posted that commentary and got wildly variable results...but yes, they were in that zone.
I have to admit that I have never run the tracert until I started having issues with latency so I cannot be sure but it seems odd that you jump from 35ms to 72ms and peak at 166ms or so before it reaches the end. It would seem there is an issue there.
I have not had any serious lag issues in a year of playing until about a week ago. Located in Australia...
Posting my tracert. Any help or advice would be great. thanks
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms (null).iiNet [10.1.1.1]
2 19 ms 17 ms 17 ms nexthop.vic.iinet.net.au [203.215.7.251]
3 18 ms 18 ms 17 ms te7-2.mel-pipe-bdr2.iinet.net.au [203.215.6.12]
4 30 ms 29 ms 30 ms xe-2-0-2.syd-mas-core1.iinet.net.au [203.215.20.117]
5 29 ms 28 ms 29 ms 32433.chep02.cu.telstraglobal.net [134.159.130.105]
6 29 ms 30 ms 30 ms i-0-6-1-0.sydp-core01.bi.telstraglobal.net [202.84.223.9]
7 173 ms 173 ms 173 ms i-0-6-0-0.1wlt-core01.bx.telstraglobal.net [202.84.249.93]
8 220 ms 220 ms 220 ms i-3-4.eqla01.bi.telstraglobal.net [202.84.251.154]
9 220 ms 220 ms 221 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159.63.198]
10 222 ms 221 ms 218 ms te0-3-0-5.mpd21.lax01.atlas.cogentco.com [154.54.44.137]
11 256 ms 256 ms 256 ms te0-3-0-6.mpd21.iah01.atlas.cogentco.com [154.54.0.230]
12 269 ms 270 ms 270 ms te0-2-0-7.mpd21.atl01.atlas.cogentco.com [154.54.2.221]
13 282 ms 282 ms 281 ms te0-0-0-3.mpd21.dca01.atlas.cogentco.com [154.54.28.205]
14 288 ms 288 ms 288 ms te0-0-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.40.46]
15 256 ms 258 ms 256 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54.44.10]
16 255 ms 255 ms 257 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
17 260 ms 255 ms 265 ms 38.111.40.114
18 257 ms 256 ms 256 ms patchserver.crypticstudios.com [208.95.185.41]
I only downloaded the game a few days ago, and while the gameplay is outstanding (definitely one of my favourite MMOs of all time), the lag and constant disconnects I'm experiencing are extremely disruptive. It seems that I'm being disconnected every 20-30 minutes.
Anyhow, I'm located in Canada (about an hour's drive from New York state) and don't experience similar problems with other online games. I've posted my info below - note that I've added some punctuation to the traceroute data to make it more coherent, but the asterisks were part of the original results (not sure what they mean):
TRACEROUTE
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1: * - <1 ms - <1 ms - monreseau.home [192.168.2.1]
2: 5 ms - 4 ms - 4 ms - bas1-ottawa09_lo0_SYMP.net.bell.ca [64.230.200.132]
3: 4 ms - 4 ms - 6 ms - dis32-ottawa23_4-2-0_100.net.bell.ca [64.230.57.60]
4: * - 17 ms - 20 ms - bxX5-newyork83_POS9-0-0.net.bell.ca [64.230.187.42]
5: 15 ms - * - 15 ms - te0-2-0-0.ccr21.jfk05.atlas.cogentco.com [154.54.10.205]
6: 15 ms - 15 ms - 15 ms - te0-3-0-5.mpd21.jfk02.atlas.cogentco.com [154.54.26.61]
7: 23 ms - 23 ms - * - te0-0-0-1.ccr21.bos01.atlas.cogentco.com [154.54.6.1]
8: * - 21 ms - 20 ms - te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
9: 29 ms - 21 ms - 31 ms - 38.111.40.114
10: 23 ms - 22 ms - * - 208.95.185.41
11: 20 ms - 20 ms - 21 ms - 208.95.185.41
Asterisks in your trace results mean that a packet of data was not received at that destination. Each "hop" (numbered step on your trace) is sent three packets of data, and the time it takes to receive each one is measured.
Are you connecting via a wireless connection to your router? There may be some packet loss occurring. Some other games won't notice that loss, but STO (being that it's a far more network intensive game than most) will.
Your nettest results are fine, in most cases well above the standard results. Just make sure when you're posting nettest results not to post your local IP. (you can always block that out before reposting results)
In regards to the post above that one....
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms (null).iiNet [10.1.1.1]
2 19 ms 17 ms 17 ms nexthop.vic.iinet.net.au [203.215.7.251]
3 18 ms 18 ms 17 ms te7-2.mel-pipe-bdr2.iinet.net.au [203.215.6.12]
4 30 ms 29 ms 30 ms xe-2-0-2.syd-mas-core1.iinet.net.au [203.215.20.117]
5 29 ms 28 ms 29 ms 32433.chep02.cu.telstraglobal.net [134.159.130.105]
6 29 ms 30 ms 30 ms i-0-6-1-0.sydp-core01.bi.telstraglobal.net [202.84.223.9]
7 173 ms 173 ms 173 ms i-0-6-0-0.1wlt-core01.bx.telstraglobal.net [202.84.249.93]
8 220 ms 220 ms 220 ms i-3-4.eqla01.bi.telstraglobal.net [202.84.251.154]
9 220 ms 220 ms 221 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159.63.198]
10 222 ms 221 ms 218 ms te0-3-0-5.mpd21.lax01.atlas.cogentco.com [154.54.44.137]
11 256 ms 256 ms 256 ms te0-3-0-6.mpd21.iah01.atlas.cogentco.com [154.54.0.230]
12 269 ms 270 ms 270 ms te0-2-0-7.mpd21.atl01.atlas.cogentco.com [154.54.2.221]
13 282 ms 282 ms 281 ms te0-0-0-3.mpd21.dca01.atlas.cogentco.com [154.54.28.205]
14 288 ms 288 ms 288 ms te0-0-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.40.46]
15 256 ms 258 ms 256 ms te0-2-0-1.ccr21.bos01.atlas.cogentco.com [154.54.44.10]
16 255 ms 255 ms 257 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
17 260 ms 255 ms 265 ms 38.111.40.114
18 257 ms 256 ms 256 ms patchserver.crypticstudios.com [208.95.185.41]
Trace complete.
Holy lag monster, Batman....
Everything from hop 7 on is beyond problematic (over 150ms). Have you attempted connecting via either one of the proxies provided to see if that clears up a little? Is this consistently happening or randomly occuring? It may help to run several traces over a period of time and see how it patterns out.
Thanks for the feedback. Deleted my local IP from that post, I appreciate the heads-up.
I'm not connecting via a wireless router, as the big heap of cables under my desk will testify . With that in mind, is there a way to determine whether the packet loss is occurring due to a problem at my end, at Cryptic's end, or somewhere in transit? If there's something I can do (or, alternatively, if there's something Cryptic/my ISP can do), I'd like to take whatever steps I can to rectify the problem. Right now I'm avoiding co-op and PvP because of rubberbanding and disconnect issues, which is kind of a shame.
Anyhow, I really appreciate the help! Thanks again!
Thanks for the feedback. Deleted my local IP from that post, I appreciate the heads-up.
I'm not connecting via a wireless router, as the big heap of cables under my desk will testify . With that in mind, is there a way to determine whether the packet loss is occurring due to a problem at my end, at Cryptic's end, or somewhere in transit? If there's something I can do (or, alternatively, if there's something Cryptic/my ISP can do), I'd like to take whatever steps I can to rectify the problem. Right now I'm avoiding co-op and PvP because of rubberbanding and disconnect issues, which is kind of a shame.
Anyhow, I really appreciate the help! Thanks again!
I would suggest running another trace later to confirm the results you're getting from the one you've posted. Lag is a tricky devil to pin down, and what one trace reveals another may not.
Probably going to need more help than I'm qualified to provide, though. Submitting a ticket will likely yield some more answers...although be forewarned, tickets are usually dealt with according to set procedures, which means you may or may not be provided with a copy/paste standardized answer. Make sure when you're submitting your ticket that you list any and all things you have done to date to help solve this issue, as well as a copy of your traceroute/nettest results. And don't be afraid to follow up if your first response doesn't help your issue.
I live in Australia and I was playing the game and I started to get some serious problems to like when I would start the game etc, I would get horrible rubber band effect, when I would start the game the UI would take awhile to load, playing the game was getting hard, I contacted my ISP and this one guy took me through my modem settings and changed alot of things and one of them was the MTU setting, and a few other things like he gave me my DNS settings and said to Uncheck the Let my ISP manage my DNS server. He also changed my protocals from PPPoE to PPPoA. The ISP I am with also has a speed connection manager that lets you chose between throttling the connection to "Thrill Seeker (max speed)" or various others like "Safe","Controlled", "Standard", "Thrill Seeker", and then the gamer setting that allows for better response. Find out if your ISP has this because this helped alot as well. Ever since I made these changes that ISP gave me the gameplay has improved drastically and even my flatmate said that when he plays WOW the response he gets is much improved.
I hope this helps. These settings for MTU etc should be found in your modem.
Also he told me to alter the QoS settings. There fairly simple to do once you know how. The only thing about this kinda thing is every ISP is different but some very simple changes can make a big difference. My Modem had my MTU settings set to 1400 which he said were way to low and so I changed them to 1454. Its kinda cool when the technical person on the other end of the phone isnt just some guy, but actually knows what he is talking about because no other support guy has ever told me to do some of the things he told me to do. Sometimes you get good support advice and sometimes you dont.
my games now un-playable it disconnects every 1-2 mins the rubber banding is something thats only just started a week ago and now my shuttle name shows instead of my ship name which is new. i got a question to when you first launch the game and get the first window asking for you to sign in is'nt there supposed to be a box with a choice of cryptic or p?f?ct world??? heres my test results
tracing results
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 44 ms 7 ms cpc14-sotn9-2-0-gw.15-1.cable.virginmedia.com [86.3.216.1]
2 6 ms 6 ms 9 ms sotn-core-1b-ae4-3865.network.virginmedia.net [80.4.225.233]
3 10 ms 11 ms 12 ms glfd-bb-1b-ae3-0.network.virginmedia.net [212.43.163.153]
4 12 ms 14 ms 11 ms nrth-bb-1a-as5-0.network.virginmedia.net [212.43.163.182]
5 14 ms 12 ms 14 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
6 27 ms 28 ms 27 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
7 30 ms 28 ms 28 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.117.14.133]
8 27 ms 30 ms 29 ms te0-2-0-2.mpd22.ams03.atlas.cogentco.com [130.117.3.85]
9 35 ms 34 ms 33 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54.37.110]
10 101 ms 103 ms 100 ms te0-5-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.217]
11 224 ms 109 ms 445 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 108 ms 105 ms 107 ms 38.111.40.114
13 102 ms 99 ms 99 ms 208.95.185.41
ive tryed everything on this forum before i start getting linked to other posts and yes reported it to a GM only to get fobbed off to to this forum i was gonna buy a lifetime account but if this is the way cryptic $tudio$ and p?rf?ct world roll i think i'll pass.
1 8 ms 7 ms 7 ms 10.82.0.1
2 15 ms 14 ms 15 ms network-184-059-242-015.midohio.rr.com [184.59.2
42.15]
3 17 ms 15 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
4 31 ms 31 ms 30 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
5 34 ms 117 ms 23 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
6 34 ms 35 ms 37 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54
.11.145]
7 36 ms 36 ms 38 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54
.5.1]
8 47 ms 44 ms 43 ms te0-0-0-2.ccr22.bos01.atlas.cogentco.com [154.54
.43.202]
9 48 ms 48 ms 46 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 53 ms 53 ms 53 ms 38.111.40.114
11 45 ms * 45 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ************
2 29 ms 13 ms 21 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [67.242.192.1]
3 12 ms 11 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
4 13 ms 12 ms 12 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
5 23 ms 24 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 22 ms 23 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 19 ms 22 ms 19 ms 107.14.19.147
8 21 ms 21 ms 22 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54.13.185]
9 20 ms 21 ms 22 ms te0-1-0-5.mpd21.jfk02.atlas.cogentco.com [154.54.3.97]
10 26 ms 27 ms 25 ms te0-3-0-2.ccr21.bos01.atlas.cogentco.com [154.54.44.14]
11 25 ms 28 ms 28 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 26 ms 35 ms 35 ms 38.111.40.114
13 27 ms 26 ms 27 ms 208.95.185.41
Trace complete.
The above seems better than my first time around back in post #11 (July 2011).
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
1 8 ms 7 ms 7 ms 10.82.0.1
2 15 ms 14 ms 15 ms network-184-059-242-015.midohio.rr.com [184.59.2
42.15]
3 17 ms 15 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
4 31 ms 31 ms 30 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
5 34 ms 117 ms 23 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
6 34 ms 35 ms 37 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54
.11.145]
7 36 ms 36 ms 38 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54
.5.1]
8 47 ms 44 ms 43 ms te0-0-0-2.ccr22.bos01.atlas.cogentco.com [154.54
.43.202]
9 48 ms 48 ms 46 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 53 ms 53 ms 53 ms 38.111.40.114
11 45 ms * 45 ms 208.95.185.41
It was started by a fellow player who was kind enough to try and give some aid to folks having problems.
If you read the first couple of posts, you might get a bit of self-help there.
But don't expect anybody from Cryptic to chime in here.
Your Trace data seems to indicate a fairly good communication between your 'puter and the STO Server...,
But your Bandwidth seems like TRIBBLE... SEND 161 KB/sec .... RECEIVE 3 KB/sec.
I'm no expert, but I'd look into that.
STO Member since February 2009. I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born! Forever a STO Veteran-Minion
It was started by a fellow player who was kind enough to try and give some aid to folks having problems.
If you read the first couple of posts, you might get a bit of self-help there.
But don't expect anybody from Cryptic to chime in here.
Your Trace data seems to indicate a fairly good communication between your 'puter and the STO Server...,
But your Bandwidth seems like TRIBBLE... SEND 161 KB/sec .... RECEIVE 3 KB/sec.
I'm no expert, but I'd look into that.
I thought this was a Cryptic thing. But either way...My bandwidth is is suposed to be a lot higher. I was on the phone againw ith my ISP. I told them I think it is a line problem. And for the heck of it. I am having the modem switch out.
But I am going to a live issue. Being thats what seems to happen alot.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.3
2 2 ms 1 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 12 ms 7 ms 8 ms ten0-0-0-6.orld10-ser1.bhn.net [72.31.194.50]
5 19 ms 12 ms 21 ms ten0-13-0-13.orld71-car1.bhn.net [72.31.195.172]
6 11 ms 15 ms 11 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
7 18 ms 19 ms 19 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
8 20 ms 22 ms 23 ms 107.14.19.38
9 16 ms 16 ms 18 ms 107.14.19.13
10 20 ms 18 ms * te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
11 20 ms 23 ms 21 ms te0-0-0-1.mpd22.atl01.atlas.cogentco.com [154.54
.3.145]
12 33 ms 32 ms 33 ms te0-2-0-3.mpd22.dca01.atlas.cogentco.com [154.54
.2.102]
13 39 ms 40 ms 40 ms te0-7-0-5.mpd22.jfk02.atlas.cogentco.com [154.54
.41.30]
14 45 ms 45 ms 52 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
15 49 ms 44 ms 43 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 * 46 ms 52 ms 38.111.40.114
17 46 ms 45 ms 44 ms 208.95.185.41
Trace complete.
And the Nettest, which I could not copy and paste for some reason, hovered around 50 kB/sec.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.3
2 2 ms 1 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 12 ms 7 ms 8 ms ten0-0-0-6.orld10-ser1.bhn.net [72.31.194.50]
5 19 ms 12 ms 21 ms ten0-13-0-13.orld71-car1.bhn.net [72.31.195.172]
6 11 ms 15 ms 11 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
7 18 ms 19 ms 19 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
8 20 ms 22 ms 23 ms 107.14.19.38
9 16 ms 16 ms 18 ms 107.14.19.13
10 20 ms 18 ms * te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
11 20 ms 23 ms 21 ms te0-0-0-1.mpd22.atl01.atlas.cogentco.com [154.54
.3.145]
12 33 ms 32 ms 33 ms te0-2-0-3.mpd22.dca01.atlas.cogentco.com [154.54
.2.102]
13 39 ms 40 ms 40 ms te0-7-0-5.mpd22.jfk02.atlas.cogentco.com [154.54
.41.30]
14 45 ms 45 ms 52 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
15 49 ms 44 ms 43 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 * 46 ms 52 ms 38.111.40.114
17 46 ms 45 ms 44 ms 208.95.185.41
Trace complete.
And the Nettest, which I could not copy and paste for some reason, hovered around 50 kB/sec.
You're getting timeouts and partial misses early in your trace, which likely means an issue on your ISP's network.
Also, 50 KB/s....first and third column, or middle? If it's first and third, that's kinda atrocious...
Traceroute from the highlighted points is high enough to be problematic, starting from just off the Verizon network. Your nettest results are abnormally low, too.
Not sure if there's anything your ISP would be able to do about the latency portion, but perhaps they can help you improve your connection to closer to normal levels for your nettest (you're wanting to shoot for at least 200 KB/s for first and third column values and 20 KB/s for the second).
"The world ain't all sunshine and rainbows. It's a very mean and nasty place and I don't care how tough you are it will beat you to your knees and keep you there permanently if you let it. You, me, or nobody is gonna hit as hard as life. But it ain't about how hard ya hit. It's about how hard you can get hit and keep moving forward." - Rocky Balboa (2006)
I am a returning STO vet. I did enjoy game when game originally launched but i didn't play for long and was hoping to see what's changed. I re-subbed and decided to give it another go, however this last week since i been playing again it's been unbearable which is on edge of completely unplayable in this state. I literally get server not responding messages anywhere from every few seconds to every few minutes during missions. I like to play my missions on advanced difficulty but it's starting to prove pointless when you cannot play tactfully and overtime you come out of a long server not responding downtime your nearly destroyed and in bad tactical position .
My ISP uses Roadrunner lightning, i purchase my internet through Brighthouse CFL. In my 20 years of online gaming this has without a doubt been the best and most reliable internet service provider i ever had, i never get disconnects or lag spikes in games, and if anything, only time i ever have connection issues is when my power goes out for extended periods of time (i have decent size battery backup!). I also am Cisco qualified and already knew how to do ping and tracert tests prior to coming to these forums. I seriously doubt it's any nodes near my end and suspect it's problem with Perfect World's servers or local traffic near them.
Here is my recording following this threads instructions:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 13 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 6 ms 7 ms 16 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 18 ms 19 ms 17 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 21 ms 15 ms 15 ms 107.14.19.38
7 18 ms 16 ms 17 ms 107.14.19.13
8 66 ms 203 ms 204 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 18 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 30 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 40 ms 41 ms 41 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54]
13 41 ms 41 ms 41 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 47 ms 54 ms 53 ms 38.111.40.114
15 43 ms 38 ms 39 ms 208.95.185.41
EDIT: Those tracerts seem to give me sparatic high pings on some of the cogentco.com hops. Here is another one showing a 200+ ping on one of thier other hops.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 9 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 14 ms 7 ms 7 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 27 ms 17 ms 18 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 20 ms 15 ms 15 ms 107.14.19.38
7 19 ms 17 ms 17 ms 107.14.19.13
8 18 ms 20 ms 16 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 17 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 29 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 41 ms 41 ms 42 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54]
13 61 ms 215 ms 207 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 41 ms 53 ms 54 ms 38.111.40.114
15 39 ms 42 ms 38 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 13 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 6 ms 7 ms 16 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 18 ms 19 ms 17 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 21 ms 15 ms 15 ms 107.14.19.38
7 18 ms 16 ms 17 ms 107.14.19.13 8 66 ms 203 ms 204 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 18 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 30 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 40 ms 41 ms 41 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54]
13 41 ms 41 ms 41 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 47 ms 54 ms 53 ms 38.111.40.114
15 43 ms 38 ms 39 ms 208.95.185.41
Trace complete.
...
Now this results appears to show a issue with Road Runner and the Cogent Communications backbone gateway. (Possible load related issue) You might want to contact Road Runner and see if their aware of this...
EDIT: Those tracerts seem to give me sparatic high pings on some of the cogentco.com hops. Here is another one showing a 200+ ping on one of thier other hops.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 9 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 14 ms 7 ms 7 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 27 ms 17 ms 18 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 20 ms 15 ms 15 ms 107.14.19.38
7 19 ms 17 ms 17 ms 107.14.19.13
8 18 ms 20 ms 16 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 17 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 29 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 41 ms 41 ms 42 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54] 13 61 ms 215 ms 207 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 41 ms 53 ms 54 ms 38.111.40.114
15 39 ms 42 ms 38 ms 208.95.185.41
Trace complete.
The second Trace Route appears to be a ongoing issue with the Cogent Communications Boston hub that Cryptic/PWE has been struggling with, that is being covered in this PWE Tech Support thread... http://techsupport.perfectworld.com/showthread.php?t=4181
Have you tried using the US Proxy option setting in the Launcher, as sometimes, the different Internet path from the Proxy can bypass the congestion issue...
You know, i was thinking i had to input a custom proxy in there and couldn't figure out why no one was posting ones they were using, then i realized it's actually built into the client. I tried it earlier today and i had no lag, but i was only on for about 30 minutes, however it was fastest loading and longest i gone without an issue, so crossing my fingers that using that US proxy option will continue working for me.
Until today i had lags only sometimes, now its unplayable. As soon as i start to fight it disconnects, using eu proxy. Without proxy its even worse, long "server not responding" times and such. And no one can tell me its an isp error, i have been playing various online games so my tought about his is they are trying to avoid facing this issue.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 22 ms 21 ms 29 ms cpe-72-135-0-1.kc.res.rr.com [72.135.0.1]
2 11 ms 15 ms 9 ms 65.28.16.198
3 53 ms 47 ms 56 ms tge0-8-0-2.ksczksmp-ccr1.kc.rr.com [98.156.42.14
4]
4 56 ms 55 ms 54 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 51 ms 55 ms 56 ms 107.14.17.138
6 308 ms 39 ms 39 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
7 39 ms 36 ms 38 ms 107.14.17.234
8 90 ms 87 ms 87 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 91 ms 83 ms 123 ms 154.54.88.78
10 98 ms 95 ms 98 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54
.3.18]
11 98 ms 117 ms 111 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
12 * 119 ms 101 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.43.178]
13 101 ms 101 ms 97 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 117 ms 108 ms 107 ms 38.111.40.114
15 103 ms 105 ms 105 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
I couldn't run the nettest.exe, each time I tried I got a "timed out" message. I don't know how to get past that.
Until today i had lags only sometimes, now its unplayable. As soon as i start to fight it disconnects, using eu proxy. Without proxy its even worse, long "server not responding" times and such. And no one can tell me its an isp error, i have been playing various online games so my tought about his is they are trying to avoid facing this issue.
Its actually sad, i really enjoyed playing here.
We can if you haven't bothered to perform the tests in this sticky. "I can play other online games" is completely irrelevant to the issue at hand. Other games follow a completely different pathing to their servers, ergo, what's affecting the route to the STO servers won't affect another game unless they use identical segments of a given route.
So run the tests, post your results, and then perhaps we can help you find your problem.
I couldn't run the nettest.exe, each time I tried I got a "timed out" message. I don't know how to get past that.
That's a little telling in itself. Have you made any changes to your PC or your firewall? You may have to allow a firewall exception for nettest.exe in order for it to run properly.
Your traceroute is fine, up until the final hops. Those readings are a little bit on the high side there. Unfortunately, it's persistent with the segment of the route controlled by Cogent Communications, with whom PWE has been working on this issue for several months now. However, it's not as easy as "well, duh, just get another ISP!!" considering that PWE would require a provider capable of handling immense amounts of bandwidth--which you can't really get from your garden-variety ISP.
I have been disconnected from the server 23 times over the past 3 days. I do not know what this means but hopefully I can get it figured out.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 22 ms 21 ms 29 ms cpe-72-135-0-1.kc.res.rr.com [72.135.0.1]
2 11 ms 15 ms 9 ms 65.28.16.198
3 53 ms 47 ms 56 ms tge0-8-0-2.ksczksmp-ccr1.kc.rr.com [98.156.42.14
4]
4 56 ms 55 ms 54 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 51 ms 55 ms 56 ms 107.14.17.138 6 308 ms 39 ms 39 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
7 39 ms 36 ms 38 ms 107.14.17.234
8 90 ms 87 ms 87 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 91 ms 83 ms 123 ms 154.54.88.78
10 98 ms 95 ms 98 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54
.3.18]
11 98 ms 117 ms 111 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
12 * 119 ms 101 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.43.178]
13 101 ms 101 ms 97 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 117 ms 108 ms 107 ms 38.111.40.114
15 103 ms 105 ms 105 ms 208.95.185.41
Trace complete.
....
This appears to be a bad congestion problem between Road Runner and the Cogent Communication backbone.... A issue that only your ISP (presumably Road Runner...) can address...
Besides complaining to your ISP, have you tried using the US Proxy option in the Launcher, as sometimes, this can bypass the localized network congestion...
"I can play other games" IS the relevant thing regarding this. Anyone thinks it makes any customer happier to hear about "completely different pathing system"? That is the irrelevant stuff here i think. We can not do anything about those pathing systems, right? All we see its unplayable. I have done tracerouting, and nettest, why posting it, since its the same as with others, going trough some atlas servers signal gets high ms times. Can anyone do anything about that?
Comments
I have to admit that I have never run the tracert until I started having issues with latency so I cannot be sure but it seems odd that you jump from 35ms to 72ms and peak at 166ms or so before it reaches the end. It would seem there is an issue there.
Brian
I have not had any serious lag issues in a year of playing until about a week ago. Located in Australia...
Posting my tracert. Any help or advice would be great. thanks
Anyhow, I'm located in Canada (about an hour's drive from New York state) and don't experience similar problems with other online games. I've posted my info below - note that I've added some punctuation to the traceroute data to make it more coherent, but the asterisks were part of the original results (not sure what they mean):
TRACEROUTE
NETTEST
Bell Canada is my internet service provider.
Any insights/feedback/tips?
Thanks in advance!
Are you connecting via a wireless connection to your router? There may be some packet loss occurring. Some other games won't notice that loss, but STO (being that it's a far more network intensive game than most) will.
Your nettest results are fine, in most cases well above the standard results. Just make sure when you're posting nettest results not to post your local IP. (you can always block that out before reposting results)
In regards to the post above that one....
Holy lag monster, Batman....
Everything from hop 7 on is beyond problematic (over 150ms). Have you attempted connecting via either one of the proxies provided to see if that clears up a little? Is this consistently happening or randomly occuring? It may help to run several traces over a period of time and see how it patterns out.
ROLL TIDE ROLL
I'm not connecting via a wireless router, as the big heap of cables under my desk will testify
Anyhow, I really appreciate the help! Thanks again!
I would suggest running another trace later to confirm the results you're getting from the one you've posted. Lag is a tricky devil to pin down, and what one trace reveals another may not.
Probably going to need more help than I'm qualified to provide, though. Submitting a ticket will likely yield some more answers...although be forewarned, tickets are usually dealt with according to set procedures, which means you may or may not be provided with a copy/paste standardized answer. Make sure when you're submitting your ticket that you list any and all things you have done to date to help solve this issue, as well as a copy of your traceroute/nettest results. And don't be afraid to follow up if your first response doesn't help your issue.
ROLL TIDE ROLL
I hope this helps. These settings for MTU etc should be found in your modem.
Also he told me to alter the QoS settings. There fairly simple to do once you know how. The only thing about this kinda thing is every ISP is different but some very simple changes can make a big difference. My Modem had my MTU settings set to 1400 which he said were way to low and so I changed them to 1454. Its kinda cool when the technical person on the other end of the phone isnt just some guy, but actually knows what he is talking about because no other support guy has ever told me to do some of the things he told me to do. Sometimes you get good support advice and sometimes you dont.
tracing results
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 6 ms 44 ms 7 ms cpc14-sotn9-2-0-gw.15-1.cable.virginmedia.com [86.3.216.1]
2 6 ms 6 ms 9 ms sotn-core-1b-ae4-3865.network.virginmedia.net [80.4.225.233]
3 10 ms 11 ms 12 ms glfd-bb-1b-ae3-0.network.virginmedia.net [212.43.163.153]
4 12 ms 14 ms 11 ms nrth-bb-1a-as5-0.network.virginmedia.net [212.43.163.182]
5 14 ms 12 ms 14 ms nrth-tmr-1-ae1-0.network.virginmedia.net [213.105.159.30]
6 27 ms 28 ms 27 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
7 30 ms 28 ms 28 ms te0-7-0-7.mpd22.fra03.atlas.cogentco.com [130.117.14.133]
8 27 ms 30 ms 29 ms te0-2-0-2.mpd22.ams03.atlas.cogentco.com [130.117.3.85]
9 35 ms 34 ms 33 ms te0-1-0-2.ccr22.lpl01.atlas.cogentco.com [154.54.37.110]
10 101 ms 103 ms 100 ms te0-5-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.217]
11 224 ms 109 ms 445 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 108 ms 105 ms 107 ms 38.111.40.114
13 102 ms 99 ms 99 ms 208.95.185.41
Trace complete.
NETTEST RESULTS
Local IP: ********
Ping: 91.2 msec
Port: 80: 503 KB/sec 18 KB/sec 531 KB/sec 500
Port: 80: 505 KB/sec 18 KB/sec 532 KB/sec 500
Port: 443: 507 KB/sec 18 KB/sec 535 KB/sec 500
Port: 443: 510 KB/sec 19 KB/sec 539 KB/sec 500
Port: 7255: 508 KB/sec 18 KB/sec 537 KB/sec 500
Port: 7255: 508 KB/sec 17 KB/sec 538 KB/sec 500
Port: 7003: 507 KB/sec 16 KB/sec 536 KB/sec 500
Port: 7003: 488 KB/sec 18 KB/sec 515 KB/sec 500
Port: 7202: 494 KB/sec 18 KB/sec 522 KB/sec 500
Port: 7202: 492 KB/sec 16 KB/sec 519 KB/sec 500
Port: 7499: 484 KB/sec 18 KB/sec 512 KB/sec 500
Port: 7499: 507 KB/sec 19 KB/sec 536 KB/sec 500
Port: 80: 509 KB/sec 18 KB/sec 537 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
ive tryed everything on this forum before i start getting linked to other posts and yes reported it to a GM only to get fobbed off to to this forum i was gonna buy a lifetime account but if this is the way cryptic $tudio$ and p?rf?ct world roll i think i'll pass.
2 15 ms 14 ms 15 ms network-184-059-242-015.midohio.rr.com [184.59.2
42.15]
3 17 ms 15 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
4 31 ms 31 ms 30 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
5 34 ms 117 ms 23 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
6 34 ms 35 ms 37 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54
.11.145]
7 36 ms 36 ms 38 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com [154.54
.5.1]
8 47 ms 44 ms 43 ms te0-0-0-2.ccr22.bos01.atlas.cogentco.com [154.54
.43.202]
9 48 ms 48 ms 46 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 53 ms 53 ms 53 ms 38.111.40.114
11 45 ms * 45 ms 208.95.185.41
Ping: 48.4 msec
Port: 80: 827 KB/sec 34 KB/sec 871 KB/sec 500
Port: 80: 509 KB/sec 77 KB/sec 560 KB/sec 500
Port: 443: 1358 KB/sec 267 KB/sec 1435 KB/sec 500
Port: 443: 1369 KB/sec 49 KB/sec 1451 KB/sec 500
Port: 7255: 1329 KB/sec 147 KB/sec 1408 KB/sec 500
Port: 7255: 1340 KB/sec 170 KB/sec 1417 KB/sec 500
Port: 7003: 678 KB/sec 42 KB/sec 716 KB/sec 500
Port: 7003: 419 KB/sec 219 KB/sec 447 KB/sec 500
Port: 7202: 1422 KB/sec 208 KB/sec 1500 KB/sec 500
Port: 7202: 1258 KB/sec 98 KB/sec 1327 KB/sec 500
Port: 7499: 1437 KB/sec 51 KB/sec 1520 KB/sec 500
Port: 7499: 1382 KB/sec 49 KB/sec 1464 KB/sec 500
Port: 80: 392 KB/sec 39 KB/sec 413 KB/sec 500
Idle NIC bandwidth Send: 161 KB/sec Recv: 3 KB/sec
hit return to exit
So I am getting bad rubber banding..and dc'ed alot. never had this issue before.
C:\Users\David>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ************
2 29 ms 13 ms 21 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [67.242.192.1]
3 12 ms 11 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
4 13 ms 12 ms 12 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
5 23 ms 24 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 22 ms 23 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 19 ms 22 ms 19 ms 107.14.19.147
8 21 ms 21 ms 22 ms te0-0-0-5.ccr21.jfk05.atlas.cogentco.com [154.54.13.185]
9 20 ms 21 ms 22 ms te0-1-0-5.mpd21.jfk02.atlas.cogentco.com [154.54.3.97]
10 26 ms 27 ms 25 ms te0-3-0-2.ccr21.bos01.atlas.cogentco.com [154.54.44.14]
11 25 ms 28 ms 28 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 26 ms 35 ms 35 ms 38.111.40.114
13 27 ms 26 ms 27 ms 208.95.185.41
Trace complete.
The above seems better than my first time around back in post #11 (July 2011).
This on the other hand, I'm not sure...
contacting nettest server..
Local IP: ************
Ping: 25.9 msec
Port: ..80: 1465 KB/sec 45 KB/sec 1554 KB/sec 500
Port: ..80: 1985 KB/sec 54 KB/sec 2101 KB/sec 500
Port: .443: 2010 KB/sec 58 KB/sec 2127 KB/sec 500
Port: . 443: 1859 KB/sec 52 KB/sec 1972 KB/sec 500
Port: 7255: 1935 KB/sec 57 KB/sec 2052 KB/sec 500
Port: 7255: 2005 KB/sec 55 KB/sec 2122 KB/sec 500
Port: 7003: 2063 KB/sec 56 KB/sec 2191 KB/sec 500
Port: 7003: 1887 KB/sec 57 KB/sec 2001 KB/sec 500
Port: 7202: 1724 KB/sec 51 KB/sec 1828 KB/sec 500
Port: 7202: 565 KB/sec 20 KB/sec 602 KB/sec 500
Port: 7499: 1761 KB/sec 49 KB/sec 1865 KB/sec 500
Port: 7499: 1984 KB/sec 56 KB/sec 2094 KB/sec 500
Port: .. 80: 1588 KB/sec 58 KB/sec 1675 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 4 KB/sec
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
So anyone going from STO going to reply to this? Or is this a waste of time like your ticket system?
It was started by a fellow player who was kind enough to try and give some aid to folks having problems.
If you read the first couple of posts, you might get a bit of self-help there.
But don't expect anybody from Cryptic to chime in here.
Your Trace data seems to indicate a fairly good communication between your 'puter and the STO Server...,
But your Bandwidth seems like TRIBBLE... SEND 161 KB/sec .... RECEIVE 3 KB/sec.
I'm no expert, but I'd look into that.
I Was A Trekkie Before It Was Cool ... Sept. 8th, 1966 ... Not To Mention Before Most Folks Around Here Were Born!
Forever a STO Veteran-Minion
I thought this was a Cryptic thing. But either way...My bandwidth is is suposed to be a lot higher. I was on the phone againw ith my ISP. I told them I think it is a line problem. And for the heck of it. I am having the modem switch out.
But I am going to a live issue. Being thats what seems to happen alot.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.3
2 2 ms 1 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 12 ms 7 ms 8 ms ten0-0-0-6.orld10-ser1.bhn.net [72.31.194.50]
5 19 ms 12 ms 21 ms ten0-13-0-13.orld71-car1.bhn.net [72.31.195.172]
6 11 ms 15 ms 11 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
7 18 ms 19 ms 19 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
8 20 ms 22 ms 23 ms 107.14.19.38
9 16 ms 16 ms 18 ms 107.14.19.13
10 20 ms 18 ms * te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
11 20 ms 23 ms 21 ms te0-0-0-1.mpd22.atl01.atlas.cogentco.com [154.54
.3.145]
12 33 ms 32 ms 33 ms te0-2-0-3.mpd22.dca01.atlas.cogentco.com [154.54
.2.102]
13 39 ms 40 ms 40 ms te0-7-0-5.mpd22.jfk02.atlas.cogentco.com [154.54
.41.30]
14 45 ms 45 ms 52 ms te0-3-0-5.ccr21.bos01.atlas.cogentco.com [154.54
.44.34]
15 49 ms 44 ms 43 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 * 46 ms 52 ms 38.111.40.114
17 46 ms 45 ms 44 ms 208.95.185.41
Trace complete.
And the Nettest, which I could not copy and paste for some reason, hovered around 50 kB/sec.
You're getting timeouts and partial misses early in your trace, which likely means an issue on your ISP's network.
Also, 50 KB/s....first and third column, or middle? If it's first and third, that's kinda atrocious...
ROLL TIDE ROLL
1 1 ms <1 ms <1 ms 192.168.0.1
2 43 ms 44 ms 44 ms L100.LSANCA-DSL-26.verizon-gni.net
3 45 ms 47 ms 43 ms P0-1-3-0.LSANCA-LCR-22.verizon-gni.net [130.81.33.206]
4 44 ms 43 ms 44 ms ae0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.246]
5 45 ms 45 ms 44 ms 0.so-7-3-0.XT1.LAX7.ALTER.NET [152.63.10.145]
6 127 ms 127 ms 128 ms 0.ge-4-3-0.XL3.BOS4.ALTER.NET [152.63.16.34]
7 126 ms 127 ms 126 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 126 ms 125 ms 125 ms internap-gw.customer.alter.net [65.207.236.58]
9 126 ms 125 ms 126 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
10 125 ms 125 ms 125 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
11 125 ms 126 ms 126 ms 208.95.185.41
Trace complete.
Ping: 125.1 msec
Port: 80: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 80: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 443: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 443: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7255: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7255: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7003: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7003: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7202: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7202: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7499: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 7499: 118 KB/sec 7 KB/sec 125 KB/sec 500
Port: 80: 118 KB/sec 7 KB/sec 125 KB/sec 500
???
Traceroute from the highlighted points is high enough to be problematic, starting from just off the Verizon network. Your nettest results are abnormally low, too.
Not sure if there's anything your ISP would be able to do about the latency portion, but perhaps they can help you improve your connection to closer to normal levels for your nettest (you're wanting to shoot for at least 200 KB/s for first and third column values and 20 KB/s for the second).
ROLL TIDE ROLL
Much appreciation!
My ISP uses Roadrunner lightning, i purchase my internet through Brighthouse CFL. In my 20 years of online gaming this has without a doubt been the best and most reliable internet service provider i ever had, i never get disconnects or lag spikes in games, and if anything, only time i ever have connection issues is when my power goes out for extended periods of time (i have decent size battery backup!). I also am Cisco qualified and already knew how to do ping and tracert tests prior to coming to these forums. I seriously doubt it's any nodes near my end and suspect it's problem with Perfect World's servers or local traffic near them.
Here is my recording following this threads instructions:
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 13 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 6 ms 7 ms 16 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 18 ms 19 ms 17 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 21 ms 15 ms 15 ms 107.14.19.38
7 18 ms 16 ms 17 ms 107.14.19.13
8 66 ms 203 ms 204 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 18 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 30 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 40 ms 41 ms 41 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54]
13 41 ms 41 ms 41 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 47 ms 54 ms 53 ms 38.111.40.114
15 43 ms 38 ms 39 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP: 97.103.69.140
Ping: 42.3 msec
Port: 80: 1097 KB/sec 40 KB/sec 1162 KB/sec 500
Port: 80: 1670 KB/sec 61 KB/sec 1763 KB/sec 500
Port: 443: 1638 KB/sec 59 KB/sec 1726 KB/sec 500
Port: 443: 1564 KB/sec 53 KB/sec 1644 KB/sec 500
Port: 7255: 1487 KB/sec 47 KB/sec 1563 KB/sec 500
Port: 7255: 1469 KB/sec 47 KB/sec 1546 KB/sec 500
Port: 7003: 1552 KB/sec 52 KB/sec 1632 KB/sec 500
Port: 7003: 1370 KB/sec 46 KB/sec 1440 KB/sec 500
Port: 7202: 1447 KB/sec 51 KB/sec 1526 KB/sec 500
Port: 7202: 1386 KB/sec 45 KB/sec 1462 KB/sec 500
Port: 7499: 1669 KB/sec 56 KB/sec 1756 KB/sec 500
Port: 7499: 1679 KB/sec 56 KB/sec 1765 KB/sec 500
Port: 80: 1602 KB/sec 56 KB/sec 1685 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
EDIT: Those tracerts seem to give me sparatic high pings on some of the cogentco.com hops. Here is another one showing a 200+ ping on one of thier other hops.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 5 ms 5 ms ten0-0-0-7.orld35-ser1.bhn.net [72.31.194.192]
3 9 ms 11 ms 11 ms ten0-9-0-5.orld71-car1.bhn.net [97.69.193.44]
4 14 ms 7 ms 7 ms hun0-1-0-0.orld71-cbr3.bhn.net [72.31.193.20]
5 27 ms 17 ms 18 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
6 20 ms 15 ms 15 ms 107.14.19.38
7 19 ms 17 ms 17 ms 107.14.19.13
8 18 ms 20 ms 16 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
9 17 ms 17 ms 18 ms te0-3-0-3.ccr22.atl01.atlas.cogentco.com [154.54
.83.201]
10 29 ms 29 ms 29 ms te0-1-0-2.ccr22.dca01.atlas.cogentco.com [154.54
.28.230]
11 34 ms 33 ms 34 ms te0-3-0-4.ccr22.jfk02.atlas.cogentco.com [154.54
.6.14]
12 41 ms 41 ms 42 ms te0-1-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.44.54]
13 61 ms 215 ms 207 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
14 41 ms 53 ms 54 ms 38.111.40.114
15 39 ms 42 ms 38 ms 208.95.185.41
Trace complete.
Have you tried using the US Proxy option setting in the Launcher, as sometimes, the different Internet path from the Proxy can bypass the congestion issue...
Its actually sad, i really enjoyed playing here.
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 22 ms 21 ms 29 ms cpe-72-135-0-1.kc.res.rr.com [72.135.0.1]
2 11 ms 15 ms 9 ms 65.28.16.198
3 53 ms 47 ms 56 ms tge0-8-0-2.ksczksmp-ccr1.kc.rr.com [98.156.42.14
4]
4 56 ms 55 ms 54 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 51 ms 55 ms 56 ms 107.14.17.138
6 308 ms 39 ms 39 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
7 39 ms 36 ms 38 ms 107.14.17.234
8 90 ms 87 ms 87 ms te0-7-0-15.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
9 91 ms 83 ms 123 ms 154.54.88.78
10 98 ms 95 ms 98 ms te0-3-0-0.mpd21.mci01.atlas.cogentco.com [154.54
.3.18]
11 98 ms 117 ms 111 ms te0-5-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.45.154]
12 * 119 ms 101 ms te0-2-0-2.ccr21.bos01.atlas.cogentco.com [154.54
.43.178]
13 101 ms 101 ms 97 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 117 ms 108 ms 107 ms 38.111.40.114
15 103 ms 105 ms 105 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
I couldn't run the nettest.exe, each time I tried I got a "timed out" message. I don't know how to get past that.
We can if you haven't bothered to perform the tests in this sticky. "I can play other online games" is completely irrelevant to the issue at hand. Other games follow a completely different pathing to their servers, ergo, what's affecting the route to the STO servers won't affect another game unless they use identical segments of a given route.
So run the tests, post your results, and then perhaps we can help you find your problem.
That's a little telling in itself. Have you made any changes to your PC or your firewall? You may have to allow a firewall exception for nettest.exe in order for it to run properly.
Your traceroute is fine, up until the final hops. Those readings are a little bit on the high side there. Unfortunately, it's persistent with the segment of the route controlled by Cogent Communications, with whom PWE has been working on this issue for several months now. However, it's not as easy as "well, duh, just get another ISP!!" considering that PWE would require a provider capable of handling immense amounts of bandwidth--which you can't really get from your garden-variety ISP.
ROLL TIDE ROLL
Besides complaining to your ISP, have you tried using the US Proxy option in the Launcher, as sometimes, this can bypass the localized network congestion...