Lag?

[RogueGunslinger]

Well shit, I guess I don't have any option but to wait until whatever changed two weeks ago changes back...or something. Thanks for taking a look anyways.

Well if the thread is any indication, most of these problem aren't actually fixed, only a couple times. They do tend to eventually go away on their own after a couple weeks.

Guess I'll stop tracerouting every time I see multiple people in-game have lag at the same time, it's apparently useless information. Glad it's not me getting issues this time around, I'd be flipping out at the amount of times Nyr's said there doesn't seem to be a problem.

[Nyr]

Guess I'll stop tracerouting every time I see multiple people in-game have lag at the same time, it's apparently useless information.

Your anecdotal data about multiple people in-game having lag at the same time isn't that useful if it isn't accompanied by said people also presenting traceroute information or any other indication about their problem.  I already went over this before, we need more people involved than just two or three people vocal enough to mention anything about it.

Even when I go back and look at your data you're artificially inflating it.

First time I've been able to get on around this time this week. Not lagging myself but noticing some others are as usual.

At approximately this time in game, one person around you mentioned lag and you put this traceroute up.  Not some others, one person.

Edit: 10:00 PM Server some others were getting lag in game:

Correction, two other people were getting lag in game that actually mentioned it around you at this time.  One was on the same IP as the previous person that had an issue, the other was at a different IP/different ISP.

Glad it's not me getting issues this time around, I'd be flipping out at the amount of times Nyr's said there doesn't seem to be a problem.

