Fight the Lag! - with metrics

[Jeshin]

Having a lag / timeout connection at 2:22 pm EST

What she said below me!

[Janna]

What Jeshin said, only at 2:22pm EST with the clocks ahead.

[Jeshin]

After Wedi's post and Nyr's reply this is the official. Unbearable lag thread. Whenever encountered with what you consider to be game affecting lag or an unintentional DC please include the following

1) PST/EST/GMT of the event or just say at the time of posting
2) IG time - early morning etc etc
3) On a scale of 1-10 how bad the lag is. 1 being one or two seconds sporadically, 5 being several seconds over a long peiod, and 10 being a full disconnect [not by the server].

We can fight lag, with data!

[hyzhenhok]

Started around or before 5:20 AM EST. Problem persists; it's 6:00 AM now and still going.
It was Dawn or Early Morning when it started. Dusk at the time of this post, and the lag continues.
On a scale of 1-10: 9. 5+ minutes to return output from commands, though no disconnect.

[Cind]

Output from commands has just gotten noticeably faster but its nothing to rp with. about a forty seconds to ninety to get commands returned, maybe?

Edit: Its like 6:14 now.

[Nyr]

Does anyone have any actual metrics like traceroutes or ping results that back this up?  That would be helpful!

[Barsook]

traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1  unknown (192.168.1.1)  1.983 ms  1.976 ms  2.399 ms
2  10.169.64.1 (10.169.64.1)  17.962 ms  18.006 ms  18.313 ms
3  ae0-1030.cr02.dytnoh55.swo.rr.com (184.59.244.114)  22.261 ms  22.241 ms  22.632 ms
4  ae1.tr00.clevohek.mwrtn.rr.com (65.189.140.130)  29.997 ms  30.047 ms ae0.tr00.clevohek.mwrtn.rr.com (65.189.140.144)  30.451 ms
5  ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70)  43.516 ms 107.14.19.58 (107.14.19.58)  42.123 ms ae10-0.cr0.dca20.tbone.rr.com (107.14.19.14)  38.221 ms
6  107.14.19.135 (107.14.19.135)  38.842 ms  31.607 ms  31.194 ms
7  3-3.r1.dc.hwng.net (69.16.190.113)  59.513 ms  36.204 ms  36.217 ms
8  e1-4.r1.ny.hwng.net (209.197.0.34)  53.645 ms e4-2.r1.ny.hwng.net (209.197.0.42)  36.201 ms e1-4.r1.ny.hwng.net (209.197.0.34)  53.886 ms
9  209.197.17.198 (209.197.17.198)  54.185 ms  53.841 ms  54.538 ms
10  edge-12-teb1.us.as19318.net (64.20.32.78)  54.916 ms  36.775 ms  54.873 ms
11  openvz17.interserver.net (206.72.207.130)  54.048 ms  40.750 ms  40.652 ms
12  206.72.207.140 (206.72.207.140)  41.135 ms !X  41.513 ms !X  57.433 ms !X

What does !X stand for for traceroute on Linux?

[Namino]

Uh, I'm going to go out on a limb (and talk out my ass) and assume it's the same as an asterisks on DOS.

Packet loss.

[Nyr]

traceroute to 206.72.207.140 (206.72.207.140), 30 hops max, 60 byte packets
1  unknown (192.168.1.1)  1.983 ms  1.976 ms  2.399 ms
2  10.169.64.1 (10.169.64.1)  17.962 ms  18.006 ms  18.313 ms
3  ae0-1030.cr02.dytnoh55.swo.rr.com (184.59.244.114)  22.261 ms  22.241 ms  22.632 ms
4  ae1.tr00.clevohek.mwrtn.rr.com (65.189.140.130)  29.997 ms  30.047 ms ae0.tr00.clevohek.mwrtn.rr.com (65.189.140.144)  30.451 ms
5  ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70)  43.516 ms 107.14.19.58 (107.14.19.58)  42.123 ms ae10-0.cr0.dca20.tbone.rr.com (107.14.19.14)  38.221 ms
6  107.14.19.135 (107.14.19.135)  38.842 ms  31.607 ms  31.194 ms
7  3-3.r1.dc.hwng.net (69.16.190.113)  59.513 ms  36.204 ms  36.217 ms
8  e1-4.r1.ny.hwng.net (209.197.0.34)  53.645 ms e4-2.r1.ny.hwng.net (209.197.0.42)  36.201 ms e1-4.r1.ny.hwng.net (209.197.0.34)  53.886 ms
9  209.197.17.198 (209.197.17.198)  54.185 ms  53.841 ms  54.538 ms
10  edge-12-teb1.us.as19318.net (64.20.32.78)  54.916 ms  36.775 ms  54.873 ms
11  openvz17.interserver.net (206.72.207.130)  54.048 ms  40.750 ms  40.652 ms
12  206.72.207.140 (206.72.207.140)  41.135 ms !X  41.513 ms !X  57.433 ms !X

