Recent lag spikes (Feb. 2011)

[Gart]

I was in the DH party,and I just experienced the lag.
IP address:69.22.186.133

[Tsavong]

I to have been getting lag

Here you go Mining

CMD tracert ns4.nsrealm.com

Tracing route to ns4.nsrealm.com [209.221.47.250]
over a maximum of 30 hops:

1 66 ms 99 ms 99 ms api.home [192.168.1.254]
2 31 ms 31 ms 31 ms esr17.kingston6.broadband.bt.net [217.47.159.140
]
3 32 ms 31 ms 32 ms 217.47.159.125
4 105 ms 33 ms 46 ms 213.1.69.50
5 36 ms 35 ms 33 ms 217.32.24.54
6 34 ms 33 ms 34 ms 217.32.24.182
7 52 ms 35 ms 34 ms acc2-10GigE-0-0-0-6.l-far.21cn-ipp.bt.net [109.1
59.249.218]
8 37 ms 34 ms 35 ms core2-te0-4-0-6.ealing.ukcore.bt.net [109.159.24
9.131]
9 37 ms 35 ms 35 ms core1-xe11-1-0.redbus.ukcore.bt.net [62.6.200.93
]
10 37 ms 35 ms 37 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.2
24.21]
11 104 ms 104 ms 112 ms 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92
.241]
12 113 ms 110 ms 113 ms 10gigabitethernet2-3.core1.ash1.he.net [72.52.92
.86]
13 126 ms 126 ms 126 ms 10gigabitethernet1-2.core1.atl1.he.net [184.105.
213.110]
14 122 ms 122 ms 121 ms uscarrier.com [198.32.132.21]
15 129 ms 128 ms 128 ms 209.221.47.250
16 133 ms 128 ms 131 ms 209.221.47.250
17 129 ms 129 ms 127 ms 209.221.47.250

Trace complete.

[mining]

Myself:

Tracing route to ns4.nsrealm.com [209.221.47.250]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms NB [192.168.2.1]
2 * * * Request timed out.
3 37 ms 38 ms 36 ms lo5000.bras2.adl1.adnap.net.au [122.49.191.6]
4 37 ms 36 ms 36 ms g3-23.cor1.adl1.adnap.net.au [219.90.143.141]
5 37 ms 218 ms 232 ms te4-1.cor2.adl1.adnap.net.au [219.90.143.246]
6 36 ms 36 ms 36 ms te1-3.cor2.adl4.adnap.net.au [219.90.143.242]
7 36 ms 36 ms 36 ms vlan369.55drc76fg.optus.net.au [59.154.0.49]
8 222 ms 221 ms 222 ms 203.208.192.241
9 221 ms 222 ms 225 ms POS3-6.sngtp-ar2.ix.singtel.com [203.208.182.213
]
10 229 ms 223 ms 225 ms paix.he.net [198.32.176.20]
11 232 ms 225 ms 224 ms 10gigabitethernet1-1.core1.lax1.he.net [72.52.92
.22]
12 236 ms 242 ms 235 ms 10gigabitethernet1-1.core1.phx1.he.net [72.52.92
.250]
13 262 ms 259 ms 265 ms 10gigabitethernet1-3.core1.dal1.he.net [72.52.92
.254]
14 279 ms 278 ms 278 ms 10gigabitethernet5-4.core1.atl1.he.net [184.105.
213.114]
15 * * * Request timed out.
16 275 ms 275 ms 275 ms 209.221.47.250
17 277 ms 277 ms 276 ms 209.221.47.250
18 276 ms 277 ms 275 ms 209.221.47.250

[cely]

How many people were in the Dwarf Home party today?

[Zaranthys Rivermoon]

My turn too (Windows XP):

C:\DOCUME~1\UTILIS~1>tracert ns4.nsrealm.com

Détermination de l'itinéraire vers ns4.nsrealm.com [209.221.47.250]
avec un maximum de 30 sauts/jumps :

