Fight the Lag! - with metrics

[musashi]

Doing my part.

Code Select Expand

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

  1  1240 ms  1587 ms     1 ms  buffalo.setup [192.168.11.1]
  2  1273 ms    16 ms    16 ms  220.220.253.6
  3  3455 ms    31 ms    22 ms  220.220.253.1
  4  1851 ms  2064 ms   942 ms  118.21.174.145
  5    98 ms   718 ms   913 ms  i118-21-178-3.s99.a049.ap.plala.or.jp [118.21.17
8.3]
  6   549 ms   779 ms   352 ms  218.43.251.129
  7  1092 ms  1004 ms  1484 ms  118.23.146.49
  8  1415 ms  1056 ms    49 ms  60.37.27.155
  9   167 ms    15 ms     7 ms  ae-11.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.12
.201]
10   618 ms   123 ms   132 ms  as-2.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.4
4]
11   206 ms   126 ms   306 ms  equinixexchange.ir1.sanjose-ca.us.xo.net [206.22
3.116.85]
12   330 ms   130 ms   327 ms  207.88.14.225.ptr.us.xo.net [207.88.14.225]
13   191 ms   460 ms   225 ms  te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12
.70]
14  1074 ms  2256 ms  2423 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
15  1392 ms  3030 ms  1925 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
16  1368 ms   185 ms     *     207.239.51.86
17  1626 ms  2131 ms   889 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
18  1371 ms   187 ms   204 ms  openvz17.interserver.net [206.72.207.130]
19   676 ms   199 ms  1708 ms  206.72.207.140

Trace complete.

[ShaLeah]

Someone IM me when it's back to decent.

* ShaLeah grumbles drunkenly!

[Gunnerblaster]

Maaaan. This shit's still down? I've been patiently biding my time until the weekend/my day off to ARM it up and I can't even connect.

This blows.

[Old Kank]

I wonder if it would be possible to give everyone 'quit anywhere' privileges until the nightly lag passes.

[adrift]

I don't think the game has ever been down this long since the weekly maintenance days...

[Barsook]

I don't think the game has ever been down this long since the weekly maintenance days...

Yeah, this is like the first time.

[greasygemo]

I makes me sad that my time zone / schedule permits me to play almost exclusively during this time of night..

How do I get these stats everyone is posting so I can help too?

[Barsook]

For Linux, you type in traceroute 206.72.207.140 in term

You may need to do apt-get traceroute first.

Actually, I think it's the same for all OS's.

[X-D]

Quote from: adrift on Today at 07:31:52 PM
I don't think the game has ever been down this long since the weekly maintenance days...

Yeah, this is like the first time.

Untrue, we have had such since then...hell, I'm pretty sure, more then once it was a bad router.

But, since we are not hosted on ginka anymore...who knows what it is.

[Barsook]

Quote from: adrift on Today at 07:31:52 PM
I don't think the game has ever been down this long since the weekly maintenance days...

Yeah, this is like the first time.

Untrue, we have had such since then...hell, I'm pretty sure, more then once it was a bad router.

But, since we are not hosted on ginka anymore...who knows what it is.

Oh duh, was this before they moved the sever (that time).

[tiptoe]

Is it safe to assume that we'll be logged out eventually? I really can't wait any longer and I'm fairly certain my PC would die if I just continued to be where I happen to be.

[The Lonely Hunter]

Yeah, my main play time is during our downtime now. Sucks. Hopefully after the weekend the issue will be resolved. It seems to be machine lag and always at the same time which would lead me to believe they are running backups, scans, or using the machine for more than just hosting Arm.

"HostingCompany offers 30 day money back guarantee on shared hosting, 99.5% uptime guarantee, 100% power guarantee, fast and easy setups, easy to use control panel choices, and much more. Come see why thousands have used HostingCompany to make their website happy!"

