Jump to content

Need some trace routes to help address lag


Fatty

Recommended Posts

I need a favor. When the server starts its warping issues, I need some people to volunteer an immediate traceroute and post it here. The more we have, the better. Thank you.

Link to comment
Share on other sites

here is 1, havent played yet today to check lag, just wanted to get this on here for starters and help

 

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 1 ms 1 ms 2 ms homeportal.gateway.2wire.net [172.16.0.1]

2 16 ms 15 ms 15 ms ppp-69-221-7-254.dsl.toldoh.ameritech.net [69.22

1.7.254]

3 17 ms 17 ms 17 ms dist2-vlan50.toldoh.ameritech.net [65.42.7.227]

 

4 15 ms 17 ms 17 ms bb1-g1-0.toldoh.ameritech.net [65.42.7.99]

5 19 ms 19 ms 19 ms bb1-p1-5.sfldmi.sbcglobal.net [151.164.242.10]

6 19 ms 19 ms 19 ms bb2-p15-0.sfldmi.ameritech.net [151.164.40.182]

 

7 27 ms 27 ms 27 ms core2-p6-1.crchil.sbcglobal.net [151.164.242.129

]

8 29 ms 27 ms 27 ms 151.164.42.168

9 28 ms 29 ms 27 ms bb2-p13-0.emhril.ameritech.net [151.164.191.174]

 

10 29 ms 29 ms 29 ms ex2-p5-0.eqchil.sbcglobal.net [151.164.42.139]

11 29 ms 29 ms 29 ms ex1-p6-0.eqchil.sbcglobal.net [151.164.40.125]

12 28 ms 29 ms 33 ms ibx.ge-0-2-0.cr2.chi1.speakeasy.net [206.223.119

.4]

13 30 ms 31 ms 29 ms 69.12.89.6

 

Trace complete.

Link to comment
Share on other sites

Member
(edited)

doing a trace route now

 

every 20-30 seconds my 5th hop down spikes to 150-200

 

sl-bb21-chi-4-3.sprintlink.net 144.232.26.37

 

 

is this it?!?!?! maybe?!?!?!

Edited by bear^
Link to comment
Share on other sites

I get similar on all servers, cept my hop number is diff.

 

1 8 ms 9 ms 21 ms 10.18.168.1

2 9 ms 8 ms 9 ms 12-215-17-193.client.mchsi.com [12.215.17.193]

3 18 ms 19 ms 18 ms 12-215-2-138.client.mchsi.com [12.215.2.138]

4 30 ms 29 ms 28 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]

5 37 ms 29 ms 30 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

6 28 ms 46 ms 29 ms 4.68.127.165

7 * 27 ms * so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

8 29 ms 27 ms 28 ms ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

9 27 ms 28 ms 47 ms unknown.Level3.net [166.90.208.206]

10 61 ms 52 ms 28 ms 69.12.89.96

 

1 9 ms 27 ms 7 ms 10.18.168.1

2 8 ms 9 ms 8 ms 12-215-17-193.client.mchsi.com [12.215.17.193]

3 19 ms 18 ms 28 ms 12-215-2-138.client.mchsi.com [12.215.2.138]

4 33 ms 28 ms 28 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]

5 31 ms 28 ms 53 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

6 30 ms 29 ms 27 ms 4.68.127.165

7 50 ms * 82 ms so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

8 30 ms 26 ms 26 ms ge-11-2.ipcolo2.Chicago1.Level3.net [4.68.101.16

9]

9 27 ms 28 ms 30 ms unknown.Level3.net [166.90.208.206]

10 30 ms 32 ms 29 ms 69.12.89.96

 

 

This is for Scopeless, but the same hop and same level times out for all three of our servers. This is consistent no matter what time of day it is.

Edited by Brillow_Head
Link to comment
Share on other sites

yeah, mock me and my seriousness

 

how dare u try and make the server better bear!

 

you've only played since beta 4 non-stop, what would you know about CS?!

 

<_<

Link to comment
Share on other sites

GC Founder

Bear,

 

Provide me with requested information, plz.

You talk about a server problem by finding a hop in your route that drops packets....which has nothing to do with the server. That makes no sense.

Controlled and fair experiments....and also find me that 24 player server with less/no choke. Apples to apples, please.

 

This topic is done as the original problem was solved.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...