Tracert's

**...bigdog...** · 09-26-10, 01:36 PM

it's not terrible...but it's not 25ms either.

**DancingCorpse** · 09-26-10, 01:41 PM

Could be worse. I've seen many a horror story where traces from Houston or other Southern states would exceed 30 hops on it's way to Chicago, resulting in over 100 pings.

**DancingCorpse** · 09-26-10, 01:43 PM

I'm happy.

Tracing route to 173.234.33.163.rdns.ubiquityservers.com [173.234.33.163]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms WL.satx.rr.com [192.168.2.1]
2 5 ms 6 ms 6 ms 10.77.9.1
3 17 ms 7 ms 5 ms 24.28.134.184
4 6 ms 7 ms 9 ms 24.28.131.32
5 7 ms 7 ms 7 ms gig10-0-5.snantx6000-rtr2.satx.rr.com [24.28.133
.122]
6 24 ms 11 ms 11 ms gig2-1-0.hstntxl3-rtr1.texas.rr.com [72.179.205.
10]
7 10 ms 11 ms 37 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
8 17 ms 16 ms 15 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
9 16 ms 15 ms 15 ms xe-2-0-3.ar1.dfw1.us.nlayer.net [69.31.63.1]
10 16 ms 16 ms 15 ms ae0-50g.cr1.dfw1.us.nlayer.net [69.31.63.125]
11 37 ms 35 ms 35 ms xe-2-2-0.cr2.ord1.us.nlayer.net [69.22.142.2]
12 36 ms 37 ms 37 ms ae2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]
13 43 ms 36 ms 38 ms er01.chi01.ubiquityservers.com [69.31.111.66]
14 37 ms 37 ms 37 ms 173.234.33.163.rdns.ubiquityservers.com [173.234
.33.163]

Trace complete.

**...bigdog...** · 09-27-10, 10:02 PM

Originally Posted by DancingCorpse

Could be worse. I've seen many a horror story where traces from Houston or other Southern states would exceed 30 hops on it's way to Chicago, resulting in over 100 pings.

go back to the early days of this thread, and you'll see traces from houston to dallas being routed through fucking colorado, or chicago, or atlanta.

It's like continental is my ISP or some shit.

**su-san** · 10-06-10, 10:16 PM

To new IPs from Houston, TX.

Code:

C:\Documents and Settings\su-san>tracert 173.234.33.163

Tracing route to 173.234.33.163.rdns.ubiquityservers.com [173.234.33.163]
over a maximum of 30 hops:

  1     3 ms     2 ms     5 ms  home [192.168.1.254]
  2   467 ms   601 ms   594 ms  76-250-64-2.lightspeed.hstntx.sbcglobal.net [76.
250.64.2]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    24 ms    20 ms    20 ms  151.164.43.136
  7    33 ms    33 ms    34 ms  ppp-151-164-52-82.rcsntx.swbell.net [151.164.52.
82]
  8    40 ms    36 ms    36 ms  xe1-0.cr01.dfw01.mzima.net [206.223.118.62]
  9    54 ms    52 ms    54 ms  te1-0.cr1.chi1.us.packetexchange.net [69.174.120
.13]
 10    61 ms    52 ms    52 ms  xe0-cdn.cust.ord01.mzima.net [72.37.148.138]
 11    53 ms    54 ms    54 ms  173.234.33.163.rdns.ubiquityservers.com [173.234
.33.163]

Trace complete.

C:\Documents and Settings\su-san>tracert 72.233.44.146

Tracing route to 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
over a maximum of 30 hops:

  1     3 ms     1 ms     2 ms  home [192.168.1.254]
  2   582 ms   615 ms   507 ms  76-250-64-2.lightspeed.hstntx.sbcglobal.net [76.
250.64.2]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    21 ms    20 ms    20 ms  151.164.38.222
  7    35 ms    34 ms    34 ms  ppp-151-164-52-18.rcsntx.swbell.net [151.164.52.
18]
  8    53 ms    35 ms    35 ms  asn3356-level3.eqdltx.sbcglobal.net [151.164.248
.210]
  9    35 ms    34 ms    35 ms  ae-32-80.car2.Dallas1.Level3.net [4.69.145.132]

 10    35 ms    35 ms    35 ms  DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]

 11    35 ms    38 ms    34 ms  10.0.0.14
 12    36 ms    35 ms    35 ms  10.200.222.10
 13    48 ms    35 ms    35 ms  146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]