Getting data is key to troubleshooting.  There's a limit to how much we can assess without information.  Did I say there doesn't seem to be a problem?  No, I said there doesn't seem to be something pointing to the cause of Desertman's (or these other players that haven't mentioned anything) problem.  There aren't enough data points to find out commonalities or differences between Desertman (having issues) and others.  Racurtne has a different issue.  FantasyWriter has a different issue.

One thing I can think of is to eliminate the ISP as a root cause, if possible, but that's difficult to do.  Simpler might be eliminating the home connection as the root cause...though that's still a pain in the ass.

[RogueGunslinger]

Eh, you're right. I'm just still bitter over the last time this happened to me.

[Desertman]

Well, since it appears to be only me, does anyone have any recommendations for anything I can do to try and cure the issue?

I am not going to pretend I have any clue about what is happening. I just know it started two weeks ago, didn't exist before then, and seems to start at 7PM central time, but does not exist in any fashion before that time. It also only exists when interacting with www.armageddon.org (to include the game directly and the GDB). No other website or game I visit during this time is affected in any way.

That is what I know.

Oh, it also affects my wife. We play from the same IP, obviously. Strangely enough when I am lagging she isn't always lagging and sometimes when she is lagging, I'm not lagging. She will freeze for twenty seconds, and I will be running fine, and sometimes she is running fine and I am freezing for twenty seconds at a time. Sometimes we both freeze at the same time. I'm not sure if that means anything.

Any help is appreciated.

[Nyr]

Do you ever play from anywhere but your house during those times you experience lag?

[Desertman]

Do you ever play from anywhere but your house during those times you experience lag?

No but I can try that probably if you think it would provide useful info.

[Nyr]

Do you ever play from anywhere but your house during those times you experience lag?

No but I can try that probably if you think it would provide useful info.

If you were able to do so, it would provide some relevant information.

If the problem goes away, it is likely something isolated to your internet service at home (whether that be your ISP, your router, or modem).
If the problem persists, traceroutes will tell us how your packets are trying to get to ginka and back.

Ideally we'd get some traceroutes from anyone else that is persistently having this problem (not your wife, though--sorry, she's great and all, but you're at the same place).

[Desertman]

Do you ever play from anywhere but your house during those times you experience lag?

No but I can try that probably if you think it would provide useful info.

If you were able to do so, it would provide some relevant information.

If the problem goes away, it is likely something isolated to your internet service at home (whether that be your ISP, your router, or modem).
If the problem persists, traceroutes will tell us how your packets are trying to get to ginka and back.

Ideally we'd get some traceroutes from anyone else that is persistently having this problem (not your wife, though--sorry, she's great and all, but you're at the same place).

I'm on it.

[Nyr]

I was looking at this earlier but did not have time to post about it. The only other clear thing to note is that your provider sends your traffic through NTT to get to XO. If this is more widespread than you then I would make the assumption that the NTT to XO link is shit at that time...for anyone else making that hop.

[racurtne]

I have some new info. I caught it while it was lagging. The first bit is when the gdb wasn't loading properly. During the second, it was a little better.

C:\Users\Rush>Tracert ginka.armageddon.org

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

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    10 ms    10 ms     9 ms  110.187.228.1
 3    14 ms    18 ms     9 ms  182.129.151.185
 4    21 ms    19 ms    22 ms  171.208.202.77
 5    51 ms    56 ms    51 ms  202.97.43.153
 6     *       51 ms    50 ms  202.97.34.114
 7    53 ms    51 ms    52 ms  202.97.60.197
 8   225 ms   227 ms   227 ms  202.97.58.218
 9   204 ms   206 ms   208 ms  202.97.90.134
10   216 ms   216 ms   215 ms  206.111.14.113
11   309 ms   298 ms   299 ms  207.88.13.82.ptr.us.xo.net [207.88.13.82]
12   279 ms   281 ms   279 ms  207.88.12.85
13   288 ms   285 ms   287 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14   283 ms   287 ms   287 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

15   287 ms   287 ms   287 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   295 ms   302 ms   305 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   323 ms   322 ms   319 ms  207.239.51.86
18   283 ms   274 ms   274 ms  66.45.224.182
19   312 ms   311 ms     *     199.231.184.130
20   284 ms   285 ms   284 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

C:\Users\Rush>Tracert ginka.armageddon.org

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

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    12 ms    16 ms     9 ms  110.187.228.1
 3    13 ms    10 ms    11 ms  182.129.151.185
 4    31 ms    23 ms    22 ms  171.208.202.77
 5    54 ms    56 ms    52 ms  202.97.43.153
 6    50 ms    67 ms    51 ms  202.97.34.114
 7    51 ms    51 ms    55 ms  202.97.60.197
 8   224 ms   226 ms   226 ms  202.97.58.218
 9   208 ms   207 ms   206 ms  202.97.90.134
10   268 ms   216 ms   216 ms  206.111.14.113.ptr.us.xo.net [206.111.14.113]
11   309 ms   299 ms   298 ms  207.88.13.82.ptr.us.xo.net [207.88.13.82]
12   310 ms   278 ms   278 ms  te0-5-4-0.rar3.denver-co.us.xo.net [207.88.12.85
]
13   284 ms   292 ms   283 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14   289 ms   287 ms   287 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

15   289 ms   290 ms   288 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   292 ms   291 ms   291 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   286 ms   287 ms   285 ms  207.239.51.86
18   274 ms   274 ms   274 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
19   283 ms   280 ms   279 ms  199.231.184.130
20   287 ms   291 ms   311 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

It's just me being in China, isn't it?

[racurtne]

Okay, as I was trying to post I was initially unable to post, so I ran another immediately.
C:\Users\Rush>Tracert ginka.armageddon.org

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

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    10 ms     9 ms    17 ms  110.187.228.1
 3    10 ms     9 ms    81 ms  182.129.151.185
 4    21 ms    19 ms    19 ms  171.208.202.77
 5    52 ms    55 ms    51 ms  202.97.43.153
 6    50 ms    50 ms    50 ms  202.97.34.114
 7    50 ms    52 ms    51 ms  202.97.60.197
 8   228 ms   230 ms   223 ms  202.97.58.218
 9   206 ms   206 ms   205 ms  202.97.90.134
10   216 ms   216 ms   216 ms  206.111.14.113.ptr.us.xo.net [206.111.14.113]
11   333 ms   312 ms   310 ms  207.88.13.82.ptr.us.xo.net [207.88.13.82]
12   278 ms   282 ms   288 ms  te0-5-4-0.rar3.denver-co.us.xo.net [207.88.12.85
]
13   280 ms   287 ms   289 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14   281 ms   287 ms   288 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

15   288 ms   287 ms   287 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   291 ms   290 ms   291 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   286 ms   286 ms   286 ms  207.239.51.86
18   278 ms   274 ms   274 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
19   295 ms   285 ms   283 ms  openvz28.interserver.net [199.231.184.130]
20   281 ms   281 ms   284 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

C:\Users\Rush>Tracert ginka.armageddon.org

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

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    11 ms     9 ms    12 ms  110.187.228.1
 3    10 ms     9 ms    10 ms  182.129.151.185
 4    22 ms    20 ms    18 ms  171.208.202.77
 5    52 ms    55 ms    55 ms  202.97.43.153
 6    50 ms    50 ms    50 ms  202.97.34.114
 7    52 ms    51 ms    52 ms  202.97.60.197
 8   223 ms   228 ms   230 ms  202.97.58.218
 9   208 ms   208 ms   206 ms  202.97.90.134
10   216 ms   218 ms   216 ms  206.111.14.113.ptr.us.xo.net [206.111.14.113]
11   309 ms   298 ms   299 ms  207.88.13.82.ptr.us.xo.net [207.88.13.82]
12   282 ms   282 ms   279 ms  te0-5-4-0.rar3.denver-co.us.xo.net [207.88.12.85
]
13   282 ms   283 ms   287 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14   281 ms   286 ms   316 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

15   288 ms   287 ms   287 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   293 ms   291 ms   291 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   320 ms   321 ms   321 ms  207.239.51.86
18   299 ms   309 ms   311 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
19   310 ms   305 ms     *     openvz28.interserver.net [199.231.184.130]
20   319 ms   317 ms   285 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

  1     2 ms     1 ms     1 ms  192.168.1.1
  2    12 ms    11 ms    10 ms  110.187.228.1
  3    43 ms    10 ms    10 ms  182.129.151.185
  4    19 ms    18 ms    21 ms  171.208.202.77
  5    52 ms    54 ms    52 ms  202.97.43.153
  6    50 ms    57 ms    50 ms  202.97.34.114
  7    60 ms    51 ms    51 ms  202.97.60.197
  8   226 ms   224 ms   227 ms  202.97.58.218
  9   206 ms   206 ms   206 ms  202.97.90.134
10   216 ms   216 ms   231 ms  206.111.14.113.ptr.us.xo.net [206.111.14.113]
11   310 ms   298 ms   306 ms  207.88.13.82.ptr.us.xo.net [207.88.13.82]
12   283 ms   278 ms   279 ms  te0-5-4-0.rar3.denver-co.us.xo.net [207.88.12.85
]
13   289 ms   284 ms   286 ms  te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14   284 ms   303 ms   283 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

15   287 ms   289 ms   288 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
16   290 ms   293 ms   291 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
17   299 ms   299 ms   292 ms  207.239.51.86
18     *      301 ms   279 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
19   277 ms   277 ms   277 ms  openvz28.interserver.net [199.231.184.130]
20     *      281 ms   284 ms  ginka.armageddon.org [206.72.201.199]


I'll stop posting these for now unless I hit something interesting, but at least I managed to catch it during the problem.

[Lizzie]

I don't know if it's "because, China" but that is where the trouble begins - at the China 202.97 servers.

[racurtne]

I like to imagine my internet going through Great Firewall security and being needlessly hassled.

[Desertman]

Picked up a new modem from the ISP, just incase that might improve the situation.

If there's one thing I like, it's consistency. 8:30PM right on time.

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

  1    <1 ms    <1 ms    <1 ms  ginka.armageddon.org [206.72.201.199]
  2    13 ms    16 ms    24 ms  10.31.32.1
  3    27 ms     8 ms    15 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    17 ms    12 ms    13 ms  74.51.206.241
  5     9 ms    12 ms     9 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
  6    19 ms    17 ms    16 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
  7    24 ms    40 ms    28 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
  8    50 ms    40 ms    37 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
  9     *       69 ms    68 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    99 ms   104 ms    95 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11   100 ms    95 ms   105 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12   108 ms   108 ms     *     te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13   152 ms   108 ms    90 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    91 ms    86 ms   100 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    79 ms    79 ms     *     207.239.51.86
16    88 ms    67 ms    79 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    77 ms    89 ms    69 ms  openvz28.interserver.net [199.231.184.130]
18    79 ms    75 ms     *     ginka.armageddon.org [206.72.201.199]
19    67 ms     *       82 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[slvrmoontiger]

I still don't get why your first hop is ginka.

[FantasyWriter]

His wife is the living incarnation of Ginka.
Oh shit, was that suppose to be a secret?

[Barsook]

Just got D/Ced.

[RogueGunslinger]

Yeah, I think we all did.

[Lizzie]

Armageddon last booted 5 minutes and 12 seconds ago.

Okay don't everyone rush to the NPC merchants now! 

[slvrmoontiger]

Armageddon last booted 5 minutes and 12 seconds ago.

Okay don't everyone rush to the NPC merchants now! 

Thanks for letting everyone know so that they do.

[RogueGunslinger]

Armageddon last booted 5 minutes and 12 seconds ago.

Okay don't everyone rush to the NPC merchants now! 

Thanks for letting everyone know so that they do.

Trust me on this. They already knew.

[slvrmoontiger]

Armageddon last booted 5 minutes and 12 seconds ago.

Okay don't everyone rush to the NPC merchants now! 

Thanks for letting everyone know so that they do.

Trust me on this. They already knew.

Oh I know they did I was just teasing.

[Fujikoma]

I've been getting an awful slowing in the text received for like, a day or two now, anyone else?

[RogueGunslinger]

I've notice a couple very brief pieces of lag that could have very well just been my connection.

[FantasyWriter]

I can watch netflix but not play arm... wtf?