Lag, loading, clipping, errors, and more fun

[Raist]

yeah.. you get the same thing I do when hopping across the pond---just before it gets to pac-net, response time shoots up briefly, then settles back down. Been seeing it do that for ages. What's probably more important is the route to the Canadian servers. Seems to be where more people are running into issues, the last hops before it gets to Ormuco's segments.

could run a netstat while you are in XIV. Look for IP's in the subnet 199.91.18x.xxx for the Canadian servers (should get hits for Ormuco if you lookup the IP) and 124.150.15x.xxx for SE. Should be one of each with the same IP consistently opened or in wait state when in game. Try traces to them to see if you spot anything wonky there. Throttling shouldn't show up with a simple trace or ping--but if you see one give *'s before the final hops, then there may well be something going on that you'll need your ISP to look into for you. Even so, forward the results of the trace if they've been putting forth an effort to resolve this for you. If you are able to provide them the correct IP as well as the route you are taking , they might be willing to look into it further for the throttling and such--just need to give them the right places to look.

Oh, in case you didn't know, while in the DOS box, you can get at an Edit menu by clicking the black/white C:\ icon in the upper-left corner to select all the text and copy it to clipboard for putting it in an email and such. You can drag and highlight text and just hit <Enter> too, but I find I sometimes miss stuff because of the way the text wraps and all... so usually just select all text from the menu and then edit out what I don't need.

Here's a sample to kind of show why I bring up the third party segments (I hit cogentco, and it goes to crap):

C:\Windows\System32>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

<initial hops from local segment removed>

4 32 ms 25 ms 32 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.
64.42]
5 31 ms 34 ms 30 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.10
9.6.82]
6 37 ms 30 ms 46 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 79 ms 79 ms 91 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.5
4.12.109]
8 79 ms 80 ms 81 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40
.249]
9 89 ms 91 ms 90 ms te0-5-0-7.mpd21.dca01.atlas.cogentco.com [154.54
.25.253]
10 96 ms 97 ms 114 ms te0-7-0-14.mpd21.jfk02.atlas.cogentco.com [154.5
4.41.22]
11 111 ms 114 ms 112 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.
134]
12 49 ms 49 ms 49 ms 38.122.42.34
13 52 ms 53 ms 53 ms 10.2.2.1
14 52 ms 49 ms 95 ms 192.34.76.2
15 61 ms 51 ms 52 ms 199.91.189.234
16 62 ms 52 ms 59 ms 199.91.189.74

Trace complete.

Granted, my response times are still "good" in general... it's just frustrating to see how crappy it gets in that section after I leave Atlanta (compared to the rest--even the ones at the end up in Canada respond better).