What does !X stand for for traceroute on Linux?

but it's not lagging now I assume?

[Namino]

It's fine now, and my tracert looks normal.

[Barsook]

It's fine.

[Nyr]

I checked back to the times folks were posting in this thread this morning.  There was definitely some strange stuff going on, but it is above my head.  We will let you know once we have more information.

[Namino]

There was definitely some strange stuff going on

[Morgenes]

Please continue to post here when you notice it, and use the 'traceroute ginka.armageddon.org' command with it so that we can verify if it is a network problem.

[Potaje]

My roommate says there is a big lag going on right now, 8:45 pst.


Tracing route to 206.72.207.140 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    39 ms    39 ms    39 ms  ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
  3    39 ms    39 ms    39 ms  ptld-agw1.inet.qwest.net [207.225.86.89]
  4    43 ms    43 ms    43 ms  sea-brdr-02.inet.qwest.net [67.14.41.18]
  5    44 ms    44 ms    44 ms  63.146.26.82
  6    44 ms    44 ms    45 ms  xe-0-0-0.mpr2.sea1.us.above.net [64.125.31.10]
  7    98 ms    98 ms    98 ms  xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
  8   121 ms   121 ms   122 ms  xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
  9   120 ms   121 ms   128 ms  xe-0-0-1.er2.lga5.us.above.net [64.125.27.65]
10   121 ms   121 ms   121 ms  64.124.44.213.interserver.com [64.124.44.213]
11   122 ms   121 ms   121 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
12   121 ms   123 ms   123 ms  openvz17.interserver.net [206.72.207.130]
13   121 ms   121 ms   122 ms  206.72.207.140

Trace complete.

[Nyr]

I've been actively chatting on the game port with another staffer.  Haven't seen any lag here.  Can you be more specific?  Big lag?  What happened?  How long?

[Dakota]

I've been actively chatting on the game port with another staffer.  Haven't seen any lag here.  Can you be more specific?  Big lag?  What happened?  How long?

Has happened 2 times over the last few days.

Game runs fine. Then at around 11am GMT +1, it slows to a crawl. Slow meaning.. You can look. But can't do actions (unless you want for about 30+ seconds). Disconnect from the game. Try to reconnect. Mud prompt says "connected" then hangs before the entry screen of arm shows up. Hangs for.. minutes usually before you get in.

This lasts for about 1-2 hours it seems.

[Potaje]

I log in and it seems from my end its evened out, he said that about an hour ago he was lagging between 1 min and two.

[Nyr]

To clarify, I didn't mean in general, I was responding to Potaje's post referring to lag just now.

When it happens again please have the other person do the ping/tracert, since it didn't seem to show anything when you did it.

[Potaje]

To clarify, I didn't mean in general, I was responding to Potaje's post referring to lag just now.

When it happens again please have the other person do the ping/tracert, since it didn't seem to show anything when you did it.

Will do, thank you.

[RogueGunslinger]

Getting lag spikes. Probably my internet even though my traceroute seems fine. Because the forums got a lag spike too.


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Rogue Gunslinger>tracert armageddon.org

