Ensign
Join Date: Jun 2012
Posts: 2
# 481
10-27-2013, 04:12 PM
Same problem the last 3 days or so.

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 28 ms 24 ms 25 ms albq-dsl-gw48.albq.qwest.net [67.42.200.48]
3 103 ms 128 ms 123 ms albq-agw1.inet.qwest.net [71.222.249.121]
4 48 ms 48 ms 59 ms lap-brdr-04.inet.qwest.net [67.14.22.158]
5 76 ms 79 ms 82 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.54.11.125]
6 86 ms 88 ms 90 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
7 116 ms 112 ms 116 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.157]
8 128 ms 124 ms 138 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 125 ms 131 ms 134 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
10 100 ms 102 ms 101 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 107 ms 105 ms 107 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
12 183 ms 104 ms 105 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
13 112 ms 107 ms 107 ms 38.111.40.114
14 105 ms 111 ms 114 ms 208.95.185.41

Trace complete.

contacting nettest server..
Local IP: 97.119.165.10
Ping: 103.5 msec
Port: 80: 321 KB/sec 13 KB/sec 348 KB/sec 500
Port: 80: 307 KB/sec 11 KB/sec 327 KB/sec 500
Port: 443: 334 KB/sec 13 KB/sec 356 KB/sec 500
Port: 443: 322 KB/sec 12 KB/sec 343 KB/sec 500
Port: 7255: 283 KB/sec 11 KB/sec 303 KB/sec 500
Port: 7255: 282 KB/sec 13 KB/sec 318 KB/sec 500
Port: 7003: 296 KB/sec 12 KB/sec 323 KB/sec 500
Port: 7003: 304 KB/sec 12 KB/sec 331 KB/sec 500
Port: 7202: 338 KB/sec 12 KB/sec 357 KB/sec 500
Port: 7202: 555 KB/sec 21 KB/sec 588 KB/sec 500
Port: 7499: 283 KB/sec 13 KB/sec 320 KB/sec 500
Port: 7499: 336 KB/sec 12 KB/sec 355 KB/sec 500
Port: 80: 255 KB/sec 11 KB/sec 282 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
Career Officer
Join Date: Jun 2012
Posts: 2,064
# 482
10-27-2013, 05:17 PM
Quote:
Originally Posted by xanderaab View Post
Same problem the last 3 days or so.

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 28 ms 24 ms 25 ms albq-dsl-gw48.albq.qwest.net [67.42.200.48]
3 103 ms 128 ms 123 ms albq-agw1.inet.qwest.net [71.222.249.121]

4 48 ms 48 ms 59 ms lap-brdr-04.inet.qwest.net [67.14.22.158]
5 76 ms 79 ms 82 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.54.11.125]
6 86 ms 88 ms 90 ms be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
7 116 ms 112 ms 116 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.157]
8 128 ms 124 ms 138 ms be2172.ccr21.atl01.atlas.cogentco.com [154.54.29.17]
9 125 ms 131 ms 134 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
10 100 ms 102 ms 101 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 107 ms 105 ms 107 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
12 183 ms 104 ms 105 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
13 112 ms 107 ms 107 ms 38.111.40.114
14 105 ms 111 ms 114 ms 208.95.185.41

Trace complete.
...
Now this looks highly suspicious, as their are no good reasons, (and lots of bad reasons, such as local network congestion...) why there is a sudden jump in latency, which looks to be a regional hub for your ISP.

Looks like you will have to contact Qwest Tech support, and ask them to diagnose your connection issues with the STO servers...

You should also post your diagnostic results in the network section of the PWE Tech Support site, as it looks like the Cogent Boston hub may be acting up again...
http://techsupport.perfectworld.com/

Last edited by grouchyotaku; 10-27-2013 at 05:19 PM.
Lieutenant
Join Date: Feb 2013
Posts: 78
# 483
10-29-2013, 10:08 AM
Hey all

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
Quote:
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.
nettest
Quote:
contacting nettest server..
Local IP: 142.162.21.198
Ping: 69.8 msec
Port: 80: 200 KB/sec 7 KB/sec 212 KB/sec 500
Port: 80: 314 KB/sec 13 KB/sec 332 KB/sec 500
Port: 443: 325 KB/sec 14 KB/sec 345 KB/sec 500
Port: 443: 307 KB/sec 13 KB/sec 325 KB/sec 500
Port: 7255: 326 KB/sec 14 KB/sec 346 KB/sec 500
Port: 7255: 318 KB/sec 13 KB/sec 336 KB/sec 500
Port: 7003: 327 KB/sec 14 KB/sec 346 KB/sec 500
Port: 7003: 237 KB/sec 10 KB/sec 252 KB/sec 500
Port: 7202: 314 KB/sec 13 KB/sec 332 KB/sec 500
Port: 7202: 327 KB/sec 14 KB/sec 346 KB/sec 500
Port: 7499: 325 KB/sec 14 KB/sec 345 KB/sec 500
Port: 7499: 307 KB/sec 13 KB/sec 325 KB/sec 500
Port: 80: 225 KB/sec 10 KB/sec 239 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
Thanks
Career Officer
Join Date: Jun 2012
Posts: 2,064
# 484
10-29-2013, 12:32 PM
Quote:
Originally Posted by j0hn41 View Post
Hey all

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/
Lieutenant
Join Date: Feb 2013
Posts: 78
# 485
10-29-2013, 02:28 PM
Thanks for the diagnosis
John
Republic Veteran
Join Date: Jun 2012
Posts: 688
# 486
10-30-2013, 01:49 PM
Quote:
Originally Posted by j0hn41 View Post
Hey all

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.
Ensign
Join Date: Jun 2013
Posts: 12
# 487
10-31-2013, 09:07 PM
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.
Republic Veteran
Join Date: Jun 2012
Posts: 131
# 488
11-01-2013, 12:27 AM
I'm on Time Warner Cable:

Quote:
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.
Republic Veteran
Join Date: Jun 2012
Posts: 688
# 489
11-01-2013, 08:47 AM
Yep, it is cogentco acting up. john started a thread about it over at PWE's Network support, should post there as well

http://techsupport.perfectworld.com/...ad.php?t=38071
Ensign
Join Date: Sep 2012
Posts: 1
# 490
11-01-2013, 10:01 AM
Same ISP, also in Nova Scotia, with the exact same issue. Hope the issue gets resolved soon.
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 05:00 AM.