Trace complete.

**Too Much Damage** · 10-07-10, 09:49 AM

New server IP from WVU

Code:

Tracing route to 173.234.33.164.WIREAFFILIATE.NET [173.234.33.164]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     5 ms     5 ms  96.179.158.1
  3     7 ms     7 ms     7 ms  ge-3-28-ur02.morgantown.wv.pitt.comcast.net [68.
85.72.89]
  4     8 ms     7 ms     7 ms  te-9-1-ur01.morgantown.wv.pitt.comcast.net [68.8
6.146.13]
  5     9 ms    11 ms     9 ms  te-3-3-ar02.pittsburgh.pa.pitt.comcast.net [68.8
6.146.18]
  6     9 ms    11 ms    10 ms  68.85.75.169
  7    23 ms    21 ms    26 ms  te-3-1-0-0-cr01.chicago.il.ibone.comcast.net [68
.86.90.181]
  8    22 ms    23 ms    23 ms  pos-0-2-0-0-pe01.350ecermak.il.ibone.comcast.net
 [68.86.86.78]
  9    26 ms    35 ms    22 ms  66-208-229-50-ubr02b-muncie01-in.hfc.comcastbusi
ness.net [66.208.229.50]
 10    22 ms    42 ms    23 ms  xe0-cdn.cust.ord01.mzima.net [72.37.148.138]
 11    27 ms    24 ms    24 ms  173.234.33.164.WIREAFFILIATE.NET [173.234.33.164
]

Trace complete.

**Mr_Blonde_OPS** · 10-07-10, 12:57 PM

From Chicago so I have a ping lower than 50.

Code:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\test>tracert 173.234.33.163
Tracing route to 173.234.33.163.rdns.ubiquityservers.com [173.234.33.163]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms home [192.168.1.254]
2 * * * Request timed out.
3 23 ms 21 ms 20 ms 71.145.96.14
4 22 ms 22 ms 21 ms 71.145.64.70
5 * * * Request timed out.
6 21 ms 23 ms 21 ms ppp-151-164-52-140.rcsntx.swbell.net [151.164.52
.140]
7 22 ms 21 ms 23 ms 151.164.99.109
8 31 ms 35 ms 35 ms xe1-1.cr01.ord01.mzima.net [206.223.119.62]
9 23 ms 23 ms 23 ms xe0-cdn.cust.ord01.mzima.net [72.37.148.138]
10 24 ms 25 ms 23 ms 173.234.33.163.rdns.ubiquityservers.com [173.234
.33.163]
Trace complete.
C:\Users\test>
C:\Users\test>tracert 72.233.44.146
Tracing route to 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms home [192.168.1.254]
2 21 ms 22 ms 21 ms 99-48-60-3.lightspeed.chcgil.sbcglobal.net [99.4
8.60.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 23 ms 21 ms 21 ms 151.164.43.206
7 22 ms 22 ms 21 ms 151.164.99.141
8 22 ms 22 ms 22 ms xe-11-1-0.edge4.Chicago3.Level3.net [4.68.62.37]
9 23 ms 21 ms 22 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
10 63 ms 61 ms 62 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
11 59 ms 70 ms 53 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
12 55 ms 53 ms 54 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
13 53 ms 52 ms 54 ms ae-22-70.car2.Dallas1.Level3.net [4.69.145.68]
14 54 ms 55 ms 53 ms DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]
15 53 ms 53 ms 64 ms 10.0.0.14
16 54 ms 67 ms 57 ms 10.100.222.10
17 54 ms 53 ms 54 ms 146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]
Trace complete.
C:\Users\test>

**...bigdog...** · 10-14-10, 10:00 AM

most of the above look good.

**MasterBlaster** · 11-18-10, 09:24 AM

So, I know I am not the only one that gets these problems. because when it starts to happen to me while playing, I ask whoever is on my team if they are getting any spikes too. My tab will show a constant 80 ms, but my net graph shows a spiking ping from 100 -150ms. Choke stays somewhat low but it does go higher when people are around (and no its not the computer, gtx470 main card, gtx 270SC physics, 4gigs ram, 3.02 ghz proc. frames stay at around 200 constant).