1 1 ms <1 ms 1 ms mymodem [house ISP]
2 9 ms 11 ms 9 ms bas7-sherbrooke40_lo0_SYMP.net.bell.ca [ISP]
3 9 ms 9 ms 9 ms dis7-sherbrooke40_10G5-2_100.net.bell.ca [ISP]
4 23 ms 21 ms 21 ms bx6-newyork83_xe2-0-0.net.bell.ca [ISP]
5 18 ms 19 ms 19 ms core1.nyc4.he.net [ISP]
6 29 ms 31 ms 29 ms 10gigabitethernet2-3.core1.ash1.he.net [72.52.92.86]
7 44 ms 50 ms 47 ms 10gigabitethernet1-2.core1.atl1.he.net [184.105.213.110]
8 * * * Délai d'attente de la demande dépassé (timed out request).
9 42 ms 43 ms 43 ms 209.221.47.250
10 * 43 ms 45 ms 209.221.47.250
11 43 ms 41 ms 45 ms 209.221.47.250

Itinéraire déterminé (path determined).

[cely]

In order to determine if the lag folks are experiencing is network related or server related, we need ALL of the information requested. Folks thus far have only been providing a bare minimum of information which has not been helpful in narrowing down the source of the lag. So to reiterate what we need:

For all of those experiencing unusual lag lasting more than 30 seconds, please send a pm to me with the following information:

1) The exact time you experienced the lag (please include your timezone or use UTC)
2) Approximately how long the lag lasted.
3) Your external IP address.
4) A traceroute to ns4.nsrealm.com.

NOTE: It's VERY important that you perform the traceroute AS THE LAG IS HAPPENING. So practice now so you'll know how to do it when the lag hits.

I want to emphasize that last note. You MUST perform the traceroute AS THE LAG IS HAPPENING. That means exit or switch out of the game and do it right away. If you wait until "one last mob is dead" then perform the traceroute, the data you captured will be completely useless.

With everyone's participation in providing accurate, timely, and complete information, we should be able to identify and eliminate the source of the lag.

Thanks!

[mining]

Anybody? Yes? No? We didn't take the blind fighting feat - we need to have some indication of what we're trying to beat down on.

[frogofpeace]

9:27 edt til i logged at 9:30 (tho it seemed to be there for about 20 minutes before that as well)

IP:65.190.43.202

Tracing route to ns4.nsrealm.com [209.221.47.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1958 ms 390 ms 99 ms cpe-065-190-040-001.nc.res.rr.com [65.190.40.1]

3 12 ms 11 ms 12 ms 66.26.45.237
4 22 ms 11 ms 30 ms ge-2-3-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.164]
5 19 ms 25 ms 19 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 20 ms 18 ms 18 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 20 ms 62 ms 19 ms ash-bb1-link.telia.net [213.248.89.193]
8 42 ms 31 ms 31 ms atl-bb1-link.telia.net [80.91.246.77]
9 34 ms 31 ms 52 ms us-carrier-109356-atl-bb1.c.telia.net [213.248.9
0.30]
10 33 ms 31 ms 31 ms 209.221.47.250
11 32 ms 34 ms 31 ms 209.221.47.250
12 34 ms 31 ms 31 ms 209.221.47.250

Trace complete.

[Blystos Re]

They named their core router T-Bone?

[cely]

Frogofpeace, thank you for the comprehensive information. I took a look at our internal cpu/memory graphs as well as latency and packet loss graphs from my house to ns4.nsrealm.com for that time period. That data compared with your data leads me to believe that the lag people are experiencing is not network related.

The staff is going to start looking into possible causes on the server itself. Hyk's original post from Feb 18th said that lag has been noticeable for "the last couple of weeks". Does everyone agree with that assessment? If so, we'll start looking to see if anything changed on the server at the beginning of February.

Thanks!

[frogofpeace]

Last couple of weeks seems about right. I don't know what any of the data means, but for what it's worth, I'm using a wireless router and the little wireless symbol down in the corner says my connection has been goofy (varies from 1mbp to 54, usually at 48 or 36) - I figured my lag was due to that.

They named their core router T-Bone?

It's not a t-bone. It's a perfect George.

[Tru3Fals3]

my lag is constant, everytime i log in, connection otherwise is running at full speed in all my tests, its just nwn.

about every 1-3 mins i get 5-10second rubber bands, often 2-3 in row, makes it barely playable, especially trying to pvp.

my isp is australias aapt.

[Tru3Fals3]

ive been back for about a month and its been goin on the whole time since then

[dethonlegs]

isp is australias aapt.

AFAIK Optus bought out AAPT, so it wouldn't surprise me that they are experiencing the same issues that Optus customers are having. Filters get applied at 6pm Sydney time and things crawl after that.

[mining]

Hrmm, haven't been having lag. Adam Internet. Australians - tell us your ISPs!