(Real name withheld so people don't take it upon themselves to contact the host)

99.5%?

[greasygemo]

For Linux, you type in traceroute 206.72.207.140 in term

You may need to do apt-get traceroute first.

Actually, I think it's the same for all OS's.

..I use the flash applet. Is there anything I can use in that?

[Rhyden]

If you're using Windows XP, 2000 or Me click start, run, type in cmd then type tracert ginka.armageddon.org

If you're using Windows 7, easiest way is to search cmd                  ""               ""                ""

[drunkendwarf]

Sat Jun 16 22:12:45 MDT 2012

traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1  192.168.1.1 (192.168.1.1)  4.478 ms  2.055 ms  2.037 ms
2  76.120.80.1 (76.120.80.1)  48.160 ms  77.977 ms  156.180 ms
3  te-7-4-ur03.arvada.co.denver.comcast.net (68.86.129.225)  15.814 ms  27.234 ms  36.869 ms
4  te-0-6-0-6-ar02.denver.co.denver.comcast.net (68.86.179.57)  24.627 ms  18.552 ms  41.481 ms
5  pos-0-1-0-0-ar02.aurora.co.denver.comcast.net (68.86.128.242)  22.149 ms  58.862 ms  29.968 ms
6  pos-3-6-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.1)  20.031 ms  43.872 ms  27.772 ms
7  pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54)  36.261 ms  54.984 ms  39.526 ms
8  pos-0-4-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.87.218)  43.204 ms  37.529 ms  58.746 ms
9  xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185)  81.835 ms  32.821 ms  51.518 ms
10  xe-3-2-0.cr1.dfw2.us.above.net (64.125.30.86)  37.233 ms  53.105 ms  33.080 ms
11  xe-1-0-0.cr2.dfw2.us.above.net (64.125.30.78)  38.260 ms  42.745 ms  54.553 ms
12  xe-4-2-0.cr2.iah1.us.above.net (64.125.31.122)  58.635 ms  39.319 ms  62.957 ms
13  xe-5-0-0.cr2.dca2.us.above.net (64.125.31.250)  67.558 ms  67.572 ms *
14  xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110)  88.141 ms  69.889 ms  66.916 ms
15  xe-0-0-1.er2.lga5.us.above.net (64.125.27.65)  66.645 ms  67.008 ms  66.667 ms
16  64.124.44.213.interserver.com (64.124.44.213)  67.503 ms  66.478 ms  94.987 ms
17  edge-12-teb1.us.as19318.net (64.20.32.78)  97.830 ms  89.496 ms  67.252 ms
18  openvz17.interserver.net (206.72.207.130)  91.836 ms  74.706 ms  70.479 ms
19  206.72.207.140 (206.72.207.140)  75.273 ms !Z  69.168 ms !Z  93.683 ms !Z

[greasygemo]

...and on a mac?

[drunkendwarf]

...and on a mac?

On a mac, open up Applications -> Utilities -> Terminal
At the prompt, type 'traceroute ginka.armageddon.org 4050'

[The Lonely Hunter]

I think that at this point it has been pretty well established that it isn't a hop to the hosting company but the box we are running on.

[greasygemo]

Code Select Expand

traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1  192.168.2.1 (192.168.2.1)  3.579 ms  2.775 ms  2.900 ms
2  142.166.182.7 (142.166.182.7)  48.119 ms  47.467 ms  91.296 ms
3  irb-84.dr02.fctn.nb.aliant.net (142.166.211.17)  90.903 ms  47.400 ms  91.888 ms
4  xe-0-0-0.cr02.stjh.nb.aliant.net (142.166.185.145)  99.737 ms  48.507 ms  91.755 ms
5  xe-1-0-0.bx01.mtrl.pq.aliant.net (207.231.227.58)  103.579 ms  61.537 ms  92.802 ms
6  xe-7-2-0.bx01.toro.on.aliant.net (207.231.227.66)  101.310 ms  67.330 ms
    xe-7-2-1.bx01.toro.on.aliant.net (207.231.227.70)  92.217 ms
7  xe-1-1-0.bx01.chcg.il.aliant.net (207.231.227.101)  85.101 ms
    xe-0-1-0.bx01.chcg.il.aliant.net (207.231.227.97)  91.979 ms
    xe-1-1-0.bx01.chcg.il.aliant.net (207.231.227.101)  85.268 ms
8  eqx-ch.3-2.r1.ch.hwng.net (206.223.119.96)  97.227 ms  87.831 ms  97.439 ms
9  e1-4.r1.ny.hwng.net (209.197.0.34)  94.067 ms  88.452 ms  97.432 ms
10  209.197.17.198 (209.197.17.198)  90.066 ms  86.908 ms  91.652 ms
11  edge-12-teb1.us.as19318.net (64.20.32.78)  92.319 ms  88.101 ms  101.978 ms
12  openvz17.interserver.net (206.72.207.130)  155.233 ms  150.888 ms  158.425 ms
13  206.72.207.140 (206.72.207.140)  151.670 ms !Z  171.689 ms !Z  152.212 ms !Z

Even so... here is my two-cents

[Case]

Why are people posting traces for

Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum

[Eurynomos]

Like Morgenes said, it's Father's Day weekend. Relax, get a beer, invite a friend over. Watch Rome on HBO Go. Read a book. We'll fix the problem. Maybe. If you're good.

[drunkendwarf]

Why are people posting traces for

Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum

In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that can fix it...and the more information you present those people with, the better.

Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."

[Barsook]

Why are people posting traces for

Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum

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!

[Case]

Why are people posting traces for

Arm doesn't own their own box so all infrastructure involved is not fixable by anybody reading this forum

In the past, when lag issues surfaced, it has been requested by the staff. While it may not be fixable by anyone reading this forum, there are staffers on this forum that can take the information to people that can fix it...and the more information you present those people with, the better.

Presenting these people with full traces from 10+ different origins certainly can't hurt, and may be infinitely more useful than "Shit's runnin' slow."

Hosting company should be sorting that out because it's their job. Back when Ginka was a PC in somebody's house that made more sense.

[greasygemo]

Seems to be running smoother now.
12:48 EST