Ran some tracerts last night while i was having some troubles. This is the first one I ran. I ran a tracert to teamplayergaming first, then one to the normal CSS server. These are all with my firewalls off and Microsoft Sec. Ess. off.

Tracing route to TeamPlayer Gaming - The Front Page [98.129.229.150]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 55 ms 54 ms 54 ms 207.225.140.194
4 54 ms 54 ms 54 ms 65.103.30.9
5 79 ms 80 ms 78 ms 67.14.2.10
6 79 ms 79 ms 79 ms 205.171.62.42
7 79 ms 79 ms 79 ms 98.129.84.181
8 79 ms 79 ms 80 ms 98.129.84.155
9 79 ms 80 ms 79 ms 98.129.229.150

Trace complete.

C:\Windows\system32>tracert 173.243.33.162

Tracing route to 173.243.33.162 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 54 ms 53 ms 54 ms mpls-dsl-gw02-194.mpls.qwest.net [207.225.140.19
4]
4 60 ms 53 ms 54 ms mpls-agw1.inet.qwest.net [65.103.30.9]
5 64 ms 64 ms 64 ms cer-core-02.inet.qwest.net [67.14.8.14]
6 64 ms 64 ms 64 ms chp-brdr-01.inet.qwest.net [205.171.139.150]
7 66 ms 64 ms 65 ms 62.156.128.157
8 81 ms 80 ms 80 ms 217.239.40.210
9 79 ms 79 ms 79 ms 80.156.162.30
10 79 ms 79 ms 79 ms 204.14.19.122
11 79 ms 79 ms 79 ms 173.243.32.2
12 80 ms 80 ms 81 ms 173.243.32.6
13 80 ms 79 ms 80 ms 173.243.32.2
14 106 ms 88 ms 82 ms 173.243.32.6
15 80 ms 100 ms 80 ms 173.243.32.2
16 245 ms 88 ms 98 ms 173.243.32.6
17 80 ms 82 ms 80 ms 173.243.32.2
18 81 ms 86 ms 81 ms 173.243.32.6
19 82 ms 80 ms 80 ms 173.243.32.2
20 81 ms 82 ms 85 ms 173.243.32.6
21 80 ms 81 ms 85 ms 173.243.32.2
22 87 ms 82 ms 85 ms 173.243.32.6
23 81 ms 92 ms 81 ms 173.243.32.2
24 83 ms 82 ms 212 ms 173.243.32.6
25 81 ms 83 ms 81 ms 173.243.32.2
26 84 ms 82 ms 92 ms 173.243.32.6
27 82 ms 81 ms 84 ms 173.243.32.2
28 94 ms 105 ms 85 ms 173.243.32.6
29 81 ms 81 ms 82 ms 173.243.32.2
30 113 ms 94 ms 249 ms 173.243.32.6

Trace complete.

Not sure why it was going back and forth between those two.

I then ran some more, and i got what looks to be a good one.

C:\Windows\system32>tracert 173.234.33.162

Tracing route to 162.33.234.173.hypernia.com [173.234.33.162]
over a maximum of 30 hops:

1 1 ms 8 ms 4 ms 192.168.1.1
2 1 ms 2 ms 1 ms 192.168.0.1
3 53 ms 54 ms 53 ms mpls-dsl-gw02-194.mpls.qwest.net [207.225.140.19
4]
4 54 ms 54 ms 53 ms mpls-agw1.inet.qwest.net [65.103.30.9]
5 64 ms 63 ms 64 ms cer-core-02.inet.qwest.net [67.14.8.14]
6 64 ms 64 ms 64 ms chx-edge-02.inet.qwest.net [205.171.139.61]
7 67 ms 64 ms 64 ms 216.207.157.42
8 65 ms 64 ms 65 ms ae0-30g.ar1.ord1.us.nlayer.net [69.31.111.129]
9 68 ms 74 ms 75 ms er01.chi01.ubiquityservers.com [69.31.111.66]
10 66 ms 65 ms 65 ms 162.33.234.173.hypernia.com [173.234.33.162]

Trace complete.

C:\Windows\system32>tracert 173.234.33.162

Tracing route to 162.33.234.173.hypernia.com [173.234.33.162]
over a maximum of 30 hops:

