Lag?

[RogueGunslinger]

I'll be on around the same time DesertMan is later tonight to test this out. We should be able to shine some perspective on both sides of the fence for you then.

But the more people doing this the better. I've been one of the people lagging during a time like this so I know how utterly frustrating it can be, so if you don't like lag but your aren't experiancing it just this second, doesn't mean it might not be a problem for you later, so help out if you can.

HOW TO RUN A TRACE ROUTE

1) Do a search with windows, type in the letters CMD and hit enter. This should bring up your command prompt instantly.
2) In the command Prompt type: Tracert ginka.armageddon.org

You will get something like this:
Tracing route to ginka.armageddon.org [206.72.201.199]
over a maximum of 30 hops:

 1     2 ms     2 ms     2 ms  192.168.0.1
 2    31 ms    27 ms    28 ms  phnx-dsl-gw69.phnx.qwest.net [67.40.227.69]
 3    48 ms    32 ms    27 ms  phnx-agw1.inet.qwest.net [75.160.238.33]
 4     *        *        *     Request timed out.
 5    43 ms    40 ms    39 ms  63.146.26.150
 6   109 ms   108 ms   106 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
 7   110 ms   104 ms   107 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
 8   113 ms   106 ms   106 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
 9   106 ms   106 ms   106 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10   104 ms   106 ms   105 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   103 ms   104 ms   105 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   105 ms   104 ms   104 ms  207.239.51.86
13   106 ms   107 ms   113 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14   105 ms   104 ms   104 ms  openvz28.interserver.net [199.231.184.130]
15   108 ms   105 ms   105 ms  ginka.armageddon.org [206.72.201.199]



Then copy and paste it like this:

1.Open Command Prompt
2.Right-click the title bar of the command prompt window, point to Edit, and then click Mark.
3.Click the beginning of the text you want to copy.
4.Press and hold down the SHIFT key, and then click the end of the text you want to copy (or you can click and drag the cursor to select the text).
5.Right-click the title bar, point to Edit, and then click Copy.
6.Position the cursor where you want the text to be inserted:
•In an MS-DOS-based program, or in a command prompt window, right-click the title bar, point to Edit, and then click Paste.
•In a Windows-based program, click the Edit menu, and then click Paste.

[Desertman]

Lag started pretty much right at 9pm for regularly scheduled programming. This includes 15 seconds of zero activity at a time for both myself and the wife, not always at the same time though. The GDB was also a cluster fuck. Not other websites showed any signs of lag.

6pm
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     7 ms     9 ms     9 ms  10.31.32.1
 3     8 ms    21 ms     7 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4    10 ms     9 ms     9 ms  74.51.206.241
 5    36 ms     9 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    16 ms    18 ms    17 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    18 ms    18 ms    16 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    14 ms    16 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    17 ms    16 ms    16 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    57 ms    71 ms    58 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    65 ms    59 ms    59 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    63 ms    58 ms    59 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    49 ms    46 ms    51 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    47 ms    50 ms    48 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    58 ms    49 ms    49 ms  207.239.51.86
16    49 ms    60 ms    50 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    48 ms    49 ms    61 ms  openvz28.interserver.net [199.231.184.130]
18    51 ms    52 ms    63 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

8pm

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     7 ms     9 ms    20 ms  10.31.32.1
 3   167 ms   201 ms   162 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     9 ms     9 ms    17 ms  74.51.206.241
 5     9 ms     9 ms     8 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    27 ms    18 ms    15 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    17 ms    19 ms    15 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    17 ms    17 ms    15 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    19 ms    15 ms    17 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    59 ms    59 ms    58 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    56 ms    71 ms    59 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    60 ms    58 ms    70 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    49 ms    49 ms    48 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    50 ms    51 ms    47 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    49 ms    47 ms    50 ms  207.239.51.86
