PINGS SUCK

**BigHub** · 09-01-05, 06:39 PM

check out my tracert....everything looks normal except for the very last strand of data that was sent.....

C:\Documents and Settings\Jono Hubbard>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 13 ms 10 ms 12 ms ip70-191-173-1.fv.dl.cox.net [70.191.173.1]
3 8 ms 9 ms 7 ms cdm-208-180-23-153.bcst.cox-internet.com [208.18
0.23.153]
4 14 ms 12 ms 13 ms cdm-208-180-23-133.bcst.cox-internet.com [208.18
0.23.133]
5 16 ms 14 ms 21 ms dllsbbrc02-gew0402.ma.dl.cox-internet.com [66.76
.45.149]
6 14 ms 15 ms 14 ms 68.1.206.45
7 16 ms 20 ms 15 ms so-3-3-0-0.gar2.Dallas1.Level3.net [4.78.234.5]

8 17 ms 17 ms 15 ms ge-1-2-52.car4.Dallas1.Level3.net [4.68.122.39]

9 17 ms 15 ms 15 ms savvis-level3-ge.Dallas1.Level3.net [4.68.111.86
]
10 22 ms 14 ms 13 ms dpr1-ae1.DallasEquinix.savvis.net [204.70.134.13
]
11 19 ms 21 ms 15 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
12 20 ms 16 ms 15 ms 216.39.64.10
13 20 ms 17 ms 18 ms 216.39.69.134
14 * * * Request timed out.
15 43 ms 41 ms 47 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

I don't know what to say...

**...bigdog...** · 09-01-05, 07:44 PM

47.......that's a little high.

C:\Documents and Settings\The System>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.0.1
2 9 ms 8 ms 9 ms adsl-70-241-95-254.dsl.hstntx.swbell.net [70.241
.95.254]
3 10 ms 9 ms 10 ms dist1-vlan60.hstntx.sbcglobal.net [151.164.11.19
0]
4 10 ms 10 ms 9 ms bb1-g1-2-0.hstntx.sbcglobal.net [151.164.11.230]

5 10 ms 11 ms 9 ms core1-p6-0.crhstx.sbcglobal.net [151.164.188.1]

6 14 ms 14 ms 15 ms core3-p3-0.crdltx.sbcglobal.net [151.164.240.189
]
7 15 ms 14 ms 14 ms core1-p9-0.crdltx.sbcglobal.net [151.164.242.118
]
8 17 ms 16 ms 15 ms bb1-p2-0.rcsntx.sbcglobal.net [151.164.40.38]
9 16 ms 16 ms 16 ms bb2-p4-0.rcsntx.sbcglobal.net [151.164.191.118]

10 17 ms 17 ms 18 ms ex1-p12-0.eqdltx.sbcglobal.net [151.164.44.45]
11 17 ms 16 ms 17 ms 151.164.249.222
12 18 ms 18 ms 18 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
13 18 ms 18 ms 18 ms 216.39.64.26
14 18 ms 19 ms 18 ms 216.39.69.206
15 * * * Request timed out.
16 39 ms 40 ms 40 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

But mine's allright. <20ms

*** correction, mine is not allright. Everythings fine until we get to the server's network, and then it goes from 18ms to 40ms. That's not normal for a single hop, and I told AoW. They bullshitted me around like they always do, but at least they didn't restart the server.

**...bigdog...** · 09-01-05, 11:34 PM

And now, we just had a HUGE lag spike on italy, knocking out my radar, and throwing dead bodies around in the apartments on italy. Krazykash was there.....he remembers me talking about it probably.

The map changed seconds after the spike, since it just so happened that the round was over, and went to assault. I checked my ping there, and I was back down in the 15-20 range, instead of the 35-40+ I got previously......as ALL of us were.

AoW said it was my ISP, but it certainly wasn't ALL of our ISP's. So fucking sick of them being stupid.

here's my tracert immediately after the spike and map change:

C:\Documents and Settings\The System>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.0.1
2 9 ms 9 ms 8 ms adsl-70-241-95-254.dsl.hstntx.swbell.net [70.241
.95.254]
3 10 ms 9 ms 10 ms dist1-vlan60.hstntx.sbcglobal.net [151.164.11.19
0]
4 9 ms 10 ms 10 ms bb1-g1-2-0.hstntx.sbcglobal.net [151.164.11.230]