1 <1 ms 10 ms 6 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 55 ms 54 ms 53 ms mpls-dsl-gw02-194.mpls.qwest.net [207.225.140.194]
4 54 ms 76 ms 54 ms mpls-agw1.inet.qwest.net [65.103.30.9]
5 65 ms 64 ms 64 ms cer-core-02.inet.qwest.net [67.14.8.14]
6 64 ms 81 ms 64 ms chx-edge-02.inet.qwest.net [205.171.139.61]
7 64 ms 65 ms 64 ms 216.207.157.42
8 65 ms 64 ms 64 ms ae0-30g.ar1.ord1.us.nlayer.net [69.31.111.129]
9 69 ms 74 ms 74 ms er01.chi01.ubiquityservers.com [69.31.111.66]
10 65 ms 65 ms 66 ms 162.33.234.173.hypernia.com [173.234.33.162]

Trace complete.

So after that one I logged into the servers to check to see if the lag was gone, it was not. Got out of game and tried a tracert again, and got this.

Tracing route to 173.234.33.62.rdns.ubiquityservers.com [173.234.33.62]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 54 ms 54 ms 54 ms mpls-dsl-gw02-194.mpls.qwest.net [207.225.140.194]
4 54 ms 54 ms 53 ms mpls-agw1.inet.qwest.net [65.103.30.9]
5 64 ms 63 ms 64 ms cer-core-02.inet.qwest.net [67.14.8.14]
6 65 ms 64 ms 64 ms chx-edge-02.inet.qwest.net [205.171.139.61]
7 64 ms 64 ms 64 ms 216.207.157.42
8 64 ms 64 ms 64 ms ae0-30g.ar1.ord1.us.nlayer.net [69.31.111.129]
9 73 ms 74 ms 74 ms er01.chi01.ubiquityservers.com [69.31.111.66]
10 er01.chi01.ubiquityservers.com [69.31.111.66] reports: Destination host un
reachable.

Trace complete.

So what do you guys think is causing this. I get it about 3 or 4 days out of the week. Qwest DSL 1.5mb (yeah i know it sucks, but when i don't have this lag problem it's just fine, and its the only thing we can get in our area).

**DJ Ms. White** · 11-18-10, 09:41 AM

Originally Posted by DJ Mr. White

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

C:\Users\Mr. White>tracert 173.243.33.162

Tracing route to 173.243.33.162 over a maximum of 30 hops

1 5 ms 11 ms 5 ms 10.238.160.1
2 8 ms 5 ms 5 ms 173-219-247-112-link.sta.suddenlink.net [173.219
.247.112]
3 17 ms 15 ms 19 ms cdm-66-76-30-177.tylrtx.suddenlink.net [66.76.30
.177]
4 32 ms 25 ms 23 ms 64.211.195.141
5 79 ms 82 ms 127 ms pos3-0-0-2488M.asr1.YYZ1.gblx.net [67.16.161.50]

6 80 ms 79 ms 81 ms BANDCON.GigabitEthernet7-7.ar1.YYZ1.gblx.net [64
.210.31.162]
7 79 ms 81 ms 79 ms 204.14.19.122
8 76 ms 78 ms 76 ms 173.243.32.2
9 77 ms 76 ms 79 ms 173.243.32.6
10 78 ms 75 ms 77 ms 173.243.32.2
11 78 ms 82 ms 78 ms 173.243.32.6
12 77 ms 77 ms 85 ms 173.243.32.2
13 77 ms 77 ms 79 ms 173.243.32.6
14 77 ms 75 ms 75 ms 173.243.32.2
15 81 ms 80 ms 77 ms 173.243.32.6
16 79 ms 76 ms 80 ms 173.243.32.2
17 79 ms 82 ms 80 ms 173.243.32.6
18 77 ms 79 ms 77 ms 173.243.32.2
19 79 ms 80 ms 81 ms 173.243.32.6
20 77 ms 80 ms 80 ms 173.243.32.2
21 79 ms 80 ms 82 ms 173.243.32.6
22 78 ms 80 ms 79 ms 173.243.32.2
23 80 ms 79 ms 80 ms 173.243.32.6
24 78 ms 77 ms 77 ms 173.243.32.2
25 83 ms 80 ms 79 ms ^C
C:\Users\Mr. White>
OK, so my tracert looked normal before, but now I'm getting bounced back and forth between two places as seen above.