16    58 ms    50 ms    60 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    51 ms    48 ms    48 ms  openvz28.interserver.net [199.231.184.130]
18    50 ms    50 ms    51 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

9pm

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     7 ms     9 ms     9 ms  10.31.32.1
 3     8 ms    21 ms     7 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4    10 ms     9 ms     9 ms  74.51.206.241
 5    36 ms     9 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    16 ms    18 ms    17 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    18 ms    18 ms    16 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    14 ms    16 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    17 ms    16 ms    16 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    57 ms    71 ms    58 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    65 ms    59 ms    59 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    63 ms    58 ms    59 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    49 ms    46 ms    51 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    47 ms    50 ms    48 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    58 ms    49 ms    49 ms  207.239.51.86
16    49 ms    60 ms    50 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    48 ms    49 ms    61 ms  openvz28.interserver.net [199.231.184.130]
18    51 ms    52 ms    63 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.


9pm


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     9 ms     9 ms     8 ms  10.31.32.1
 3     8 ms     9 ms     9 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     8 ms     9 ms     9 ms  74.51.206.241
 5    14 ms     8 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    17 ms    28 ms    17 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    16 ms    25 ms    16 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    17 ms    16 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    17 ms    17 ms    16 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    76 ms    70 ms    70 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    69 ms    70 ms    70 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    79 ms    69 ms    72 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    78 ms    71 ms    70 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    68 ms    69 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    50 ms    51 ms    49 ms  207.239.51.86
16    51 ms    62 ms    52 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    50 ms    49 ms    50 ms  openvz28.interserver.net [199.231.184.130]
18    49 ms    49 ms    49 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

9:10

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     9 ms     9 ms     8 ms  10.31.32.1
 3     8 ms     9 ms     9 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     8 ms     9 ms     9 ms  74.51.206.241
 5    14 ms     8 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    17 ms    28 ms    17 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    16 ms    25 ms    16 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    17 ms    16 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    17 ms    17 ms    16 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    76 ms    70 ms    70 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    69 ms    70 ms    70 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    79 ms    69 ms    72 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    78 ms    71 ms    70 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    68 ms    69 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    50 ms    51 ms    49 ms  207.239.51.86
16    51 ms    62 ms    52 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    50 ms    49 ms    50 ms  openvz28.interserver.net [199.231.184.130]
18    49 ms    49 ms    49 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

9:30

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     9 ms     9 ms     8 ms  10.31.32.1
 3     8 ms     9 ms     9 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     8 ms     9 ms     9 ms  74.51.206.241
 5    14 ms     8 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    17 ms    28 ms    17 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    16 ms    25 ms    16 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    17 ms    16 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    17 ms    17 ms    16 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    76 ms    70 ms    70 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    69 ms    70 ms    70 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    79 ms    69 ms    72 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    78 ms    71 ms    70 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    68 ms    69 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    50 ms    51 ms    49 ms  207.239.51.86
16    51 ms    62 ms    52 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    50 ms    49 ms    50 ms  openvz28.interserver.net [199.231.184.130]
18    49 ms    49 ms    49 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.


9:30

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     8 ms     9 ms     8 ms  10.31.32.1
 3    12 ms     8 ms    10 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     9 ms    11 ms     9 ms  74.51.206.241
 5    16 ms     9 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    33 ms    36 ms    27 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    17 ms    17 ms    17 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    15 ms    19 ms    14 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    20 ms    21 ms    17 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    57 ms    70 ms    59 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    72 ms    68 ms    72 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    70 ms    82 ms    58 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    60 ms    61 ms    61 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    59 ms    59 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    51 ms    51 ms     *     207.239.51.86
16     *        *       51 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17     *       68 ms    53 ms  openvz28.interserver.net [199.231.184.130]
18    50 ms    49 ms    49 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.



The lag seemed to be at its absolute worst between 9pm and 10:30pm.