Tracing route to armageddon.org [206.72.207.140]
over a maximum of 30 hops:

 1     1 ms     2 ms     2 ms  192.168.0.1
 2    42 ms    43 ms    42 ms  phnx-dsl-gw66.phnx.qwest.net [67.40.227.66]
 3    43 ms    42 ms    44 ms  phnx-agw1.inet.qwest.net [75.160.238.9]
 4    54 ms    54 ms    55 ms  lap-brdr-03.inet.qwest.net [67.14.22.78]
 5    54 ms    55 ms    54 ms  xe-0-1-0.mpr1.lax12.us.above.net [64.125.12.25]

 6    82 ms    54 ms    57 ms  xe-3-0-0.cr2.lax112.us.above.net [64.125.30.29]

 7    82 ms    82 ms    81 ms  xe-2-3-0.cr2.iah1.us.above.net [64.125.25.17]
 8   138 ms   122 ms   114 ms  xe-3-1-0.cr2.dca2.us.above.net [64.125.30.54]
 9   116 ms   115 ms   116 ms  xe-2-2-0.cr2.lga5.us.above.net [64.125.26.106]
10   115 ms   115 ms   115 ms  xe-0-2-1.er2.lga5.us.above.net [64.125.30.210]
11   115 ms   116 ms   115 ms  64.124.44.213.interserver.com [64.124.44.213]
12   116 ms   116 ms   116 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
13   116 ms   116 ms   116 ms  openvz17.interserver.net [206.72.207.130]
14   116 ms   116 ms   116 ms  206.72.207.140

[JustAnotherGuy]

I've been getting some too, but didn't get any tracerts.

[Potaje]

hitting some lag spikes.


Tracing route to 206.72.207.140 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    39 ms    39 ms    39 ms  ptld-dsl-gw44-236.ptld.qwest.net [207.225.84.236
]
  3    39 ms    40 ms    39 ms  ptld-agw1.inet.qwest.net [207.225.86.89]
  4    42 ms    77 ms    43 ms  sea-brdr-02.inet.qwest.net [67.14.41.18]
  5    43 ms    43 ms    43 ms  63.146.26.82
  6    44 ms    44 ms    44 ms  xe-1-0-0.mpr2.sea1.us.above.net [64.125.31.14]
  7    98 ms    98 ms    98 ms  xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
  8   120 ms   121 ms   121 ms  xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
  9   121 ms   120 ms   120 ms  xe-0-0-1.er2.lga5.us.above.net [64.125.27.65]
10   317 ms   125 ms   189 ms  64.124.44.213.interserver.com [64.124.44.213]
11   122 ms   121 ms   120 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
12   122 ms   122 ms   122 ms  openvz17.interserver.net [206.72.207.130]
13   121 ms   121 ms   122 ms  206.72.207.140

Trace complete.

[titansfan]

Its just horrid right now. I can't even reconnect.

[Namino]

Same:

 1     5 ms     5 ms     7 ms  192.168.1.1
 2     8 ms    11 ms    11 ms  10.123.32.1
 3    13 ms    11 ms    12 ms  ten0-1-0-7.orld14-ser2.bhn.net [72.31.194.40]
 4    20 ms    23 ms    22 ms  ten0-11-0-4.orld71-car2.bhn.net [97.69.193.190]
 5    18 ms    16 ms    15 ms  hun0-7-0-0.orld71-cbr3.bhn.net [72.31.193.24]
 6    23 ms    35 ms    24 ms  ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
 7    39 ms    39 ms    48 ms  107.14.19.36
 8    42 ms    47 ms    55 ms  ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
 9    68 ms    39 ms    48 ms  107.14.19.133
10    38 ms    44 ms    37 ms  3-3.r1.dc.hwng.net [69.16.190.113]
11    61 ms    68 ms    64 ms  e1-4.r1.ny.hwng.net [209.197.0.34]
12    61 ms    60 ms    73 ms  209.197.17.198
13    72 ms    79 ms    59 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
14    68 ms    66 ms    70 ms  openvz17.interserver.net [206.72.207.130]
15    67 ms    60 ms    58 ms  206.72.207.140

Trace complete.


Looks like uh... nothing's wrong with the trace. Gremlins in the pipes somewhere deeper, me thinks.

Edit: On the plus side, now we can all figure out what cities we all live in based on our traces. Whee.