Server lag/packet loss?

Go to http://acmectf.com for more info and file downloads!

[WORM]

I have heard a few complaints of server lag/packet loss lately. Although I appreciate being told of a problem that happened hours ago/last-night/the-other-day there is more needed than just saying you had a problem.

Let me ask this of you guys...again. 

Please help me to help you...do the following for me when there are problems and we have something to work with:

1) If running R1Q2, type "lag" in console and write down the info it gives you.

2) Drop your connection to the game for a few minutes and do the following two items:

   A) Run a tracert to the server. You can do this in command prompt or download R1CH's GUI tracert
       program,  http://www.r1ch.net/stuff/ftrace/wftrace.exe Save to a text file for me.

   B) Run a ping summary. Use the command prompt and type "ping  -n 100 208.43.95.250" It will return
    something like this:

    Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 47ms, Average = 45ms
   
   Copy the results to a text file also.

3) Note the date, time (including timezone you are in) and your IP then email the above files to me, along with   any other info you think may help.

This way I will have documentation to present to SoftLayer.

I have run the above checks and so far haven't seen any problem...at the times I ran them. No doubt there are some problems at times but it's extremely hard to nail it down with them being intermittent and no test data to show.

Thanks in advance for your help!

[angry]

I realize this isn't e-mail, but I logged the data in question earlier tonight.

This is right when I connected.



Disconnected, ran a traceroute:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 12/31/2011 4:59:40 PM to 12/31/2011 5:00:19 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1     8   0  0.0   0   1   0  [192.168.1.1]
 2     8   0  0.0  23 130  36  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3     8   0  0.0  23  25  23  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4     8   0  0.0  25  96  34  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5     8   0  0.0  25  27  25  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6     8   0  0.0  25  26  25  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7     8   0  0.0  25  26  25  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8     8   0  0.0  25  57  31  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9     8   0  0.0  26  54  35  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10     8   2 25.0  60  61  60  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11     8   0  0.0  59  61  59  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12     8   0  0.0  85 118  99  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13     8   0  0.0  96 102  97  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14     8   0  0.0  95 102  97  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15     8   0  0.0  95  98  96  po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16     8   0  0.0  95 107  98  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17     8   0  0.0  95 101  97  acmegamers.com [208.43.95.250]

This was at 5:00 PM Pacific (8 PM EST), 31 December.

[angry]

Logged more data. This was after the lag had stopped.

Again, right when I first connected:



Disconnected, ran another traceroute:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 12/31/2011 9:39:11 PM

 1    1 ms  N/A       0 ms  N/A       0 ms  [192.168.1.1]
 2   24 ms  N/A      25 ms  N/A      24 ms  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3   24 ms  N/A      25 ms  N/A      25 ms  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4   27 ms  N/A      79 ms  N/A      26 ms  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5   26 ms  N/A      27 ms  N/A      26 ms  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6   26 ms  N/A      26 ms  N/A      26 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7   26 ms  N/A      28 ms  N/A      26 ms  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8   26 ms  N/A      27 ms  N/A      27 ms  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9   27 ms  N/A      27 ms  N/A      28 ms  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10   62 ms  N/A      61 ms  N/A      62 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11   95 ms  N/A      60 ms  N/A      71 ms  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12   86 ms  N/A      86 ms  N/A      85 ms  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13   98 ms  N/A      98 ms  N/A      97 ms  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14   98 ms  N/A      98 ms  N/A      96 ms  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15   95 ms  N/A      97 ms  N/A      97 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16   95 ms  N/A      95 ms  N/A      95 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17   97 ms  N/A      98 ms  N/A      98 ms  acmegamers.com [208.43.95.250]

Ping statistics for www.acmectf.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 97ms, Maximum = 98ms, Average = 97ms

This was at 9:39 PM Pacific, 31 December (1 January, 12:39 AM EST).

[spec]

Tracert and ping sended by pm

Netgraph:

http://imageshack.us/photo/my-images/844/quake117.png/

[WORM]

Nodody runs a ping summary? 100 ping? Please do so when you are experiencing the worst problems. Along with a tracert, thes two items are utmost importance.

Netgraph doesn't help me. Yes, it shows you have lag..but we already knew that. 

Is there a pattern to when the problems occur? Checks I run during day don't show any problems at all. Is it same time at night? Same duration?

SoftLayer has been having load balancer issues in WDC, I have asked them to check us out but they do need some data.

Thanks, I appreciate it.

[WORM]

Softlayer, and myself, have performed tests today on our server and the network. No issues were found.

I have asked them to monitor traffic for us tonight and they have agreed to do so. We have scheduled this for 1/1/12 between the hours of 8:00 - 11:00 PM EST. Stay with the server tonight and let's get a report from them.

Thanks!

[Bones]

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:
This was run about 10pm

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     8 ms    17 ms  gig5-2-21.ardlme04-rtr001.ne.northeast.rr.com [24.31.155.110]
  4    17 ms    11 ms    12 ms  g10-4-1-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.246]
  5    20 ms    17 ms    17 ms  rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
  6    36 ms    27 ms    27 ms  ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
  7    32 ms     *       27 ms  ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
  8    28 ms    26 ms    32 ms  66.109.11.126
  9    28 ms    26 ms    27 ms  ae7.bbr01.tl01.nyc01.networklayer.com [173.192.18.176]
 10    33 ms    33 ms    33 ms  ae1.bbr01.eq01.wdc02.networklayer.com [173.192.18.156]
 11    38 ms    47 ms    35 ms  ae0.dar01.sr01.wdc01.networklayer.com [173.192.18.197]
 12    33 ms    33 ms    37 ms  po1.fcr01.sr01.wdc01.networklayer.com [208.43.118.134]
 13    35 ms    33 ms    34 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
 14    33 ms    37 ms     *     acmegamers.com [208.43.95.250]
 15    34 ms    34 ms    33 ms  acmegamers.com [208.43.95.250]

Trace complete.


Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:

the 1% loss was done while right after i bailed out of game to run the test. I was phone jacked like every 2 to 5 seconds. From what i was told, it did that for almost half the map.

[NQK Ramirez]

Usually happens when a map load and not all the time.  Then it can go on for more then 5 minutes into the map.  Where you can move a little then freeze, move a little then freeze over and over again.

[angry]

Nodody runs a ping summary? 100 ping? Please do so when you are experiencing the worst problems. Along with a tracert, thes two items are utmost importance.

Fuck, I misread your original post. I thought it said run traceroute OR ping, not that it said to do both.

My bad, boss.


Just ran this:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 1/1/2012 8:27:24 PM to 1/1/2012 8:27:51 PM

 1    1 ms  N/A       0 ms  N/A       0 ms  N/A       0 ms  N/A       0 ms  [192.168.1.1]
 2   23 ms  N/A      23 ms  N/A      23 ms  N/A      24 ms  N/A      23 ms  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3   23 ms  N/A      23 ms  N/A      23 ms  N/A      24 ms  N/A      24 ms  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4  101 ms  N/A      25 ms  N/A     110 ms  N/A      25 ms  N/A      26 ms  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5   71 ms  N/A      83 ms  N/A      75 ms  N/A      70 ms  N/A      72 ms  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6   78 ms  N/A      76 ms  N/A      79 ms  N/A      82 ms  N/A      73 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7   54 ms  N/A      61 ms  N/A      59 ms  N/A      62 ms  N/A      59 ms  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8   27 ms  N/A      26 ms  N/A      26 ms  N/A      26 ms  N/A      26 ms  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9   70 ms  N/A      26 ms  N/A      28 ms  N/A      26 ms  N/A      47 ms  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10  N/A     N/A      60 ms  N/A      *      N/A      *      N/A      60 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11   59 ms  N/A      59 ms  N/A      59 ms  N/A      60 ms  N/A      66 ms  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12  123 ms  N/A     137 ms  N/A     113 ms  N/A     114 ms  N/A     113 ms  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13  109 ms  N/A     104 ms  N/A     108 ms  N/A     109 ms  N/A     104 ms  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14  103 ms  N/A     107 ms  N/A     107 ms  N/A     104 ms  N/A     102 ms  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15  105 ms  N/A     108 ms  N/A     107 ms  N/A     103 ms  N/A      *      po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16  104 ms  N/A     106 ms  N/A     105 ms  N/A     102 ms  N/A     106 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17  106 ms  N/A     107 ms  N/A     109 ms  N/A     103 ms  N/A     106 ms  acmegamers.com [208.43.95.250]

Ping statistics for www.acmectf.com
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 103ms, Maximum = 109ms, Average = 106ms

Code:

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 102ms, Maximum = 110ms, Average = 107ms

1 January, 2012; 8:27 PM Pacific (11:27 EST)

[WORM]

Everything looks okay. SoftLayer spent time to check last night as stated and provided me with results that show no problems at all.

I ran tests myself last night from the server and found nothing.

If this happens again, get me some data as stated above...tracerts and ping summaries with date/time/ip info.

[ex]

According to quadz @ tastyspleen, the problem is Time Warner...at least for now.

http://tastyspleen.net/quake/forums/index.php?topic=17911.0

From Time Warner Cable:

Time Warner Cable is performing a maintenance on their network equipment in Dallas. Certain TWC routers will be unavailable until the maintenance is complete, which explains the routing through Atlanta. The maintenance is expected to end at 0700 CDT today (1 hour from now). However the possibility exists that some of the maintenance activity may extend beyond the change window due to the complexity of this maintenance.

That explains it I think, at least if you have Time Warner (Road Runner).  They had some servers down here in Dallas, and I was getting routed through altanta, to new york, then back to dallas. 

I notice it gets really bad at night, from midnight through 6 a.m.  Apparently, this should be temporary (at least with Time Warner).

[Legend]

WORM the lag is pretty bad, 3 maps in a row, everyone lags out. I felt p2450 servers run smoother. I have a 21 ping and it feels like its an 80. I am not sure wether it is connection or the box itself.

[Bones]

10:35pm 1-5-12

connection quality 0%
server to client   6.19%
client to server  11.72%

10:50pm

connection quality 100%
server to client   5.88
client to server   4014.16

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    minimum = 33ms, Maximum = 53ms, Average = 36ms

11:05pm

connection quality 100%
server to client   1.75%   
client to server   2624.81%

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss)
Approximate round trip times in milli-seconds:
    minimum = 32ms, Maximum = 130ms, Average = 36ms

[WORM]

Legend: Please read up and give me some data.

Bones: No tracert to go with that? I appears your problem could be routing to the server, but hard to say.

[Bones]

Map changed and I was getting phone jack every 3 to 5 seconds. others asked about the lag as well
1/8/12  9PM

connection quality 0%
server to client   1.43%   
client to server   48.52%

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mark>tracert acmectf.com

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    15 ms    10 ms    16 ms  gig5-2-21.ardlme04-rtr001.ne.northeast.rr.com [24.31.155.110]
  4    10 ms     9 ms    10 ms  g10-4-1-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.246]
  5    22 ms    24 ms    20 ms  rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
  6    28 ms    27 ms    28 ms  ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
  7    29 ms    26 ms    29 ms  ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
  8    32 ms    29 ms    27 ms  66.109.11.126
  9    28 ms    27 ms    44 ms  ae7.bbr01.tl01.nyc01.networklayer.com [173.192.18.176]
 10    34 ms    33 ms     *     ae1.bbr01.eq01.wdc02.networklayer.com [173.192.18.156]
 11    37 ms    33 ms    34 ms  ae0.dar01.sr01.wdc01.networklayer.com [173.192.18.197]
 12    33 ms    35 ms    39 ms  po1.fcr01.sr01.wdc01.networklayer.com [208.43.118.134]
 13    36 ms    35 ms    33 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
 14    35 ms    33 ms    34 ms  acmegamers.com [208.43.95.250]

Trace complete.



ping  -n 100 208.43.95.250

Pinging 208.43.95.250 with 32 bytes of data:



Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 70ms, Average = 38ms

[Ash@S-Mart]

About every 4th tracert showed a little slow in Atlanta on NetworkLayer.  Continous ping shows no drops, but 1 in 11 slowed down 20-25%

C:\Documents and Settings\ME>tracert 208.43.95.250