12:20am  (At this point it is lagging a bit again. Even the GDB is being extremely slow to load.)


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    18 ms    13 ms     9 ms  10.31.32.1
 3     9 ms     8 ms     9 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4     8 ms     9 ms     9 ms  74.51.206.241
 5    13 ms    11 ms    10 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    17 ms    34 ms    20 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    18 ms    19 ms    22 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    17 ms    18 ms    22 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    16 ms    20 ms    18 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    70 ms    60 ms    58 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    62 ms    57 ms    58 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    69 ms    58 ms    60 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    50 ms    49 ms    52 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    48 ms    49 ms    50 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    51 ms    49 ms    48 ms  207.239.51.86
16    50 ms    52 ms    53 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    65 ms    49 ms    66 ms  openvz28.interserver.net [199.231.184.130]
18    48 ms    54 ms    53 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[racurtne]

2:50 AM server time.

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     9 ms     9 ms    11 ms  110.187.228.1
  3    13 ms     9 ms     9 ms  182.129.151.189
  4    18 ms    19 ms    19 ms  171.208.202.149
  5    50 ms    55 ms    51 ms  202.97.35.181
  6    51 ms    52 ms    52 ms  202.97.33.150
  7    52 ms    52 ms    53 ms  202.97.60.70
  8   315 ms   348 ms   315 ms  202.97.51.130
  9   271 ms   289 ms   261 ms  202.97.90.78
10   320 ms   313 ms   312 ms  218.30.54.82
11   294 ms   299 ms   298 ms  207.88.14.225.ptr.us.xo.net [207.88.14.225]
12   390 ms   384 ms   388 ms  te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12
.70]
13   287 ms   287 ms   287 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14   376 ms   378 ms   376 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15   505 ms   511 ms   459 ms  207.239.51.86
16   358 ms   309 ms   313 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17   337 ms   337 ms   338 ms  openvz28.interserver.net [199.231.184.130]
18   367 ms   366 ms   364 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[RogueGunslinger]

Had a little bit of delay trying to connect, about 20 secs.


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

  1     5 ms    15 ms     2 ms  192.168.0.1
  2    30 ms    29 ms    27 ms  phnx-dsl-gw69.phnx.qwest.net [67.40.227.69]
  3    29 ms    28 ms    29 ms  phnx-agw1.inet.qwest.net [75.160.238.33]
  4     *       39 ms    39 ms  los-brdr-01.inet.qwest.net [67.14.102.30]
  5    40 ms    41 ms    38 ms  63.146.26.150
  6   111 ms   106 ms   109 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
  7   119 ms   106 ms   106 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
  8   122 ms   115 ms   118 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
  9   118 ms   105 ms   106 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10   105 ms   107 ms   103 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   103 ms   107 ms   105 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   108 ms   104 ms   105 ms  207.239.51.86
13   109 ms   106 ms   108 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14   104 ms   104 ms   106 ms  openvz28.interserver.net [199.231.184.130]
15   104 ms   111 ms   104 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Lizzie]

raturcne is routing through China, so that's why he's got a delay. Desertman and RGS are routing through a server from XO Communications, which looks like it's having a little trouble but nothing significant.

My hops jump from 47 to 67 at the last AT&T, and stay over 70 through XO. I have DSL, so I don't expect it to be all that fast. For me, anything over 70 would be questionable. The worst mine is, is 83 at the same 207.88 central office that RGS and Desertman are having problems with.

[Desertman]

Been lagging since about 8:30 pm, running smooth all day long before that.

Now it is so bad I want to kill kittens. (10pm central currently.)

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    28 ms    30 ms    31 ms  10.31.32.1
  3     8 ms     8 ms    10 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    35 ms    26 ms    31 ms  74.51.206.241
  5    15 ms    15 ms    13 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
  6    39 ms    45 ms    38 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
  7    20 ms    18 ms    30 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
  8    16 ms    17 ms    23 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
  9    35 ms    25 ms    29 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    73 ms    63 ms    97 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    82 ms    55 ms    60 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12   120 ms   102 ms    75 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    50 ms    50 ms    49 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    49 ms    51 ms    51 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    51 ms    53 ms    52 ms  207.239.51.86
16    93 ms    77 ms    79 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    63 ms    62 ms     *     openvz28.interserver.net [199.231.184.130]
18     *       82 ms    75 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Desertman]

Getting progressively worse. (10:35pm central)

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    11 ms     7 ms    10 ms  10.31.32.1
 3     7 ms    17 ms    36 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
 4    11 ms    10 ms    13 ms  74.51.206.241
 5    10 ms    11 ms    11 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.2
50.202.13]
 6    17 ms    16 ms    20 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.1
76]
 7    19 ms    38 ms    19 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.2
25]
 8    16 ms    15 ms    17 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.1
1]
 9    23 ms    21 ms    18 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.ne
t [129.250.9.158]
10    50 ms    60 ms    58 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    84 ms    78 ms    67 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]

12    61 ms    60 ms    57 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
13    51 ms    51 ms    50 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    54 ms    48 ms    50 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15     *       76 ms     *     207.239.51.86
16     *       52 ms     *     edge-10-teb2.us.as19318.net [66.45.224.182]
17    56 ms     *       59 ms  openvz28.interserver.net [199.231.184.130]
18    62 ms     *       55 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Rahnevyn]

I noticed this for the first time tonight as well. The game wasn't affected for me though, just the request tool.

[slvrmoontiger]

Had a huge spike of lag between 12:30am and 1am server time... MTR showed no latency and no packet loss.

[Desertman]

I have been having lag for probably a week and a half now. My trace didn't show any packet loss or latency until the last few days actually.

Last night was the worst it has been obviously.

[Desertman]

Getting worse and worse earlier and earlier. 7:30pm for me today she starts lagging.

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     *       54 ms    46 ms  10.31.32.1
  3    43 ms    51 ms    34 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    24 ms    24 ms    18 ms  74.51.206.241
  5    10 ms    11 ms    12 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.
50.202.13]
  6    57 ms     *       19 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.
76]
  7    21 ms    23 ms    24 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.
25]
  8    20 ms    36 ms    34 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.
1]
  9    25 ms    26 ms    38 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.n
t [129.250.9.158]
10    85 ms    80 ms    81 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    87 ms    77 ms    70 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1

12    81 ms    92 ms    71 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.
2.10]
13    70 ms    72 ms    73 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    72 ms    67 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    69 ms    65 ms    54 ms  207.239.51.86
16    59 ms    54 ms    63 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    93 ms    84 ms    78 ms  openvz28.interserver.net [199.231.184.130]
18    55 ms    55 ms    56 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

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    52 ms    24 ms    42 ms  10.31.32.1
  3    22 ms    27 ms    23 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    37 ms    39 ms    40 ms  74.51.206.241
  5    45 ms    46 ms    26 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.
50.202.13]
  6    46 ms    50 ms    47 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.
76]
  7    56 ms    49 ms    42 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.
25]
  8    35 ms    34 ms    35 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.
1]
  9    29 ms    35 ms    24 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.n
t [129.250.9.158]
10    76 ms    83 ms    78 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    81 ms    83 ms    88 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1

12    77 ms    92 ms    75 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.
2.10]
13    88 ms    72 ms    88 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14   114 ms   113 ms    96 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15     *       65 ms     *     207.239.51.86
16    62 ms     *       54 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    53 ms    54 ms    52 ms  openvz28.interserver.net [199.231.184.130]
18    54 ms    54 ms    58 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Nyr]

Anyone else?

[Lizzie]

  1     4 ms     4 ms     4 ms  10.0.0.1
 2     4 ms     4 ms     4 ms  (my computer)
 3    46 ms    45 ms    45 ms  adsl-blah blah att.net
 4    46 ms    44 ms    45 ms  204.60.1.65
 5    47 ms    47 ms    47 ms  12.83.32.254
 6    97 ms    97 ms    98 ms  gar13.cgcil.ip.att.net [12.122.132.121]
 7    73 ms     *       68 ms  206.111.2.89.ptr.us.xo.net [206.111.2.89]
 8    79 ms    83 ms    83 ms  207.88.14.201.ptr.us.xo.net [207.88.14.201]
 9    75 ms    76 ms    75 ms  ae0d0.mcr1.nyc-ny.us.xo.net [216.156.0.18]
10    76 ms    76 ms    76 ms  207.239.51.86
11    76 ms    76 ms    75 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
12    77 ms    76 ms    76 ms  openvz28.interserver.net [199.231.184.130]
13    77 ms    76 ms    76 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

So mine starts before it hits the xo.net central offices. Since I'm on ADSL though, that change in ms is just a tiny blip of delay in the game. My times are pretty much the same no matter where I go on the internet

[RogueGunslinger]

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

  1     1 ms     3 ms     2 ms  192.168.0.1
  2    27 ms    39 ms    30 ms  phnx-dsl-gw69.phnx.qwest.net [67.40.227.69]
  3    27 ms    26 ms    65 ms  phnx-agw1.inet.qwest.net [75.160.238.33]
  4    39 ms    37 ms    43 ms  los-brdr-01.inet.qwest.net [67.14.102.30]
  5    62 ms    59 ms    61 ms  63.146.26.150
  6   135 ms   128 ms   130 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
  7   134 ms   130 ms   128 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
  8   131 ms   130 ms   138 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
  9   131 ms   130 ms   131 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10   126 ms   129 ms   124 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   125 ms   126 ms   125 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   106 ms   105 ms   108 ms  207.239.51.86
13   109 ms   106 ms   105 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14   103 ms   103 ms   103 ms  openvz28.interserver.net [199.231.184.130]
15   104 ms   105 ms   105 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[slvrmoontiger]

Getting worse and worse earlier and earlier. 7:30pm for me today she starts lagging.

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     *       54 ms    46 ms  10.31.32.1
  3    43 ms    51 ms    34 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    24 ms    24 ms    18 ms  74.51.206.241
  5    10 ms    11 ms    12 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.
50.202.13]
  6    57 ms     *       19 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.
76]
  7    21 ms    23 ms    24 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.
25]
  8    20 ms    36 ms    34 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.
1]
  9    25 ms    26 ms    38 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.n
t [129.250.9.158]
10    85 ms    80 ms    81 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    87 ms    77 ms    70 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1

12    81 ms    92 ms    71 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.
2.10]
13    70 ms    72 ms    73 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14    72 ms    67 ms    68 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15    69 ms    65 ms    54 ms  207.239.51.86
16    59 ms    54 ms    63 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    93 ms    84 ms    78 ms  openvz28.interserver.net [199.231.184.130]
18    55 ms    55 ms    56 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

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    52 ms    24 ms    42 ms  10.31.32.1
  3    22 ms    27 ms    23 ms  ip-173-45-192-1.wavevision.com [173.45.192.1]
  4    37 ms    39 ms    40 ms  74.51.206.241
  5    45 ms    46 ms    26 ms  xe-0-0-0-3.r05.hstntx01.us.bb.gin.ntt.net [129.
50.202.13]
  6    46 ms    50 ms    47 ms  ae-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.
76]
  7    56 ms    49 ms    42 ms  ae-9.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.
25]
  8    35 ms    34 ms    35 ms  ae-1.r01.dllstx04.us.bb.gin.ntt.net [129.250.2.
1]
  9    29 ms    35 ms    24 ms  ae-0.xo-communications.dllstx04.us.bb.gin.ntt.n
t [129.250.9.158]
10    76 ms    83 ms    78 ms  207.88.14.242.ptr.us.xo.net [207.88.14.242]
11    81 ms    83 ms    88 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1

12    77 ms    92 ms    75 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.
2.10]
13    88 ms    72 ms    88 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14   114 ms   113 ms    96 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15     *       65 ms     *     207.239.51.86
16    62 ms     *       54 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17    53 ms    54 ms    52 ms  openvz28.interserver.net [199.231.184.130]
18    54 ms    54 ms    58 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

I'm a bit confused as to why your first hop is ginka.armageddon.org. Could you explain please?

[Desertman]

Is it not supposed to be?

All I do is open my command prompt and type "tracert www.armageddon.org"......the machine does the rest.

[RogueGunslinger]

... Desertman... IS GINKA

[slvrmoontiger]

Is it not supposed to be?

All I do is open my command prompt and type "tracert www.armageddon.org"......the machine does the rest.

No, you should see your routers private IP as the first hop... This is typically a 192.168.x.x address, but could also be a couple others. The it looks your router is set up with the private IP Address of ginka. Which isn't right. Send me a PM if you'd like me to work with you more on finding out what's going on. I think there might be something messed up on your internal network that could be causing problems and its not really something we'll want the whole community to see all the going back and forth. If you PM me I'll give you my AIM so we can chat live time and try to get to the bottom of this. Something is very very wrong if your first hop is showing that as the IP.

[RogueGunslinger]

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


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

 1     2 ms     2 ms     1 ms  192.168.0.1
 2    30 ms    27 ms    27 ms  phnx-dsl-gw69.phnx.qwest.net [67.40.227.69]
 3    38 ms    27 ms    27 ms  phnx-agw1.inet.qwest.net [75.160.238.33]
 4    38 ms    40 ms    46 ms  los-brdr-01.inet.qwest.net [67.14.102.30]
 5    39 ms    38 ms    38 ms  63.146.26.150
 6   127 ms   132 ms   128 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
 7   135 ms   131 ms   129 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
 8   129 ms   130 ms   132 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1

 9   142 ms   130 ms   130 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.
2.10]
10   131 ms   124 ms   127 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   127 ms   122 ms   123 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   104 ms   105 ms   105 ms  207.239.51.86
13   106 ms   106 ms   106 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14   104 ms   103 ms   104 ms  openvz28.interserver.net [199.231.184.130]
15   110 ms   105 ms   105 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

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


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

 1     2 ms     1 ms     1 ms  192.168.0.1
 2    32 ms    28 ms    27 ms  phnx-dsl-gw69.phnx.qwest.net [67.40.227.69]
 3    27 ms    33 ms    27 ms  phnx-agw1.inet.qwest.net [75.160.238.33]
 4     *        *       45 ms  los-brdr-01.inet.qwest.net [67.14.102.30]
 5    57 ms    57 ms    61 ms  63.146.26.150
 6   129 ms   147 ms   131 ms  207.88.14.217.ptr.us.xo.net [207.88.14.217]
 7   134 ms   131 ms   135 ms  vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
 8   188 ms   139 ms   132 ms  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
 9   132 ms   185 ms   128 ms  te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10   122 ms   124 ms   149 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   124 ms   126 ms   133 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   139 ms   130 ms   137 ms  207.239.51.86
13   105 ms   109 ms   108 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14   112 ms   104 ms   103 ms  openvz28.interserver.net [199.231.184.130]
15   104 ms   113 ms   104 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[FantasyWriter]

I haven't been able to log in in a couple days.
Most of the time can't even get the mantis head to load.
I have my ISP looking at the problem on this end, but they are all morons, damn small town monopolies.


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

  1     1 ms    <1 ms     1 ms  10.10.10.1
  2   256 ms   279 ms   309 ms  mlx4.fultontelephone.net [66.211.112.1]
  3   246 ms   301 ms   237 ms  12.119.41.21
  4   282 ms   269 ms   279 ms  cr2.nsvtn.ip.att.net [12.122.148.134]
  5   310 ms   351 ms   286 ms  cr1.nsvtn.ip.att.net [12.122.148.45]
  6   299 ms   310 ms   330 ms  cr2.attga.ip.att.net [12.122.28.105]
  7   309 ms   335 ms   349 ms  attga04jt.ip.att.net [12.122.84.149]
  8   149 ms   141 ms   128 ms  67.111.23.89.ptr.us.xo.net [67.111.23.89]
  9    73 ms    82 ms    82 ms  vb2002.rar3.washington-dc.us.xo.net [207.88.13.1
62]
10   321 ms   336 ms   317 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11   209 ms   147 ms    70 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   204 ms   185 ms   211 ms  207.239.51.86
13   180 ms   225 ms   212 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
14     *      252 ms   234 ms  openvz28.interserver.net [199.231.184.130]
15     *      281 ms   339 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Desertman]

For reference my traces every single night are basically the same. I stopped posting them. I can keep going if you want me to, but it is basically the same data repeatedly, just starting earlier in the night and worse.

[slvrmoontiger]

Just out of curiosity what does a traceroute to www.google.com show for you DMan?

[Nyr]

For reference we still only have two people that have mentioned having problems during this time/providing any statistics as data points.  That's not really helping make the case that lots of people are having problems, so I'll have to look somewhere else to get information.

An analysis of "reconnection" messages shows that there are more reconnections during peak times than any other time of the day.  However, that increase in reconnections matches up with the increase in the amount of players that we have online during this time, plus we can't correlate all "reconnections" as "this" problem.  For instance, I'm one of those people.  I disconnected and reconnected because my laptop battery died and it's a piece of crap.  Staff members can generally be excluded anyway since they stay logged in and often just disconnect rather than quit out.

The only things I see as noteworthy is that of the people reporting here, two of them reconnect a lot during the times they are logged in.  That would be:

Desertman
racurtne

That holds true for the last several login sessions; racurtne has it way worse off than Desertman.  There are other people that reconnect regularly during the same time periods, but they also reconnect at other times (leading me to think they have issues in general with staying connected).

Still not seeing something that can be held up as the reason for your problem, nor am I seeing anything pointing to a specific problem yet.

[racurtne]

I'll post a couple of more. After checking a few American websites, most have issues with speed in spikes.Arm is much the same. Sometimes it's smooth and then suddenly nothing moves...if it takes around a minute, I generally just disconnect and reconnect. Usually this works, at least for a second or two. Sometimes it appears to fix the problem for a longer duration . This is a random sample. I'm not on Arm. When I get on again, I'll post another the moment I experience issues.

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

  1     3 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    17 ms    10 ms  110.187.228.1
  3    11 ms   14 ms     9 ms  182.129.151.189
  4    20 ms    19 ms    19 ms  171.208.202.149
  5    55 ms    55 ms    62 ms  202.97.35.181
  6    54 ms    52 ms    59 ms  202.97.34.182
  7    72 ms    67 ms    77 ms  202.97.61.218
  8   223 ms   225 ms   226 ms  202.97.51.134
  9   272 ms   276 ms   278 ms  202.97.50.74
10   337 ms   334 ms   332 ms  218.30.54.10
11   302 ms   299 ms   298 ms  207.88.14.225.ptr.us.xo.net [207.88.14.225]
12   312 ms   315 ms   321 ms  te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12
.70]
13   352 ms   335 ms   326 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
14   303 ms   308 ms   305 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
15   331 ms   344 ms   346 ms  207.239.51.86
16     *      308 ms   284 ms  edge-10-teb2.us.as19318.net [66.45.224.182]
17   347 ms   368 ms   359 ms  openvz28.interserver.net [199.231.184.130]
18   337 ms   339 ms   338 ms  ginka.armageddon.org [206.72.201.199]

Trace complete.

[Desertman]

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.