5 10 ms 10 ms 10 ms core1-p6-0.crhstx.sbcglobal.net [151.164.188.1]

6 14 ms 15 ms 14 ms core3-p3-0.crdltx.sbcglobal.net [151.164.240.189
]
7 15 ms 15 ms 15 ms core1-p9-0.crdltx.sbcglobal.net [151.164.242.118
]
8 15 ms 17 ms 16 ms bb1-p2-0.rcsntx.sbcglobal.net [151.164.40.38]
9 16 ms 15 ms 16 ms bb2-p4-0.rcsntx.sbcglobal.net [151.164.191.118]

10 17 ms 17 ms 17 ms ex1-p12-0.eqdltx.sbcglobal.net [151.164.44.45]
11 17 ms 17 ms 17 ms 151.164.249.222
12 18 ms 17 ms 17 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
13 31 ms 18 ms 17 ms 216.39.64.26
14 26 ms 18 ms 32 ms 216.39.69.206
15 * * * Request timed out.
16 19 ms 18 ms 17 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

The last hops don't have that 20+ ms jump like the previous tracert....so whatever was wrong with the network.....is now fixed.

I think.

**BigHub** · 09-01-05, 11:54 PM

Here is my new one... the time is 11:54 pm

C:\Documents and Settings\Jono Hubbard>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 12 ms 15 ms ip70-191-173-1.fv.dl.cox.net [70.191.173.1]
3 9 ms 10 ms 10 ms cdm-208-180-23-153.bcst.cox-internet.com [208.18
0.23.153]
4 15 ms 8 ms 8 ms cdm-208-180-23-133.bcst.cox-internet.com [208.18
0.23.133]
5 16 ms 13 ms 35 ms dllsbbrc02-gew0402.ma.dl.cox-internet.com [66.76
.45.149]
6 15 ms 16 ms 13 ms 68.1.206.45
7 16 ms 16 ms 16 ms so-3-3-0-0.gar2.Dallas1.Level3.net [4.78.234.5]

8 16 ms 16 ms 16 ms ge-1-2-52.car4.Dallas1.Level3.net [4.68.122.39]

9 18 ms 18 ms 14 ms savvis-level3-ge.Dallas1.Level3.net [4.68.111.86
]
10 17 ms 14 ms 22 ms dpr1-ae1.DallasEquinix.savvis.net [204.70.134.13
]
11 86 ms 19 ms 20 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
12 28 ms 17 ms 16 ms 216.39.64.10
13 22 ms 16 ms 16 ms 216.39.69.134
14 * * * Request timed out.
15 17 ms 19 ms 16 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

**...bigdog...** · 09-02-05, 12:38 AM

C:\Documents and Settings\The System>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms 192.168.0.1
2 8 ms 8 ms 8 ms adsl-70-241-95-254.dsl.hstntx.swbell.net [70.241
.95.254]
3 10 ms 9 ms 9 ms dist1-vlan60.hstntx.sbcglobal.net [151.164.11.19
0]
4 10 ms 9 ms 10 ms bb1-g1-2-0.hstntx.sbcglobal.net [151.164.11.230]

5 10 ms 9 ms 11 ms core1-p6-0.crhstx.sbcglobal.net [151.164.188.1]

6 14 ms 14 ms 14 ms core3-p3-0.crdltx.sbcglobal.net [151.164.240.189
]
7 15 ms 15 ms 15 ms core1-p9-0.crdltx.sbcglobal.net [151.164.242.118
]
8 15 ms 16 ms 16 ms bb1-p2-0.rcsntx.sbcglobal.net [151.164.40.38]
9 15 ms 16 ms 15 ms bb2-p4-0.rcsntx.sbcglobal.net [151.164.191.118]

10 17 ms 17 ms 16 ms ex1-p12-0.eqdltx.sbcglobal.net [151.164.44.45]
11 17 ms 17 ms 17 ms 151.164.249.222
12 18 ms 17 ms 18 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
13 18 ms 17 ms 18 ms 216.39.64.26
14 18 ms 18 ms 19 ms 216.39.69.206
15 * * * Request timed out.
16 38 ms 39 ms 37 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

now it's all messed up again. 37ms is not acceptable for me.