Recently I?ve been having some pretty crippling lag and disconnections. I Think it started roughly around 3am EST, (though I cant remember exactly), October 29th. Connection was great before that.
My ISP is Bell Aliant, up here in NB Canada. Ran the tracert and the nettest though I could use a little help making sense of the results.
tracert
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 5 ms 192.168.2.1
2 6 ms 7 ms 5 ms 10.255.252.1
3 4 ms 3 ms 3 ms irb-84.dr02.fctn.nb.aliant.net [142.166.211.17]
4 7 ms 7 ms 3 ms ae7.cr02.stjh.nb.aliant.net [142.166.185.145]
5 9 ms 7 ms 7 ms ae6.cr02.hlfx.ns.aliant.net [142.166.181.137]
6 19 ms 11 ms 11 ms be3.cr01.hlfx.ns.aliant.net [142.166.181.141]
7 23 ms 23 ms 23 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
8 28 ms 27 ms 70 ms nyk-b5-link.telia.net [213.248.83.181]
9 24 ms 28 ms 26 ms cogent-ic-151338-nyk-b5.c.telia.net [213.248.85.
106]
10 27 ms 25 ms 23 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
.57]
11 29 ms 27 ms 28 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 38 ms 195 ms 27 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
13 32 ms 35 ms 35 ms 38.111.40.114
14 26 ms 28 ms 27 ms 208.95.185.41
Recently I?ve been having some pretty crippling lag and disconnections. I Think it started roughly around 3am EST, (though I cant remember exactly), October 29th. Connection was great before that.
My ISP is Bell Aliant, up here in NB Canada. Ran the tracert and the nettest though I could use a little help making sense of the results.
tracert
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 5 ms 192.168.2.1
2 6 ms 7 ms 5 ms 10.255.252.1
3 4 ms 3 ms 3 ms irb-84.dr02.fctn.nb.aliant.net [142.166.211.17]
4 7 ms 7 ms 3 ms ae7.cr02.stjh.nb.aliant.net [142.166.185.145]
5 9 ms 7 ms 7 ms ae6.cr02.hlfx.ns.aliant.net [142.166.181.137]
6 19 ms 11 ms 11 ms be3.cr01.hlfx.ns.aliant.net [142.166.181.141]
7 23 ms 23 ms 23 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
8 28 ms 27 ms 70 ms nyk-b5-link.telia.net [213.248.83.181]
9 24 ms 28 ms 26 ms cogent-ic-151338-nyk-b5.c.telia.net [213.248.85.
106]
10 27 ms 25 ms 23 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
.57]
11 29 ms 27 ms 28 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14] 12 38 ms 195 ms 27 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
13 32 ms 35 ms 35 ms 38.111.40.114
14 26 ms 28 ms 27 ms 208.95.185.41
Trace complete.
Thanks
Looks like the Cogent Boston hub is acting up again...
You should post these diagnostic results in the Networking section of the PWE Tech Support site, so they can use this data to kick Cogent a few more times with to try to get this fixed.... http://techsupport.perfectworld.com/
Recently I?ve been having some pretty crippling lag and disconnections. I Think it started roughly around 3am EST, (though I cant remember exactly), October 29th. Connection was great before that.
My ISP is Bell Aliant, up here in NB Canada. Ran the tracert and the nettest though I could use a little help making sense of the results.
tracert
nettest
Thanks
Having the same problem as you, same ISP, only in Nova Scotia.
Also the same issue using Bell Aliant in NS. Seems to be abit of a trend here. I've done a complete reformat. Contacted my isp, had the connection turned off, then turned back on. Had the connection reset twice. Router reset to manufacturers. I've done numerous traces. Unfortunately the tracert shows the same as j0hn41.
Cogentco seems to be the issue for the connection. What j0hn41's tracert doesn't show, is that along side massive latency spikes, Cogentco is suffering from MASSIVE packet loss and errors. The packet loss and errors continue right up to Craptics front door.
Funny though, Aliant's network hops are low latency and barely if any packet loss. I'm sure some clown will come along and say its Bell Aliant though...because Craptic's Cogentco connection works for them.
Personally I firmly believe that Craptic has a bummed out route to the patch server and login server. Not a route that every user uses, and so only affects a small percentage of users. Unfortunately unless there are enough complaints, little if anything will be done.
1 1 ms 3 ms <1 ms 192.168.1.1
2 33 ms 31 ms 30 ms cpe-172-251-176-1.socal.res.rr.com [172.251.176.
1]
3 15 ms 12 ms 11 ms tge0-7-0-1.snmncaby01h.socal.rr.com [76.166.16.8
9]
4 13 ms 11 ms 14 ms agg10.snmncaby02h.socal.rr.com [72.129.10.133]
5 19 ms 10 ms 15 ms agg20.lamrcadq02r.socal.rr.com [72.129.10.130]
6 17 ms 15 ms 15 ms agg28.tustcaft01r.socal.rr.com [72.129.9.2]
7 14 ms 17 ms 16 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
8 23 ms 18 ms 21 ms ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
9 55 ms 57 ms 55 ms te0-0-0-29.ccr23.lax05.atlas.cogentco.com [154.5
4.10.249]
10 61 ms 55 ms 55 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41
.113]
11 90 ms 69 ms 70 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.
161]
12 68 ms 70 ms 76 ms be2173.ccr22.atl01.atlas.cogentco.com [154.54.29
.117]
13 86 ms 85 ms 98 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
14 86 ms 85 ms 82 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31
.130]
15 92 ms 89 ms 91 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42] 16 296 ms 211 ms 215 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
17 90 ms 89 ms 88 ms 38.111.40.114
18 94 ms 92 ms 89 ms 208.95.185.41
Trace complete.
Note: I am being timedout everytime I change maps and the reconnect is slow. I already did the ipconfig /release & renew thing. I got the above quoted results after.
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.1.1
2 50 ms 27 ms 29 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [67.242.192.1]
3 11 ms 12 ms 12 ms gig8-46.schnny52-rtr001.alb.northeast.rr.com [24.29.46.201]
4 11 ms 12 ms 16 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
5 25 ms 22 ms 40 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 25 ms 23 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 * 21 ms 21 ms 66.109.1.35
8 57 ms 65 ms 53 ms te0-0-0-17.ccr21.jfk05.atlas.cogentco.com [154.54.13.81]
9 54 ms 57 ms 58 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31.9]
10 59 ms 62 ms 60 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
11 59 ms 58 ms 61 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 57 ms 35 ms 35 ms 38.111.40.114
13 57 ms 28 ms 27 ms 208.95.185.41
Trace complete.
What does the STAR mean at #7?
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
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 36 ms 24 ms 28 ms cpe-172-250-112-1.socal.res.rr.com [172.250.112.
1]
2 10 ms 10 ms 7 ms tge0-6-0-2.lsaicaev01h.socal.rr.com [76.166.24.1
93]
3 8 ms 10 ms 10 ms agg11.lsaicaev01r.socal.rr.com [72.129.18.192]
4 11 ms 10 ms 9 ms agg26.lsancarc01r.socal.rr.com [72.129.17.0]
5 12 ms 10 ms 12 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.212]
6 17 ms 11 ms 10 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
7 51 ms 47 ms 45 ms te0-4-0-17.ccr23.lax05.atlas.cogentco.com [154.5
4.11.133]
8 46 ms 48 ms 53 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41
.57]
9 115 ms 110 ms 109 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.
65]
10 113 ms * 112 ms be2175.mpd22.atl01.atlas.cogentco.com [154.54.29
.221]
11 90 ms 91 ms 91 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
12 99 ms 99 ms 102 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
13 104 ms 109 ms 108 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
14 106 ms 100 ms 100 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
15 89 ms 87 ms 88 ms 38.111.40.114
16 94 ms 81 ms 81 ms 208.95.185.41
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\IanM>ping rr.com
Pinging rr.com [71.74.42.238] with 32 bytes of data:
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=80ms TTL=54
Ping statistics for 71.74.42.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 82ms, Average = 81ms
C:\Users\IanM>
C:\Users\IanM>tracert google.com
Tracing route to google.com [74.125.224.102]
over a maximum of 30 hops:
1 32 ms 28 ms 29 ms cpe-172-250-112-1.socal.res.rr.com [172.250.112.
1]
2 10 ms 9 ms 8 ms tge0-6-0-2.lsaicaev01h.socal.rr.com [76.166.24.1
93]
3 13 ms 14 ms 13 ms agg11.lsaicaev01r.socal.rr.com [72.129.18.192]
4 9 ms 13 ms 10 ms agg26.lsancarc01r.socal.rr.com [72.129.17.0]
5 12 ms 13 ms 14 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.102]
6 10 ms 10 ms 11 ms 107.14.19.118
7 24 ms 23 ms * 72.14.197.157
8 23 ms 22 ms 25 ms 64.233.174.238
9 8 ms 11 ms 10 ms 209.85.250.245
10 24 ms 22 ms 36 ms lax02s19-in-f6.1e100.net [74.125.224.102]
Edit - I contact Road Runner Tech Support and after I gave them my results (and after I refused to disconnect all of my equipment) the rep did some testing and then told me he would "refresh my signal". He just did that and said he is certain I'll have no more issues. I asked him what the problem was and he said there was some degradation. *shrug* We shall see.
Dear Cryptic, don't you think its just about time to step in and say something? You have got to sort out yours ISP problems! I'm starting to feel stupid for paying a subscripion (700+ days)!
I'm worried about the release of season 8 under this condition!
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 26 ms 26 ms 172.17.--
4 27 ms 26 ms 26 ms 172.--
5 35 ms 36 ms 35 ms 172.17.--
6 39 ms 39 ms 39 ms 172.17.--
7 43 ms 47 ms 45 ms bundle-ether13.milano50.mil.seabone.net [93.186.
128.237]
8 45 ms 48 ms 47 ms xe-3-3-2.franco31.fra.seabone.net [195.22.211.11
2]
9 56 ms 55 ms 57 ms te0-0-0-4.mag21.fra03.atlas.cogentco.com [130.11
7.15.93]
10 56 ms 56 ms 56 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
11 62 ms 58 ms 60 ms te0-5-0-6.mpd21.ams03.atlas.cogentco.com [154.54
.78.173]
12 62 ms 63 ms 62 ms multi-use.cogentco.com [154.54.62.145]
13 69 ms 69 ms 69 ms te0-6-0-2.ccr22.lpl01.atlas.cogentco.com [154.54
.77.230]
14 135 ms 135 ms 134 ms te0-3-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.1.157]
15 267 ms 225 ms 230 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
16 138 ms 144 ms 158 ms 38.111.40.114
17 140 ms 152 ms 139 ms 208.95.185.41
Dear Cryptic, don't you think its just about time to step in and say something? You have got to sort out yours ISP problems! I'm starting to feel stupid for paying a subscripion (700+ days)!
I'm worried about the release of season 8 under this condition!
.
Keep in mind that this is a 'Peer to Peer' support forum. (read the forum description)
If you really want Cryptic/PWE to see this, you should be posting in network section of the PWE Support forum... http://techsupport.perfectworld.com/
I tried running this and it stops like right away at port 80...
Port: 80 0kb/sec 1kb/sec 11kb/sec 232
and it hangs from there... what does this mean?
It means that 'Net Test' can't maintain a reliable connection to the diagnostic server that's on the same local network as the STO servers... Which shows that your problems are not a STO Server issue, their a Internet/network connection issue...
So the next question is 'Why?'... what does the 'Trace Route' results look like?
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 3 ms 1 ms homeportal [192.168.2.1]
2 236 ms * 158 ms loop0.63w.ba11.hlfx.ns.aliant.net [142.176.50.11
]
3 147 ms 159 ms 177 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
4 311 ms * 344 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
5 * 310 ms 217 ms nyk-b5-link.telia.net [213.248.83.181]
6 178 ms 213 ms 207 ms te0-0-0-18.ccr21.jfk07.atlas.cogentco.com [154.5
4.11.69]
7 * 360 ms 438 ms be2056.ccr21.jfk02.atlas.cogentco.com [154.54.44
.217]
8 213 ms 340 ms 303 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
9 * 362 ms * te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 234 ms 267 ms 217 ms 38.111.40.114
11 180 ms * 283 ms 208.95.185.41
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 3 ms 1 ms homeportal [192.168.2.1]
2 236 ms * 158 ms loop0.63w.ba11.hlfx.ns.aliant.net [142.176.50.11
]
3 147 ms 159 ms 177 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
4 311 ms * 344 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
5 * 310 ms 217 ms nyk-b5-link.telia.net [213.248.83.181]
6 178 ms 213 ms 207 ms te0-0-0-18.ccr21.jfk07.atlas.cogentco.com [154.5
4.11.69]
7 * 360 ms 438 ms be2056.ccr21.jfk02.atlas.cogentco.com [154.54.44
.217]
8 213 ms 340 ms 303 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
9 * 362 ms * te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 234 ms 267 ms 217 ms 38.111.40.114
11 180 ms * 283 ms 208.95.185.41
Trace complete.
Yes, they are bad, and with the first hop into the Internet too....
This indicates you have a router/gateway problem. If a reset/power cycle of the router does not correct the problem, then you will have to contact your ISP and have them send a tech person out to take a look at the device...
Ouch, I was hoping that was not to be the case.. as I dont really have control of the ISP or the router... looks like my plans to re-join STO have been squashed by a move to a new place with a new internet provider..
So this morning, I disabled the account protection thing and retried and got this
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms homeportal [***********]
2 22 ms 22 ms 21 ms loop0.63w.ba11.hlfx.ns.aliant.net [142.176.50.11
]
3 31 ms 21 ms 22 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
4 34 ms 34 ms 49 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
5 40 ms 38 ms 39 ms nyk-b5-link.telia.net [213.248.83.181]
6 46 ms 45 ms 46 ms te0-0-0-18.ccr21.jfk07.atlas.cogentco.com [154.5
4.11.69]
7 44 ms 45 ms * be2059.mpd22.jfk02.atlas.cogentco.com [154.54.1.
221]
8 50 ms 51 ms 49 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
9 51 ms 50 ms 49 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 51 ms 53 ms 51 ms 38.111.40.114
11 49 ms 51 ms 49 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
Looks better.. but still the patcher isn't working and... nettest is stalling at port 80 *sigh*
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.1
2 9 ms 9 ms 9 ms 10.206.128.1
3 16 ms 9 ms 9 ms 58.160.24.65
4 9 ms 8 ms 9 ms te6-3.agg2.fli.bigpond.net.au [58.160.27.250]
5 21 ms 22 ms 10 ms 172.18.242.105
6 17 ms 10 ms 11 ms bundle-ether10.way33.waymouth.telstra.net [139.1
30.5.125]
7 10 ms 10 ms 11 ms bundle-ether4.way-core4.adelaide.telstra.net [20
3.50.11.85]
8 24 ms 26 ms 23 ms bundle-ether9.exi-core1.melbourne.telstra.net [2
03.50.11.93]
9 40 ms 38 ms 39 ms bundle-ether12.chw-core2.sydney.telstra.net [203
.50.11.74]
10 665 ms 43 ms 43 ms bundle-ether1.oxf-gw2.sydney.telstra.net [203.50
.6.90]
11 43 ms 39 ms 38 ms 203.50.13.130
12 48 ms 42 ms 40 ms i-0-2-0-6.sydo-core02.bi.telstraglobal.net [202.
84.223.46]
13 181 ms 182 ms 182 ms i-0-2-0-2.1wlt-core01.bx.telstraglobal.net [202.
84.140.21]
14 184 ms 181 ms 184 ms i-0-4-0-0.eqla01.bi.telstraglobal.net [202.84.25
1.174]
15 184 ms 186 ms 183 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159
.63.198]
16 182 ms 184 ms 182 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41
.81]
17 215 ms 223 ms 217 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.
161]
18 232 ms 233 ms 235 ms be2174.mpd21.atl01.atlas.cogentco.com [154.54.29
.201]
19 248 ms 244 ms 243 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
20 248 ms 248 ms 250 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
21 254 ms 251 ms 254 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
22 255 ms 257 ms 255 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
23 259 ms 254 ms 266 ms 38.111.40.114
24 309 ms 277 ms 255 ms patchserver2.crypticstudios.com [208.95.185.41]
Okay, I'm suffering seriously bad rubberbanding very frequently. Here's my tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 8 ms 9 ms L100.WASHDC-VFTTP-93.verizon-gni.net [173.66.179
.1]
3 12 ms 9 ms 14 ms G0-12-4-3.WASHDC-LCR-21.verizon-gni.net [130.81.
184.34]
4 15 ms 10 ms 11 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.30]
5 23 ms 24 ms 26 ms 0.ae1.XL3.BOS4.ALTER.NET [140.222.226.13]
6 33 ms 23 ms 23 ms 0.xe-10-2-0.GW15.BOS4.ALTER.NET [152.63.21.138]
7 29 ms 28 ms 28 ms internap-gw.customer.alter.net [152.179.134.214]
8 581 ms 33 ms 25 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 92 ms 64 ms 81 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 64 ms 61 ms 62 ms patchserver2.crypticstudios.com [208.95.185.41]
Okay, I'm suffering seriously bad rubberbanding very frequently. Here's my tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 8 ms 9 ms L100.WASHDC-VFTTP-93.verizon-gni.net [173.66.179
.1]
3 12 ms 9 ms 14 ms G0-12-4-3.WASHDC-LCR-21.verizon-gni.net [130.81.
184.34]
4 15 ms 10 ms 11 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.30]
5 23 ms 24 ms 26 ms 0.ae1.XL3.BOS4.ALTER.NET [140.222.226.13]
6 33 ms 23 ms 23 ms 0.xe-10-2-0.GW15.BOS4.ALTER.NET [152.63.21.138]
7 29 ms 28 ms 28 ms internap-gw.customer.alter.net [152.179.134.214]
8 581 ms 33 ms 25 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 92 ms 64 ms 81 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 64 ms 61 ms 62 ms patchserver2.crypticstudios.com [208.95.185.41]
Okay, I'm suffering seriously bad rubberbanding very frequently. Here's my tracert:...
My service provider is Verizon and I'm in Northern Virginia. I was on the phone with them earlier and everything is hunky-dory. So... what now?
You should post your Trace Route results in the Networking section of the PWE Tech Support site, so that PWE IT people can do some kicking on their end to try to get this fixed...
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.1.1
2 23 ms 15 ms 22 ms cpe-173-89-160-1.neo.res.rr.com [173.89.160.1]
3 13 ms 12 ms 13 ms gig4-4.genvoh1-rtr1.neo.rr.com [24.164.115.45]
4 11 ms 11 ms 11 ms tge1-5.ashtoh1-swt401.neo.rr.com [24.164.115.160
]
5 13 ms 13 ms 13 ms tge10-1.clvhoh1-rtr2.neo.rr.com [24.164.117.144]
6 15 ms 14 ms 16 ms tge0-8-0-13.clevohek02r.midwest.rr.com [24.164.9
6.79]
7 16 ms 19 ms 18 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 24 ms 24 ms 23 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
9 21 ms 21 ms 21 ms 66.109.1.47
10 22 ms 21 ms 20 ms te0-13-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.13.157]
11 22 ms 22 ms 23 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.
170]
12 29 ms 30 ms 31 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
13 34 ms 41 ms 35 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
14 36 ms 35 ms 36 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
15 36 ms 33 ms 34 ms 38.111.40.114
16 33 ms 34 ms 34 ms patchserver2.crypticstudios.com [208.95.185.41]
I think, according to the tracert result, I should have a good connection. But I still get lag and rubber-banding. I even went as far as uninstalling and reinstalling STO. Still lags after a while.
I can't make heads or tails of it. = /
My service provider, I believe, is Time Warner Cable, and my location is in Madison, Ohio.
Also, I'm using both a hard cable and wifi connection.
I get lag and rubber-banding as well:
...
I think, according to the tracert result, I should have a good connection. But I still get lag and rubber-banding. I even went as far as uninstalling and reinstalling STO. Still lags after a while.
I can't make heads or tails of it. = /
My service provider, I believe, is Time Warner Cable, and my location is in Madison, Ohio.
Also, I'm using both a hard cable and wifi connection.
Unfortunately, neither Trace Route, nor the Cryptic 'Net Test' utility are good tools for detecting packet drop. And silently dropped packets is most likely the cause of your symptoms.
The Microsoft pathping utility from the command prompt may do a better job at this...
Unfortunately, neither Trace Route, nor the Cryptic 'Net Test' utility are good tools for detecting packet drop. And silently dropped packets is most likely the cause of your symptoms.
The Microsoft pathping utility from the command prompt may do a better job at this...
silently dropped packets? what are those, and how do I deal with this problem? How do I use a pathping utility on the prompt?
silently dropped packets? what are those, and how do I deal with this problem? How do I use a pathping utility on the prompt?
'pathping' is very much like the 'tracert' utility. you can follow the same instructions as 'tracert', but use 'pathping' instead...
Now there isn't anything you can really do about 'dropped packets' (packets that are lost, or thrown away during transmission...) as this is a ISP issue. But the 'pathping' should be able to show who's to blame for the problem, and if its the Cogent backbone that's causing, you can forward the information to Cryptic/PWE so they can deal with it. If its not Cogent, then you can complain to your ISP to fix it...
But you have to know who's the responsible party is first, before you can do any of this...
My service provider, I believe, is Time Warner Cable, and my location is in Madison, Ohio.
Also, I'm using both a hard cable and wifi connection.
Yep Time warner cable
IP address 173.89.160.0
Hostname cpe-173-89-160-0.neo.res.rr.com
Area code (US Only) 440
Metropolitan Area (US Only) Cleveland-Akron (Canton) OH
City Geneva
State/Province OH
Country United States
ISP Time Warner Cable
Organisation Time Warner Cable
Up-to-date? Yes, IP Address information is less than 3 months old.
Tools - Whois information for IP address 173.89.160.0
- Convert 173.89.160.0 to an IPv6 address
I have been getting bad lag and rubberbanding lately. I am trying to connect from Goose Creek, SC using Comcast.
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.1.1
2 59 ms 41 ms 15 ms 76.23.104.1
3 11 ms 10 ms 12 ms te-9-4-ur01.goosecreek.sc.chrlstn.comcast.net [6
8.85.123.13]
4 12 ms 11 ms 11 ms te-7-4-ar02.charleston.sc.chrlstn.comcast.net [6
8.86.144.57]
5 30 ms 46 ms 27 ms 68.87.164.121
6 64 ms 42 ms 42 ms pos-3-15-0-0-cr01.56marietta.ga.ibone.comcast.ne
t [68.86.91.221]
7 * * * Request timed out.
8 85 ms 85 ms 86 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.5
4.10.233]
9 86 ms 85 ms 85 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.
165]
10 108 ms 123 ms 110 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
.94]
11 109 ms 139 ms 125 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
12 113 ms 117 ms 123 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
13 138 ms 122 ms 120 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 77 ms 85 ms 77 ms 38.111.40.114
15 90 ms 74 ms 74 ms patchserver2.crypticstudios.com [208.95.185.41]
My location Czech republic (europe)
Provider: Telefonica Czech Republic / O2.cz
Internet run perfectly, probl?m is only in STO
V?pis trasy k patchserver.crypticstudios.com [208.95.185.41]
s nejv??e 30 směrov?n?mi:
1 < 1 ms < 1 ms < 1 ms 10.0.0.138
2 18 ms 17 ms 17 ms 88.103.200.71
3 26 ms 26 ms 25 ms 88.103.203.137
4 28 ms 27 ms 27 ms 194.228.190.85
5 26 ms 27 ms 27 ms 194.228.190.193
6 26 ms 26 ms 26 ms 5.53.0.89
7 49 ms 49 ms 49 ms 5.53.7.118
8 174 ms 218 ms 215 ms 213.140.52.210
9 68 ms 65 ms 65 ms te0-7-0-8.mpd21.par01.atlas.cogentco.com [130.117.1.69]
10 65 ms * 68 ms te0-4-0-6.mpd21.lon13.atlas.cogentco.com [154.54.37.157]
11 139 ms 139 ms 139 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
12 * 137 ms * te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 144 ms 144 ms 142 ms 38.111.40.114
14 140 ms 139 ms 137 ms patchserver2.crypticstudios.com [208.95.185.41]
Comments
Recently I?ve been having some pretty crippling lag and disconnections. I Think it started roughly around 3am EST, (though I cant remember exactly), October 29th. Connection was great before that.
My ISP is Bell Aliant, up here in NB Canada. Ran the tracert and the nettest though I could use a little help making sense of the results.
tracert
nettest
Thanks
Looks like the Cogent Boston hub is acting up again...
You should post these diagnostic results in the Networking section of the PWE Tech Support site, so they can use this data to kick Cogent a few more times with to try to get this fixed.... http://techsupport.perfectworld.com/
John
Having the same problem as you, same ISP, only in Nova Scotia.
Cogentco seems to be the issue for the connection. What j0hn41's tracert doesn't show, is that along side massive latency spikes, Cogentco is suffering from MASSIVE packet loss and errors. The packet loss and errors continue right up to Craptics front door.
Funny though, Aliant's network hops are low latency and barely if any packet loss. I'm sure some clown will come along and say its Bell Aliant though...because Craptic's Cogentco connection works for them.
Personally I firmly believe that Craptic has a bummed out route to the patch server and login server. Not a route that every user uses, and so only affects a small percentage of users. Unfortunately unless there are enough complaints, little if anything will be done.
Note: I am being timedout everytime I change maps and the reconnect is slow. I already did the ipconfig /release & renew thing. I got the above quoted results after.
http://techsupport.perfectworld.com/showthread.php?t=38071
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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 192.168.1.1
2 50 ms 27 ms 29 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [67.242.192.1]
3 11 ms 12 ms 12 ms gig8-46.schnny52-rtr001.alb.northeast.rr.com [24.29.46.201]
4 11 ms 12 ms 16 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
5 25 ms 22 ms 40 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 25 ms 23 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 * 21 ms 21 ms 66.109.1.35
8 57 ms 65 ms 53 ms te0-0-0-17.ccr21.jfk05.atlas.cogentco.com [154.54.13.81]
9 54 ms 57 ms 58 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31.9]
10 59 ms 62 ms 60 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
11 59 ms 58 ms 61 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 57 ms 35 ms 35 ms 38.111.40.114
13 57 ms 28 ms 27 ms 208.95.185.41
Trace complete.
What does the STAR mean at #7?
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
well I too have been having the same issues lately only I'm in Los Angeles with Road Runner / Time Warner.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\IanM>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 36 ms 24 ms 28 ms cpe-172-250-112-1.socal.res.rr.com [172.250.112.
1]
2 10 ms 10 ms 7 ms tge0-6-0-2.lsaicaev01h.socal.rr.com [76.166.24.1
93]
3 8 ms 10 ms 10 ms agg11.lsaicaev01r.socal.rr.com [72.129.18.192]
4 11 ms 10 ms 9 ms agg26.lsancarc01r.socal.rr.com [72.129.17.0]
5 12 ms 10 ms 12 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.212]
6 17 ms 11 ms 10 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
7 51 ms 47 ms 45 ms te0-4-0-17.ccr23.lax05.atlas.cogentco.com [154.5
4.11.133]
8 46 ms 48 ms 53 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41
.57]
9 115 ms 110 ms 109 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.
65]
10 113 ms * 112 ms be2175.mpd22.atl01.atlas.cogentco.com [154.54.29
.221]
11 90 ms 91 ms 91 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31
.98]
12 99 ms 99 ms 102 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
13 104 ms 109 ms 108 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
14 106 ms 100 ms 100 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
15 89 ms 87 ms 88 ms 38.111.40.114
16 94 ms 81 ms 81 ms 208.95.185.41
Trace complete.
C:\Users\IanM>
contacting nettest server..
Local IP: 172.250.113.48
Ping: 83.3 msec
Port: 80: 747 KB/sec 19 KB/sec 786 KB/sec 500
Port: 80: 760 KB/sec 21 KB/sec 800 KB/sec 500
Port: 443: 753 KB/sec 23 KB/sec 797 KB/sec 500
Port: 443: 747 KB/sec 21 KB/sec 789 KB/sec 500
Port: 7255: 766 KB/sec 21 KB/sec 809 KB/sec 500
Port: 7255: 753 KB/sec 23 KB/sec 797 KB/sec 500
Port: 7003: 744 KB/sec 20 KB/sec 790 KB/sec 500
Port: 7003: 770 KB/sec 21 KB/sec 814 KB/sec 500
Port: 7202: 756 KB/sec 23 KB/sec 800 KB/sec 500
Port: 7202: 748 KB/sec 21 KB/sec 790 KB/sec 500
Port: 7499: 769 KB/sec 21 KB/sec 813 KB/sec 500
Port: 7499: 749 KB/sec 21 KB/sec 789 KB/sec 500
Port: 80: 787 KB/sec 22 KB/sec 828 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\IanM>ping rr.com
Pinging rr.com [71.74.42.238] with 32 bytes of data:
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=82ms TTL=54
Reply from 71.74.42.238: bytes=32 time=80ms TTL=54
Ping statistics for 71.74.42.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 82ms, Average = 81ms
C:\Users\IanM>
C:\Users\IanM>tracert google.com
Tracing route to google.com [74.125.224.102]
over a maximum of 30 hops:
1 32 ms 28 ms 29 ms cpe-172-250-112-1.socal.res.rr.com [172.250.112.
1]
2 10 ms 9 ms 8 ms tge0-6-0-2.lsaicaev01h.socal.rr.com [76.166.24.1
93]
3 13 ms 14 ms 13 ms agg11.lsaicaev01r.socal.rr.com [72.129.18.192]
4 9 ms 13 ms 10 ms agg26.lsancarc01r.socal.rr.com [72.129.17.0]
5 12 ms 13 ms 14 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.102]
6 10 ms 10 ms 11 ms 107.14.19.118
7 24 ms 23 ms * 72.14.197.157
8 23 ms 22 ms 25 ms 64.233.174.238
9 8 ms 11 ms 10 ms 209.85.250.245
10 24 ms 22 ms 36 ms lax02s19-in-f6.1e100.net [74.125.224.102]
Trace complete.
C:\Users\IanM>
Latest Speedtest result:
http://www.speedtest.net/result/3073486179.png
Is the commonality here Cogent?
Cheers.
Edit - I contact Road Runner Tech Support and after I gave them my results (and after I refused to disconnect all of my equipment) the rep did some testing and then told me he would "refresh my signal". He just did that and said he is certain I'll have no more issues. I asked him what the problem was and he said there was some degradation. *shrug* We shall see.
Builds:
http://tinyurl.com/kqqg8f5
http://tinyurl.com/n3ewgcw
I'm worried about the release of season 8 under this condition!
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 26 ms 26 ms 172.17.--
4 27 ms 26 ms 26 ms 172.--
5 35 ms 36 ms 35 ms 172.17.--
6 39 ms 39 ms 39 ms 172.17.--
7 43 ms 47 ms 45 ms bundle-ether13.milano50.mil.seabone.net [93.186.
128.237]
8 45 ms 48 ms 47 ms xe-3-3-2.franco31.fra.seabone.net [195.22.211.11
2]
9 56 ms 55 ms 57 ms te0-0-0-4.mag21.fra03.atlas.cogentco.com [130.11
7.15.93]
10 56 ms 56 ms 56 ms be2028.mpd21.fra03.atlas.cogentco.com [154.54.74
.137]
11 62 ms 58 ms 60 ms te0-5-0-6.mpd21.ams03.atlas.cogentco.com [154.54
.78.173]
12 62 ms 63 ms 62 ms multi-use.cogentco.com [154.54.62.145]
13 69 ms 69 ms 69 ms te0-6-0-2.ccr22.lpl01.atlas.cogentco.com [154.54
.77.230]
14 135 ms 135 ms 134 ms te0-3-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.1.157]
15 267 ms 225 ms 230 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
16 138 ms 144 ms 158 ms 38.111.40.114
17 140 ms 152 ms 139 ms 208.95.185.41
Trace complete.
Keep in mind that this is a 'Peer to Peer' support forum. (read the forum description)
If you really want Cryptic/PWE to see this, you should be posting in network section of the PWE Support forum... http://techsupport.perfectworld.com/
Port: 80 0kb/sec 1kb/sec 11kb/sec 232
and it hangs from there... what does this mean?
It means that 'Net Test' can't maintain a reliable connection to the diagnostic server that's on the same local network as the STO servers... Which shows that your problems are not a STO Server issue, their a Internet/network connection issue...
So the next question is 'Why?'... what does the 'Trace Route' results look like?
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 3 ms 3 ms 1 ms homeportal [192.168.2.1]
2 236 ms * 158 ms loop0.63w.ba11.hlfx.ns.aliant.net [142.176.50.11
]
3 147 ms 159 ms 177 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
4 311 ms * 344 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
5 * 310 ms 217 ms nyk-b5-link.telia.net [213.248.83.181]
6 178 ms 213 ms 207 ms te0-0-0-18.ccr21.jfk07.atlas.cogentco.com [154.5
4.11.69]
7 * 360 ms 438 ms be2056.ccr21.jfk02.atlas.cogentco.com [154.54.44
.217]
8 213 ms 340 ms 303 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30
.38]
9 * 362 ms * te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
10 234 ms 267 ms 217 ms 38.111.40.114
11 180 ms * 283 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
Lotta high numbers... which seems bad...
Yes, they are bad, and with the first hop into the Internet too....
This indicates you have a router/gateway problem. If a reset/power cycle of the router does not correct the problem, then you will have to contact your ISP and have them send a tech person out to take a look at the device...
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms homeportal [***********]
2 22 ms 22 ms 21 ms loop0.63w.ba11.hlfx.ns.aliant.net [142.176.50.11
]
3 31 ms 21 ms 22 ms BE7-84.cr01.hlfx.ns.aliant.net [142.176.53.50]
4 34 ms 34 ms 49 ms be5.bx01.nycm.ny.aliant.net [207.231.227.90]
5 40 ms 38 ms 39 ms nyk-b5-link.telia.net [213.248.83.181]
6 46 ms 45 ms 46 ms te0-0-0-18.ccr21.jfk07.atlas.cogentco.com [154.5
4.11.69]
7 44 ms 45 ms * be2059.mpd22.jfk02.atlas.cogentco.com [154.54.1.
221]
8 50 ms 51 ms 49 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
9 51 ms 50 ms 49 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 51 ms 53 ms 51 ms 38.111.40.114
11 49 ms 51 ms 49 ms 208.95.185.41
Trace complete.
C:\Windows\system32>
Looks better.. but still the patcher isn't working and... nettest is stalling at port 80 *sigh*
My location is Adelaide, Australia.
Tracert below:
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 10.206.128.1
3 16 ms 9 ms 9 ms 58.160.24.65
4 9 ms 8 ms 9 ms te6-3.agg2.fli.bigpond.net.au [58.160.27.250]
5 21 ms 22 ms 10 ms 172.18.242.105
6 17 ms 10 ms 11 ms bundle-ether10.way33.waymouth.telstra.net [139.1
30.5.125]
7 10 ms 10 ms 11 ms bundle-ether4.way-core4.adelaide.telstra.net [20
3.50.11.85]
8 24 ms 26 ms 23 ms bundle-ether9.exi-core1.melbourne.telstra.net [2
03.50.11.93]
9 40 ms 38 ms 39 ms bundle-ether12.chw-core2.sydney.telstra.net [203
.50.11.74]
10 665 ms 43 ms 43 ms bundle-ether1.oxf-gw2.sydney.telstra.net [203.50
.6.90]
11 43 ms 39 ms 38 ms 203.50.13.130
12 48 ms 42 ms 40 ms i-0-2-0-6.sydo-core02.bi.telstraglobal.net [202.
84.223.46]
13 181 ms 182 ms 182 ms i-0-2-0-2.1wlt-core01.bx.telstraglobal.net [202.
84.140.21]
14 184 ms 181 ms 184 ms i-0-4-0-0.eqla01.bi.telstraglobal.net [202.84.25
1.174]
15 184 ms 186 ms 183 ms cogent-peer.eqla01.pr.telstraglobal.net [134.159
.63.198]
16 182 ms 184 ms 182 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41
.81]
17 215 ms 223 ms 217 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.
161]
18 232 ms 233 ms 235 ms be2174.mpd21.atl01.atlas.cogentco.com [154.54.29
.201]
19 248 ms 244 ms 243 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
20 248 ms 248 ms 250 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40
.74]
21 254 ms 251 ms 254 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
22 255 ms 257 ms 255 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
23 259 ms 254 ms 266 ms 38.111.40.114
24 309 ms 277 ms 255 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
And nettest below:
contacting nettest server..
Local IP: 101.166.33.122
Ping: 250.1 msec
Port: 80: 173 KB/sec 5 KB/sec 182 KB/sec 500
Port: 80: 54 KB/sec 2 KB/sec 57 KB/sec 500
Port: 443: 148 KB/sec 3 KB/sec 156 KB/sec 500
Port: 443: 147 KB/sec 4 KB/sec 156 KB/sec 500
Port: 7255: 154 KB/sec 4 KB/sec 162 KB/sec 500
Port: 7255: 154 KB/sec 4 KB/sec 163 KB/sec 500
Port: 7003: 174 KB/sec 4 KB/sec 184 KB/sec 500
Port: 7003: 154 KB/sec 4 KB/sec 162 KB/sec 500
Port: 7202: 47 KB/sec 2 KB/sec 51 KB/sec 500
Port: 7202: 154 KB/sec 4 KB/sec 164 KB/sec 500
Port: 7499: 82 KB/sec 2 KB/sec 86 KB/sec 500
Port: 7499: 164 KB/sec 4 KB/sec 173 KB/sec 500
Port: 80: 128 KB/sec 2 KB/sec 135 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
And finally, a speedtest.net result from my city to the US west coast (Frost Gaming Server)
http://www.speedtest.net/result/3096390212.png
Any thing that you can recommend would be greatly appreciated.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 8 ms 9 ms L100.WASHDC-VFTTP-93.verizon-gni.net [173.66.179
.1]
3 12 ms 9 ms 14 ms G0-12-4-3.WASHDC-LCR-21.verizon-gni.net [130.81.
184.34]
4 15 ms 10 ms 11 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.30]
5 23 ms 24 ms 26 ms 0.ae1.XL3.BOS4.ALTER.NET [140.222.226.13]
6 33 ms 23 ms 23 ms 0.xe-10-2-0.GW15.BOS4.ALTER.NET [152.63.21.138]
7 29 ms 28 ms 28 ms internap-gw.customer.alter.net [152.179.134.214]
8 581 ms 33 ms 25 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
9 92 ms 64 ms 81 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 64 ms 61 ms 62 ms patchserver2.crypticstudios.com [208.95.185.41]
And here's my nettest:
contacting nettest server..
Local IP: 71.163.250.183
Ping: 103.5 msec
Port: 80: 120 KB/sec 5 KB/sec 131 KB/sec 500
Port: 80: 279 KB/sec 10 KB/sec 296 KB/sec 500
Port: 443: 102 KB/sec 4 KB/sec 113 KB/sec 500
Port: 443: 115 KB/sec 6 KB/sec 124 KB/sec 500
Port: 7255: 158 KB/sec 7 KB/sec 168 KB/sec 500
Port: 7255: 498 KB/sec 18 KB/sec 529 KB/sec 500
Port: 7003: 167 KB/sec 9 KB/sec 191 KB/sec 500
Port: 7003: 446 KB/sec 18 KB/sec 474 KB/sec 500
Port: 7202: 203 KB/sec 11 KB/sec 232 KB/sec 500
Port: 7202: 281 KB/sec 13 KB/sec 323 KB/sec 500
Port: 7499: 963 KB/sec 31 KB/sec 1019 KB/sec 500
Port: 7499: 891 KB/sec 28 KB/sec 941 KB/sec 500
Port: 80: 567 KB/sec 19 KB/sec 601 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 0 KB/sec
hit return to exit
My service provider is Verizon and I'm in Northern Virginia. I was on the phone with them earlier and everything is hunky-dory. So... what now?
Do a pathping to 8 581 ms 33 ms 25 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
however the problem is there.
Short 10 sec trailer for Cube 571
The one good thing about being Borg you never need tech-support
Before you post in the STO tech support forum
You should post your Trace Route results in the Networking section of the PWE Tech Support site, so that PWE IT people can do some kicking on their end to try to get this fixed...
http://techsupport.perfectworld.com/
TRACERT:
NETTEST:
I think, according to the tracert result, I should have a good connection. But I still get lag and rubber-banding. I even went as far as uninstalling and reinstalling STO. Still lags after a while.
I can't make heads or tails of it. = /
My service provider, I believe, is Time Warner Cable, and my location is in Madison, Ohio.
Also, I'm using both a hard cable and wifi connection.
View My gallery at http://captricosakara.deviantart.com
Unfortunately, neither Trace Route, nor the Cryptic 'Net Test' utility are good tools for detecting packet drop. And silently dropped packets is most likely the cause of your symptoms.
The Microsoft pathping utility from the command prompt may do a better job at this...
silently dropped packets? what are those, and how do I deal with this problem? How do I use a pathping utility on the prompt?
View My gallery at http://captricosakara.deviantart.com
'pathping' is very much like the 'tracert' utility. you can follow the same instructions as 'tracert', but use 'pathping' instead...
Now there isn't anything you can really do about 'dropped packets' (packets that are lost, or thrown away during transmission...) as this is a ISP issue. But the 'pathping' should be able to show who's to blame for the problem, and if its the Cogent backbone that's causing, you can forward the information to Cryptic/PWE so they can deal with it. If its not Cogent, then you can complain to your ISP to fix it...
But you have to know who's the responsible party is first, before you can do any of this...
Yep Time warner cable
IP address 173.89.160.0
Hostname cpe-173-89-160-0.neo.res.rr.com
Area code (US Only) 440
Metropolitan Area (US Only) Cleveland-Akron (Canton) OH
City Geneva
State/Province OH
Country United States
ISP Time Warner Cable
Organisation Time Warner Cable
Up-to-date? Yes, IP Address information is less than 3 months old.
Tools - Whois information for IP address 173.89.160.0
- Convert 173.89.160.0 to an IPv6 address
Short 10 sec trailer for Cube 571
The one good thing about being Borg you never need tech-support
Before you post in the STO tech support forum
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.1.1
2 59 ms 41 ms 15 ms 76.23.104.1
3 11 ms 10 ms 12 ms te-9-4-ur01.goosecreek.sc.chrlstn.comcast.net [6
8.85.123.13]
4 12 ms 11 ms 11 ms te-7-4-ar02.charleston.sc.chrlstn.comcast.net [6
8.86.144.57]
5 30 ms 46 ms 27 ms 68.87.164.121
6 64 ms 42 ms 42 ms pos-3-15-0-0-cr01.56marietta.ga.ibone.comcast.ne
t [68.86.91.221]
7 * * * Request timed out.
8 85 ms 85 ms 86 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.5
4.10.233]
9 86 ms 85 ms 85 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.
165]
10 108 ms 123 ms 110 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31
.94]
11 109 ms 139 ms 125 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
12 113 ms 117 ms 123 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
13 138 ms 122 ms 120 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 77 ms 85 ms 77 ms 38.111.40.114
15 90 ms 74 ms 74 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 76.23.105.61
Ping: 79.0 msec
Port: 80: 432 KB/sec 14 KB/sec 455 KB/sec 500
Port: 80: 447 KB/sec 15 KB/sec 471 KB/sec 500
Port: 443: 403 KB/sec 13 KB/sec 426 KB/sec 500
Port: 443: 413 KB/sec 14 KB/sec 434 KB/sec 500
Port: 7255: 354 KB/sec 12 KB/sec 371 KB/sec 500
Port: 7255: 330 KB/sec 10 KB/sec 347 KB/sec 500
Port: 7003: 420 KB/sec 11 KB/sec 440 KB/sec 500
Port: 7003: 341 KB/sec 11 KB/sec 359 KB/sec 500
Port: 7202: 361 KB/sec 12 KB/sec 379 KB/sec 500
Port: 7202: 397 KB/sec 13 KB/sec 417 KB/sec 500
Port: 7499: 437 KB/sec 14 KB/sec 459 KB/sec 500
Port: 7499: 368 KB/sec 12 KB/sec 386 KB/sec 500
Port: 80: 493 KB/sec 16 KB/sec 518 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Provider: Telefonica Czech Republic / O2.cz
Internet run perfectly, probl?m is only in STO
V?pis trasy k patchserver.crypticstudios.com [208.95.185.41]
s nejv??e 30 směrov?n?mi:
1 < 1 ms < 1 ms < 1 ms 10.0.0.138
2 18 ms 17 ms 17 ms 88.103.200.71
3 26 ms 26 ms 25 ms 88.103.203.137
4 28 ms 27 ms 27 ms 194.228.190.85
5 26 ms 27 ms 27 ms 194.228.190.193
6 26 ms 26 ms 26 ms 5.53.0.89
7 49 ms 49 ms 49 ms 5.53.7.118
8 174 ms 218 ms 215 ms 213.140.52.210
9 68 ms 65 ms 65 ms te0-7-0-8.mpd21.par01.atlas.cogentco.com [130.117.1.69]
10 65 ms * 68 ms te0-4-0-6.mpd21.lon13.atlas.cogentco.com [154.54.37.157]
11 139 ms 139 ms 139 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
12 * 137 ms * te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
13 144 ms 144 ms 142 ms 38.111.40.114
14 140 ms 139 ms 137 ms patchserver2.crypticstudios.com [208.95.185.41]
Trasov?n? bylo dokončeno. (Trace complete.)
contacting nettest server..
Local IP: 90.179.41.246
Ping: 1000.3 msec
Port: 80: 21 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 20 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 23 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 19 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 16 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 16 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: timed out
Port: 7003: timed out
Port: 7202: timed out
Port: 7202: 18 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 17 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: timed out
Port: 80: 19 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec