If anyone else gets lag, maybe do a tracert and add your data to this. Note the two of three lost packets on the very last hop. It's definitely an ISP problem, not your server. The first two of those three pings were during one of the lag bursts, then it came out of it and pinged successfully the third time:
Tracing route to waroftheworlds.ath.cx [209.115.181.78]
over a maximum of 30 hops:
1 41 ms 23 ms 29 ms 10.88.93.1
2 10 ms 9 ms 10 ms 12.244.84.193
3 47 ms 12 ms 27 ms 12.244.64.142
4 13 ms 69 ms 14 ms 12.244.72.42
5 13 ms 41 ms 14 ms gbr1-p70.st6wa.ip.att.net [12.123.44.57]
6 21 ms 20 ms 22 ms gbr3-p70.st6wa.ip.att.net [12.122.5.157]
7 16 ms 13 ms 21 ms ggr1-p360.st6wa.ip.att.net [12.123.44.129]
8 30 ms 95 ms 32 ms acr1-sonet2-2-1-0.Seattle.cw.net [208.172.83.209
]
9 32 ms 29 ms 32 ms acr2-loopback.Seattle.cw.net [208.172.82.62]
10 71 ms 30 ms 48 ms telus-services-inc.Seattle.cw.net [208.172.81.13
0]
11 41 ms 46 ms 64 ms sttlwa01br01.bb.telus.com [204.174.217.81]
12 74 ms 61 ms 67 ms vancbc01br01.bb.telus.com [209.53.75.165]
13 62 ms 59 ms 58 ms clgrab21br01.bb.telus.com [209.53.75.182]
14 79 ms 134 ms 79 ms edtnabxmbr01.bb.telus.com [205.233.111.217]
15 81 ms 80 ms 78 ms edtnabkddr01.bb.telus.com [205.233.111.134]
16 94 ms 118 ms 82 ms EDTNXJ-COMP02.ab.tac.net [209.115.219.133]
17 82 ms 101 ms 81 ms titan-fe00.interbaun.net [199.185.131.249]
18 * * 103 ms 078.209-115-181-0.interbaun.com [209.115.181.78]
Maybe send this along to your ISP and they can find the problem... Since it's the last hop, it's not a router somewhere, it's definitely the fault of your LOCAL ISP, so sic em! hehe
Tracing route to waroftheworlds.ath.cx [209.115.181.78]
over a maximum of 30 hops:
1 41 ms 23 ms 29 ms 10.88.93.1
2 10 ms 9 ms 10 ms 12.244.84.193
3 47 ms 12 ms 27 ms 12.244.64.142
4 13 ms 69 ms 14 ms 12.244.72.42
5 13 ms 41 ms 14 ms gbr1-p70.st6wa.ip.att.net [12.123.44.57]
6 21 ms 20 ms 22 ms gbr3-p70.st6wa.ip.att.net [12.122.5.157]
7 16 ms 13 ms 21 ms ggr1-p360.st6wa.ip.att.net [12.123.44.129]
8 30 ms 95 ms 32 ms acr1-sonet2-2-1-0.Seattle.cw.net [208.172.83.209
]
9 32 ms 29 ms 32 ms acr2-loopback.Seattle.cw.net [208.172.82.62]
10 71 ms 30 ms 48 ms telus-services-inc.Seattle.cw.net [208.172.81.13
0]
11 41 ms 46 ms 64 ms sttlwa01br01.bb.telus.com [204.174.217.81]
12 74 ms 61 ms 67 ms vancbc01br01.bb.telus.com [209.53.75.165]
13 62 ms 59 ms 58 ms clgrab21br01.bb.telus.com [209.53.75.182]
14 79 ms 134 ms 79 ms edtnabxmbr01.bb.telus.com [205.233.111.217]
15 81 ms 80 ms 78 ms edtnabkddr01.bb.telus.com [205.233.111.134]
16 94 ms 118 ms 82 ms EDTNXJ-COMP02.ab.tac.net [209.115.219.133]
17 82 ms 101 ms 81 ms titan-fe00.interbaun.net [199.185.131.249]
18 * * 103 ms 078.209-115-181-0.interbaun.com [209.115.181.78]
Maybe send this along to your ISP and they can find the problem... Since it's the last hop, it's not a router somewhere, it's definitely the fault of your LOCAL ISP, so sic em! hehe
Comment