Tracing route to acmegamers.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.6.66
  2     9 ms     8 ms     6 ms  ip##-###-###-1.om.om.cox.net [#.###.###.#]
  3     9 ms     8 ms     7 ms  ##.##.#.###
  4     9 ms     7 ms     8 ms  ##.##.#.##
  5    10 ms    14 ms    17 ms  mtc1dsrj02-ae3.0.rd.om.cox.net [68.13.14.13]
  6    57 ms    23 ms    24 ms  68.1.2.121
  7    23 ms    23 ms    25 ms  ae7.bbr02.eq01.dal03.networklayer.com [173.192.1
8.209]
  8    70 ms    56 ms    64 ms  ae1.bbr01.tl01.atl01.networklayer.com [173.192.1

[Legend]

Ping test at 9:33pm when the lag is happening.

From Eastern region "Rhode Island"

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

C:\Users\Jean>ping acmectf.com -t

Pinging acmectf.com [208.43.95.250] with 32 bytes of data:
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=50ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=25ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=27ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118

Ping statistics for 208.43.95.250:
    Packets: Sent = 132, Received = 132, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 50ms, Average = 20ms
Control-C
^C
C:\Users\Jean>d`

Lag still happening on the tracert:

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

C:\Users\Jean>ping acmectf.com -t

Pinging acmectf.com [208.43.95.250] with 32 bytes of data:
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=50ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=25ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=23ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=22ms TTL=118
Reply from 208.43.95.250: bytes=32 time=24ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=27ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=18ms TTL=118
Reply from 208.43.95.250: bytes=32 time=19ms TTL=118
Reply from 208.43.95.250: bytes=32 time=21ms TTL=118
Reply from 208.43.95.250: bytes=32 time=20ms TTL=118

Ping statistics for 208.43.95.250:
    Packets: Sent = 132, Received = 132, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 50ms, Average = 20ms
Control-C
^C
C:\Users\Jean>tracert acmectf.com

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     6 ms     7 ms     6 ms  10.1.8.1
  3     7 ms     7 ms     7 ms  cransysc01-gex0102000.ri.ri.cox.net [68.9.8.101]

  4     6 ms     7 ms     7 ms  ip68-9-7-13.ri.ri.cox.net [68.9.7.13]
  5    11 ms     7 ms     7 ms  ip98-190-160-193.ri.ri.cox.net [98.190.160.193]

  6     7 ms     8 ms     8 ms  provdsrj01-ae3.0.rd.ri.cox.net [98.190.33.20]
  7    18 ms    20 ms    18 ms  68.1.4.133
  8    20 ms    23 ms    19 ms  ae1.dar02.sr01.wdc01.networklayer.com [173.192.1
8.189]
  9    19 ms    19 ms    21 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 10    19 ms    19 ms    20 ms  208.43.108.254-static.reverse.softlayer.com [208
.43.108.254]
 11    20 ms    23 ms    25 ms  acmegamers.com [208.43.95.250]

Trace complete.

I don't think it's the "Connection", it maybe server side.

[Bones]

9:32PM in the middle of map edge

connection quality 0%
server to client   0.68%   
client to server   48.57%


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mark>tracert acme.cfg

Tracing route to acme.cfg [72.3.199.7]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms     9 ms    20 ms  gig5-2-21.ardlme04-rtr001.ne.northeast.rr.com [24.31.155.110]
  4    13 ms    17 ms     9 ms  g10-4-1-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.246]
  5    21 ms    21 ms    19 ms  rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
  6    27 ms    28 ms    60 ms  ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
  7    29 ms    27 ms    35 ms  107.14.17.169
  8    47 ms    45 ms    46 ms  xe-11-1-2.edge2.Newark1.Level3.net [4.28.190.89]

  9    48 ms    52 ms    55 ms  ae-32-52.ebr2.Newark1.Level3.net [4.69.156.62]
 10    67 ms    67 ms    72 ms  ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101]
 11    54 ms    56 ms    56 ms  ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
 12    62 ms    59 ms    58 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
 13   135 ms   126 ms   129 ms  ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
 14    89 ms    86 ms    86 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 15    90 ms    90 ms    90 ms  ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]

 16   100 ms    99 ms    97 ms  ae-4-90.edge2.Dallas3.Level3.net [4.69.145.204]

 17   172 ms   132 ms    69 ms  RACKSPACE-M.edge2.Dallas3.Level3.net [4.59.36.50
]
 18    90 ms    65 ms    65 ms  vlan901.core1.dfw1.rackspace.com [72.3.128.21]
 19    70 ms    69 ms    74 ms  aggr125a.dfw1.rackspace.net [72.3.129.149]
 20     *        *        *     Request timed out.
 21     *        *

ping  -n 100 208.43.95.250

Pinging 208.43.95.250 with 32 bytes of data:



Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 63ms, Average = 36ms

[NQK Ramirez]

That intermittent lag every 2 seconds really killed the server tonight. Looks like it's back.

[Fors]

yes I agree, I keep getting the phone jack but a semi-clean trace.... its like a constant ping to the server, is that possible for someone to do?

[WORM]

Tracerts and ping summaries do not show a problem with network traffic so far. I am a bit worried by seeing some of the client to server pl percentages. Leads me to ask what version of client are you using? I've been testing some today and everything is smooth.

I've done a few things to the server today so let's see how it goes tonite....trying to narrow this puppy down. 

Fors: Yes, you can run a continuous ping but I don't see that helping. The 100 ping runs during problem periods show okay.

Still, if this persists, please run your tests for me. Thanks and sorry for the troubles.

[WORM]

C:\Documents and Settings\Mark>tracert acme.cfg

Tracing route to acme.cfg [72.3.199.7]
over a maximum of 30 hops:

Try tracert acmectf.com 

[Bones]

hmmm lol i normally type that.  tracert acmectf.com   i must have mispelled it.  im using the updated r1q2   8012

[alka]

C:\Documents and Settings\Mark>tracert acme.cfg

Tracing route to acme.cfg [72.3.199.7]
over a maximum of 30 hops:

Try tracert acmectf.com 

heh 

[Bones]

I kinda thought to myself why does this tracert look different lol. 

[WORM]

Checking in the server last night I did not see where there were any network issues..except for Bones having trouble with Roadrunner..my traceroute to him from the server showed a bit of packet loss at a node in NYC, but nothing in our data center.

Fors was saying he had problems but running to him was fine. He did not give me a tracert to the server so it's impossible to pin that one down.

I've added a tool for you to run a traceroute from the server to you if you are experiencing any problems. You can access it here: http://acmectf.com/trace.php

It will run a trace from the server to your IP, or whatever IP/host you enter, for a maximum of 30 hops using the system tracert command and outputting to web page. It may take several minutes to run so be patient.

Don't everyone flood it at the same time or it may start killing tracert sessions and give wrong info.

Most of you probably already know that if your router is not responding to ICMP requests it will only show * with no route info until it hits the 30th hop and stops, so kill it before then.

Also, see a * on other nodes does not necessarily indicate a problem there, some switches on the route to you may not all respond to ICMP requests and traffic is still passed on. Just look for large jumps in ping and inconsistencies on nodes.

[The Cleaner]

I could go for some hash browns right now.

[alka]

This was tonight 02-17-2012 starting around 11:20pm and ending around 11:30pm EST.
Map was marics_ctf14.

During the time of issues :

Code:

Lag stats for alka:
RTT (min/avg/max)  : 20 ms / 22 ms / 27 ms
Connection quality : 0.00%
Server to Client PL: 0.61%
Client to Server PL: 1.28%

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     7 ms     9 ms    11 ms  xe-10-2-0-0-sur01.l1douglas.ga.atlanta.comcast.n
et [68.86.109.249]
  4     8 ms     9 ms    10 ms  xe-0-0-0-0-sur01.b5mableton.ga.atlanta.comcast.n
et [68.85.109.50]
  5     7 ms     9 ms    11 ms  xe-1-1-0-0-ar01.b0atlanta.ga.atlanta.comcast.net
 [68.85.109.54]
  6    16 ms    12 ms    12 ms  pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.93.201]
  7    17 ms    15 ms     *     pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.86.86]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    28 ms    25 ms    25 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 12    23 ms    22 ms    26 ms  208.43.108.254-static.reverse.networklayer.com [
208.43.108.254]
 13    21 ms    22 ms    23 ms  acmegamers.com [208.43.95.250]

Trace complete.
--------------------------------------------------
Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     7 ms     9 ms    12 ms  xe-10-2-0-0-sur01.l1douglas.ga.atlanta.comcast.n
et [68.86.109.249]
  4     8 ms    10 ms    10 ms  xe-0-0-0-0-sur01.b5mableton.ga.atlanta.comcast.n
et [68.85.109.50]
  5     9 ms    11 ms     7 ms  xe-1-1-0-0-ar01.b0atlanta.ga.atlanta.comcast.net
 [68.85.109.54]
  6    10 ms    16 ms    10 ms  pos-3-8-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.95.197]
  7    12 ms     *       13 ms  pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.86.86]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    24 ms    21 ms    23 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 12    22 ms    23 ms    23 ms  208.43.108.254-static.reverse.networklayer.com [
208.43.108.254]
 13    22 ms    23 ms    21 ms  acmegamers.com [208.43.95.250]

Trace complete.
--------------------------------------------------
Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    11 ms  xe-10-2-0-0-sur01.l1douglas.ga.atlanta.comcast.n
et [68.86.109.249]
  4     9 ms     6 ms    11 ms  xe-0-0-0-0-sur01.b5mableton.ga.atlanta.comcast.n
et [68.85.109.50]
  5   114 ms    39 ms    10 ms  xe-1-1-0-0-ar01.b0atlanta.ga.atlanta.comcast.net
 [68.85.109.54]
  6    12 ms    13 ms    11 ms  pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.93.201]
  7    13 ms    11 ms    11 ms  pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.86.86]
  8    12 ms    11 ms    14 ms  xe-0-0-1.bbr01.tl01.atl01.networklayer.com [75.1
49.231.154]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    23 ms    26 ms    26 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 12    21 ms    22 ms    25 ms  208.43.108.254-static.reverse.networklayer.com [
208.43.108.254]
 13    29 ms    27 ms    25 ms  acmegamers.com [208.43.95.250]

Trace complete.
--------------------------------------------------
Pinging 208.43.95.250 with 32 bytes of data:
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=25ms TTL=116
Reply from 208.43.95.250: bytes=32 time=28ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=27ms TTL=116
Reply from 208.43.95.250: bytes=32 time=29ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=25ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=27ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=24ms TTL=116
Reply from 208.43.95.250: bytes=32 time=28ms TTL=116
Reply from 208.43.95.250: bytes=32 time=27ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=25ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=32ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=27ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=24ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=24ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=27ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=24ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=26ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=22ms TTL=116
Reply from 208.43.95.250: bytes=32 time=23ms TTL=116
Reply from 208.43.95.250: bytes=32 time=21ms TTL=116

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 32ms, Average = 23ms

Results after the issue subsided:

Code:

Lag stats for alka:
RTT (min/avg/max)  : 23 ms / 23 ms / 23 ms
Connection quality : 100.00%
Server to Client PL: 0.00%
Client to Server PL: 0.00%

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     7 ms    11 ms  xe-10-2-0-0-sur01.l1douglas.ga.atlanta.comcast.n
et [68.86.109.249]
  4     7 ms     9 ms     8 ms  xe-0-0-0-0-sur01.b5mableton.ga.atlanta.comcast.n
et [68.85.109.50]
  5    10 ms     7 ms    10 ms  xe-1-1-0-0-ar01.b0atlanta.ga.atlanta.comcast.net
 [68.85.109.54]
  6    10 ms     9 ms    10 ms  pos-3-5-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.93.125]
  7     *       15 ms    19 ms  pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.86.86]
  8    11 ms    12 ms    60 ms  xe-0-0-1.bbr01.tl01.atl01.networklayer.com [75.1
49.231.154]
  9    25 ms    25 ms    23 ms  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.1
8.152]
 10    25 ms    21 ms    27 ms  ae0.dar02.sr01.wdc01.networklayer.com [173.192.1
8.203]
 11    27 ms    27 ms    27 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 12    24 ms    25 ms    24 ms  208.43.108.254-static.reverse.networklayer.com [
208.43.108.254]
 13    23 ms    24 ms    25 ms  acmegamers.com [208.43.95.250]

Trace complete.

ping summary was pretty much unchanged during both times.

[WORM]

We're performing some tests. This may take a while but I have an idea what is causing the problem and it is external to our server so please bear with us as we try to narrow it down.

[The Cleaner]

Time is the one thing the dwindling Q2 community doesn't really have.  Sadly.

[WORM]

I hear the test last nite didn't go well....changing it up for tonite. Let's see.

[WORM]

And again.

[WORM]

After denials of any problems with their network we now get this notice from SoftLayer:

Scheduled Maintenance -- Maintenance ID 4576764 -- Multiple Firewall Devices [03/14/2012]
Date: Wednesday, March 14, 2012 (03/14/2012)
Start Time: 12:01 AM EST
End Time: 04:01 AM EST
Services affected: Firewall Services
Location: WDC01
Duration: 4 hours

Network Engineers have identified an issue with your hardware firewall on the WDC01 network. The devices impacted by this maintenance are fw01.fcr01.wdc01, fw01.fcr02.wdc01 and fw01.fcr03.wdc01. To prevent an unplanned outage resulting in significant downtime, Engineers will be upgrading firmware during a scheduled maintenance window.

Private connectivity will NOT be affected by this maintenance (iSCSI, DNS, NAS, etc). While the maintenance window is set for 4 hours, we expect no more than 10 minutes of down time per device.

Hang in there with us and hope this cures the problems. 

[Targe+]

After denials of any problems with their network we now get this notice from SoftLayer:

Scheduled Maintenance -- Maintenance ID 4576764 -- Multiple Firewall Devices [03/14/2012]
Date: Wednesday, March 14, 2012 (03/14/2012)
Start Time: 12:01 AM EST
End Time: 04:01 AM EST
Services affected: Firewall Services
Location: WDC01
Duration: 4 hours

Network Engineers have identified an issue with your hardware firewall on the WDC01 network. The devices impacted by this maintenance are fw01.fcr01.wdc01, fw01.fcr02.wdc01 and fw01.fcr03.wdc01. To prevent an unplanned outage resulting in significant downtime, Engineers will be upgrading firmware during a scheduled maintenance window.

Private connectivity will NOT be affected by this maintenance (iSCSI, DNS, NAS, etc). While the maintenance window is set for 4 hours, we expect no more than 10 minutes of down time per device.

Hang in there with us and hope this cures the problems. 

Has this been done yet? I am hoping this will fix my connection issues. If it has already been done, then it hasn't resolved them 

[WORM]

Response - 2012-Mar-16 05:39 (GMT-0600) [Update 4]
   
We apologize for the delay in updating you, but this maintenance was completed on time and successfully. Thank you for your patience, and we are now going to close this ticket.

Sincerely,

Network Engineering

Completed. Better now?

Sincerely,

WORM.

[Targe+]

Response - 2012-Mar-16 05:39 (GMT-0600) [Update 4]
   
We apologize for the delay in updating you, but this maintenance was completed on time and successfully. Thank you for your patience, and we are now going to close this ticket.

Sincerely,

Network Engineering

Completed. Better now?

Sincerely,

WORM.

Yes. I went from have 40-50 red lines @ the bottom to 3-5. HUGE difference. <3

Talgo

[alka]

3-5?!!?? submit another ticket worm!

[ex]

Serious horrible lag is back with a fury tonight, been getting progressively worse night after night, and only on map loads.  It's the strangest thing I've ever seen.

You might wanna demand a free month's service or something, because softlayer SUCKS.

I'm sure it is softlayer because tastyspleen and several other servers have been lagging and been getting higher pings progressively over the last few months since softlayer came into the picture.

[alka]

It's being investigated with the same fury that it's affecting the server.
Bear with us! 

and no sense in getting free month's service, we're still working off the aol CDs that were laying around.. like 8000 hours total for free.

[WORM]

I sincerely apologize that the quality of service you are receiving is not up our usual standards. We strive to provide you with the best possible online gaming experience and we are diligently working to improve upon that and reach new heights.

Due to the nature of the problem we are using everything in our power to solve this and humbly ask for your patience and kind indulgence until we resolve the issue. As there are a number of factors involved this is not an easy task and we have some of the best minds in the business hard at work troubleshooting the problem(s).

We do ask for your cooperation in providing information as we may ask from time to time. No personal information will be shared with any third party and we promise not to sell, barter, trade or otherwise release any personally identifiable information to any third parties for any reason whatsoever unless required by law. Such information will only be used to support and/or enhance your gaming experience while using our services.

The choice to help is entirely up to you and you will not be penalized in any way for refusing our requests except we do reserve the right to insult, ridicule, belittle, boot, ban or otherwise harass you for your hesitance in assisting.

Thank you again for using ACMECTF.com and we look forward to your continued support.

[Targe+]

I do realize that this is a "free to me" service & I am very grateful for that fact. However, I can't help but feel frustrated with constant PL. I do my very best to portray my frustration in the most civil of manner & very much appreciate the help that has been given in return.

Alka has been trying to help me with my issues and has been very helpful. This makes me marvel at the quality of people you find to be admins. Even the worst admins that you have found (present/past) have been better then the admins at DirtyWhore's server. It's funny how quickly people forget that.

Thanks,

Talgo

[NQK Ramirez]

Yes, an Acme admin came to my house the other day and fixed all my computer issues so my quake could run smoothly     I heard Yowza pays the admins 80k+ a year so there is probably a lot of applicants and they just pick the crop of the cream.

There is probably a crack team of Acme scientist perusing over the problem right now. And all that is FREE. Never played on Dirty whore server, I stopped back then but from what I heard he probably would have told me to Beep OFF if i required assistance.  He probably didn't pay his admins top dollars either.

[marsq2dm]

Hey Ramirez,

Did Target+ not express his appreciation up front for what is essentially a free service? 

Did you not learn to read well?

Can you please stfu unless you can offer real help, it would be most appreciated.

signed - everyone else on the internet.

[ex]

lol

[NQK Ramirez]

Hey Ramirez,

Did Target+ not express his appreciation up front for what is essentially a free service? 

Did you not learn to read well?

Can you please stfu unless you can offer real help, it would be most appreciated.

signed - everyone else on the internet.

Why so serious 

[WORM]

I didn't mean to be insulting to anyone so please don't take it that way...just my smart-arsed way of trying to inject a bit of levity into a frustrating situation. I apologize if it came across as anything else

Now....don't get serious.

[ex]

I think the only serious part of this thread is the LAG.

And Ramirez needing to stfu.

Both very serious issues that need to be addressed!   

[WORM]

We're working on it...and will be asking for volunteers to try something out soon..process of elimination.

Trust me. 

[ex]

I formally volunteer my services to eliminate Ramirez!  Keep me posted.

[NQK Ramirez]

I formally volunteer my services to eliminate Ramirez!  Keep me posted.

Bring it on!!! 

[WORM]

http://www.wormlair.com/forum/index.php/topic,3483.msg51351.html#msg51351

[Targe+]

Thanks for the notice. Is the goal to have lots of people on the pub?

[alka]

Thanks for the notice. Is the goal to have lots of people on the pub?

This is temporary to aid in troubleshooting the lag (phonejack during map change) that everyone is experiencing.

[Targe+]

What I meant was, is it okay to go on the server? Should we avoid the server? Does it even matter? I am guessing it doesn't if nothing was said.

If we you were looking for people to be on the server to test, I would make a point of logging on.

Talgo

[WORM]

Go for it...the more the merrier tonite.  

Would be great to test with full server...make admins have to use their reserved slots.

[WORM]

We are now redirecting traffic on the pub to an offsite server for testing purposes. Other servers, (match, rwz, etc), are not affected.

You may, or may not, notice an extra connection as we direct you to this test server. Some people may see pings a little higher or lower than what they are used to but shouldn't be a huge variation. This box is in the Washington/Baltimore area and is set up with only our Q2 server running.

We do not plan on this as a permanent solution, it is only for troubleshooting.

You will not see any players on our pub if you view using Q2 server browser, HLSW or other server browsing software. Go ahead and connect anyway and you will be connected to the test server.

Thanks for your understanding, patience and help.

[WORM]

We are removing the redirect today and all traffic will go back to our normal server.

Thanks to everyone connecting last nite as it was a help in troubleshooting our problems.

I will not be available today so alka will be doing some work on the server from what we have discovered. Hopefully, this will solve the phonejack-on-map-change issues. If not, blame alka. 

No...really...if it doesn't work, we move on to plan X.

As always, we appreciate your patience.

[alka]

No...really...if it doesn't work, we move on to plan X.

Plan X is when shit gets serious. And you don't want any of this shit Dewey.

[NQK Ramirez]

We are removing the redirect today and all traffic will go back to our normal server.

Thank god!

Haven't seen anyone pinging better to that temp server.

[WORM]

Setting up that test server was a way for us to prove/disprove a theory. We feel we have learned something from it....how the pub runs tonite will tell more.

Again, sorry for the inconveniences, this should be resolved soon.

Please send/post any tracerts/ping summaries you may run if there are problems tonite.

Thanks again for your help.

[ex]

The lag wasn't around on any maps for me tonight.  Didn't see anyone else complaining either.  I did get on after 10 pm CST tho, not a ton of ppl were on.

Maybe problem is alleviated when connection gets reset?  Just a thought.

[WORM]

Thanks, ex. We'll see how it goes tonite....any and all feedback is greatly appreciated.

[CaKe]

I was getting multiple plugs at the beginning of every map
I usually have pl and see plugs occassionally/get kicked from the server entirely sometime, but this was a lot at the very beginning of every map

/my feedback

[Legend]

same as what Cake said, it would also lag if you were downloading a map you didn't have from what some people said on vent.

[Targe+]

Red Lines Everywhere :-/

Talgo

[yowza]

TRACERT needed.

Red Lines Everywhere :-/

Talgo

[Targe+]

TRACERT needed.

http://www.wormlair.com/forum/index.php/topic,3476.0.html

[WORM]

TRACERT needed.

http://www.wormlair.com/forum/index.php/topic,3476.0.html

Unfortunately, I don't see any posting of, or link to, a tracert run to our server from the period you were experiencing problems.

Am I missing something?

[Targe+]

Unfortunately, I don't see any posting of, or link to, a tracert run to our server from the period you were experiencing problems.

Am I missing something?

Yes.

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

C:\Users\User>tracert acmectf.com

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    24 ms    24 ms    23 ms  d66-222-160-1.abhsia.telus.net [66.222.160.1]
  3    25 ms    23 ms    23 ms  96.1.176.129
  4    69 ms    69 ms    69 ms  75.154.223.174
  5    69 ms    71 ms    69 ms  173.182.200.42
  6    77 ms    62 ms    62 ms  cer-edge-17.inet.qwest.net [67.14.8.86]
  7    62 ms   100 ms    63 ms  xe-1-0-0.bbr01.eq01.chi01.networklayer.com [65.1
13.255.94]
  8     *       69 ms    70 ms  ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
  9     *       95 ms    95 ms  ae0.bbr02.eq01.wdc02.networklayer.com [173.192.1
8.154]
 10    90 ms    88 ms   114 ms  ae1.dar02.sr01.wdc01.networklayer.com [173.192.1
8.189]
 11    90 ms    98 ms    89 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.11
8.138]
 12    90 ms    88 ms    90 ms  208.43.108.254-static.reverse.networklayer.com [
208.43.108.254]
 13    89 ms    89 ms    90 ms  acmegamers.com [208.43.95.250]

Trace complete.

C:\Users\User>^A

That's from March 12 (only couple weeks ago). Changes to the server have changed nothing. I still have 20-30 Red lines in my netgraph.

I have changed every setting around (with the help of Alka) that I can think of. I posted pics of Tastyspleen (and netgraph) for comparison reasons (so that we know it's not a Q2 problem per-say. Although I get red lines there tooo...).

I want a ways to narrow down the problem. I tried downloading Alka's Q2 pack (and did not change any settings) and still had red lines. I removed the anticheat.dll out of my Q2 folder, still red lines.

Last night when I was playing, I still had red lines, though not as bad as other nights (last night was 7-10 not the normal ~30).

If you can tell me it's my ISP, that is something I can work out on my out. If it's the path...I don't know how to fix that. If it's a setting... I don't know. I can tell you it hasn't always been there, it's only the last couple months.

Talgo

[alka]

So the pl wasn't as bad as normal last night for you Targe+?
The only changes made to the server thus far have been to try and solve the phonejack-on-map-change issue.
Nothing changed so far would help, nor hurt, your connection to the server.

I'm still thinking it's something in your route from you to the server.

Now, if more people came forward with issues of packet loss to acme then it would lean more towards a server-side issue.

I've never asked if you had a tracert from before the problem started for comparison?

If you are on the server tonight and have mad pl you can run a recent tracert and I will be around to run a reverse back to you.

We'll figure this thing out!  

http://www.youtube.com/watch?v=ZxrEth_KvOg

[h0ps]

haha alka, katt williams is so funny. i love watching that guys stand-up

http://www.youtube.com/watch?NR=1&feature=fvwp&v=r8T7HWxwHEQ

[WORM]

What alka said ^

Target:

Red Lines Everywhere :-/

From the date and time on that post we have to assume you were referring to last night.

TRACERT needed.

YOWZA asks, in one word, if you can provide a tracert.

And you reply with a tracert from almost 3 weeks ago.  

Hence my comment and asking if I missed something. And I did...there is no tracert from you from last night.

We're trying to help you, and anyone else with problems. Help us to help you.

Your problem may be in routing, as alka stated. To fully determine if there is a problem with routing or connections to the data center where we are located or to the server itself, we have to have more info and evidence to present to Softlayer, if it is a local network problem. Otherwise, we're pissing into an Alberta Clipper...head on.

So...what needs to happen is this:

When you are having problem on server, let alka or myself know. (And you will have a much, much greater chance of catching alka.)

You will need to follow instructions in this post: http://www.wormlair.com/forum/index.php/topic,3448.msg50674.html#msg50674

Alka will do the same from the server itself to your IP. This all needs to be done at the time the problem is occuring, not after it goes away.

That can tell us where the problem is and, if a problem is found with local network, we will have something to take to Softlayer.

Please understand that we work for free. Softlayer doesn't. If there is an issue with the network, they will fix it at no charge....but we have to show an issue! If we can not show an issue, (they don't hang on our server playing Q2), they won't waste time with us...or they will charge ungodly sums of money with no guarantee of any improvement.

We are continuing to investigate server-side issues as well.

[Targe+]

I was having a "red lines issue" 3 weeks ago and posted that Netgraph. Nothing has changed since 3 weeks ago (afaik). This is not a "new" issue. What are you guys expecting to change in my netgraph as compared to 3 weeks ago? I also did the ping -n 100 deal which is also posted in the other thread. All 100 came back a-okay.

I realize that I know next to nothing about these types of things, which is leading to my increasing frustration. For example; If I had a rattle in my car, and I took a audio recording and sent it to my dealership, and then 3 weeks later they ask for a new audio recording because "the other one is 3 weeks old", I would be like "It's the same freeking sound!". I don't understand how this is any different.

Regardless, if I am on tonight, I will take another SS, another Tracert, and another ping 100 test.

Talgo

[WORM]

I can fully commiserate with your frustration.....we're frustrated too. 

The internet isn't like a car...if it was, we'd just change oil, filter, fill up the tank, air up the tires and be off doing 90 mph down main street with panties tied to the radio antenna. 

Your route to the server can be different from one time to another, depending on a number of things. Best of worlds is it would remain the same and stable...but with the vagaries of ISP agreements to carriers, traffic loads on switches and balancing or non-balancing of same, a backhoe cutting major cable and ensuing re-routing, DDoS attacks, etc. and so on....nothing is static.

That's why a picture, (read tracert), taken 3 weeks ago is only good for comparison. Think of it as taking a picture of me 40 years ago and saying, "My, what a fine looking young man that is!".....well, I still cut a dashing figure, but I'm not the same as then. 

One more thing.....when asking alka or myself to trace/ping to you...please change your router configuration so it will reply to ICMP requests. You can set it back afterwards, and I would recommend you do so afterwards.

Thanks again for your patience.

[Targe+]

The internet isn't like a car...if it was, we'd just change oil, filter, fill up the tank, air up the tires and be off doing 90 mph down main street with panties tied to the radio antenna. 

Did you try re-starting the server 

Talgo

PS - Turn off who and a what now?

[alka]

Did you try re-starting the server 

* alka giggles

PS - Turn off who and a what now?

for software firewall including 3rd party:
http://www.dslreports.com/faq/tweaks/3._Becoming_Pingable

not sure if you have firewall enabled on your router, but if you do:
http://screenshots.portforward.com/Actiontec/V1000H/Firewall_Firewall.htm