Tracert's

**WileECyte** · 08-04-09, 07:02 AM

This morning... tracert is normal... I've noticed increase lag spikes on the new server so perhaps there's an issue?

Tracing route to unknown.dfw.colocrossing.com [207.210.254.226] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 9 ms 10 ms 7 ms 10.4.32.1
3 8 ms 9 ms 8 ms gig2-24.dllatxrch-rtr1.tx.rr.com [70.125.218.232]
4 9 ms 9 ms 9 ms gig5-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.111]
5 20 ms 13 ms 11 ms gig2-0-0.dllatxl3-rtr1.texas.rr.com [24.93.37.100]
6 11 ms 11 ms 11 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
7 15 ms 17 ms 15 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 14 ms 15 ms 23 ms 64.132.69.65
9 18 ms 15 ms 17 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.234.4]
10 15 ms 13 ms 13 ms 206.123.64.34
11 13 ms 12 ms 16 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
12 14 ms 11 ms 13 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

**DJ Ms. White** · 08-04-09, 01:50 PM

Have you checked for dropped packets along the way?

**alienhunt** · 08-09-09, 01:37 AM

why does my tracert to the CSS server time out on all my hops?? It seems no one else has this issue, yet no one else lives in China

**KidWithTheFace** · 08-20-09, 01:52 PM

I just moved into my college dorms and I'm not sure of the settings, need some help
Microsoft Windows XP [Version 5.1.2600]

C:\Documents and Settings\>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 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 175 ms 175 ms 175 ms 146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]

Trace complete.

C:\Documents and Settings\>d

**...bigdog...** · 08-20-09, 10:00 PM

yeah...I'm gonna say that your net problems are NOT due to TTP.

Might want to ask others in the dorm that game....see how they are set up.

**ElFuriosoGato** · 09-11-09, 09:51 PM

Having problems connecting to the BF2 server. I can connect to other non-TTP servers fine. I get in game, play for about 10 seconds and get booted to main screen with "Your connection to the server has been lost." Running ping to the server for about 3 minutes shows around 3 request timed outs. Wasn't a problem last week or this weekend but after Monday I could not play.

Tracing route to unknown.dfw.colocrossing.com [207.210.254.226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms *
2 <1 ms <1 ms <1 ms *

3 3 ms 4 ms 3 ms *
4 <1 ms <1 ms <1 ms *
5 1 ms 1 ms <1 ms 165.234.165.129
6 <1 ms 1 ms <1 ms 8e6-core-fargo-ext.itd.nd.gov [165.234.33.25]
7 <1 ms <1 ms <1 ms 165.234.33.18
8 37 ms 37 ms 37 ms 66.62.227.21
9 47 ms 47 ms 47 ms ge-3-10.r01.dllstx09.us.bb.gin.ntt.net [157.238.
224.137]
10 47 ms 47 ms 47 ms ae-3.r20.dllstx09.us.bb.gin.ntt.net [129.250.3.7
3]
11 47 ms 47 ms 47 ms eqix.dlfw.twtelecom.net [206.223.118.36]
12 47 ms 47 ms 47 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.
234.4]
13 47 ms 48 ms 47 ms 206.123.64.34
14 48 ms 49 ms 49 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]

15 48 ms 48 ms * unknown.dfw.colocrossing.com [207.210.254.226]
16 48 ms 48 ms 48 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

**...bigdog...** · 09-13-09, 04:07 PM

hmmm....perhaps it's just a temporary network issue affecting you? Thre are no reports from our datacenters, or any mass reports from our users.

check again later today/ tomorrow?

**Jonas Quin** · 12-20-09, 02:33 AM

bf2142

these were run about a min apart
themost noatable difference is @ #10

Traceroute has started…

traceroute to 207.210.254.226 (207.210.254.226), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 17.525 ms 25.343 ms 15.003 ms
2 10.85.192.1 (10.85.192.1) 13.971 ms 9.997 ms 8.917 ms
3 acr01gldlca-gbe-1-24.rvsd.ca.charter.com (96.34.96.136) 9.126 ms 26.002 ms 8.349 ms
4 96-34-96-38.static.unas.ca.charter.com (96.34.96.38) 9.020 ms 10.985 ms 12.291 ms
5 96-34-96-5.static.unas.ca.charter.com (96.34.96.5) 23.153 ms 21.878 ms 13.310 ms
6 96-34-100-8.static.unas.ca.charter.com (96.34.100.8) 15.991 ms 14.925 ms 15.394 ms
7 bbr01rvsdca-tge-0-0-0-6.rvsd.ca.charter.com (96.34.2.28) 14.123 ms 15.182 ms 15.617 ms
8 te-3-2.car1.lasvegas1.level3.net (4.71.176.25) 198.816 ms 203.180 ms 64.250 ms
9 ae-11-11.car2.lasvegas1.level3.net (4.69.133.114) 18.793 ms 17.608 ms 17.447 ms
10 ae-2-2.car1.saltlakecity1.level3.net (4.69.133.118) 108.122 ms 230.155 ms 483.839 ms
11 ae-11-11.car2.saltlakecity1.level3.net (4.69.133.122) 41.429 ms 41.205 ms 44.476 ms
12 ae-5-5.ebr1.denver1.level3.net (4.69.133.126) 43.846 ms 54.798 ms 52.129 ms
13 ae-2.ebr2.dallas1.level3.net (4.69.132.106) 64.532 ms 53.528 ms 54.772 ms
14 ae-11-60.car1.dallas1.level3.net (4.69.145.3) 59.364 ms 51.029 ms 53.613 ms
15 cwie-llc.car1.dallas1.level3.net (4.59.113.70) 56.834 ms 52.045 ms 52.954 ms
16 226.254.210.207.hypernia.com (207.210.254.226) 61.337 ms 51.037 ms 52.728 ms

Traceroute has started…

traceroute to 207.210.254.226 (207.210.254.226), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 10.898 ms 0.688 ms 0.652 ms
2 10.85.192.1 (10.85.192.1) 9.225 ms 250.607 ms 41.810 ms
3 acr01gldlca-gbe-1-24.rvsd.ca.charter.com (96.34.96.136) 8.391 ms 9.773 ms 7.124 ms
4 96-34-96-38.static.unas.ca.charter.com (96.34.96.38) 8.589 ms 9.825 ms 10.108 ms
5 96-34-96-5.static.unas.ca.charter.com (96.34.96.5) 11.781 ms 11.513 ms 13.251 ms
6 96-34-100-8.static.unas.ca.charter.com (96.34.100.8) 17.712 ms 14.765 ms 15.594 ms
7 bbr01rvsdca-tge-0-0-0-6.rvsd.ca.charter.com (96.34.2.28) 13.666 ms 12.991 ms 14.354 ms
8 te-3-2.car1.lasvegas1.level3.net (4.71.176.25) 20.396 ms 16.865 ms 18.167 ms
9 ae-11-11.car2.lasvegas1.level3.net (4.69.133.114) 25.999 ms 21.923 ms 18.735 ms
10 ae-2-2.car1.saltlakecity1.level3.net (4.69.133.118) 41.607 ms 42.421 ms 41.127 ms
11 ae-11-11.car2.saltlakecity1.level3.net (4.69.133.122) 161.110 ms 48.868 ms 86.050 ms
12 ae-5-5.ebr1.denver1.level3.net (4.69.133.126) 40.478 ms 51.157 ms 53.681 ms
13 ae-2.ebr2.dallas1.level3.net (4.69.132.106) 64.551 ms 54.119 ms 52.679 ms
14 ae-11-60.car1.dallas1.level3.net (4.69.145.3) 53.775 ms 51.073 ms 50.304 ms
15 cwie-llc.car1.dallas1.level3.net (4.59.113.70) 51.942 ms 51.932 ms 53.670 ms
16 226.254.210.207.hypernia.com (207.210.254.226) 51.384 ms 51.652 ms 60.910 ms

Traceroute has started…

traceroute to 207.210.254.226 (207.210.254.226), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 12.487 ms 1.110 ms 0.652 ms
2 10.85.192.1 (10.85.192.1) 17.110 ms 10.675 ms 8.724 ms
3 acr01gldlca-gbe-1-24.rvsd.ca.charter.com (96.34.96.136) 8.123 ms 9.147 ms 8.114 ms
4 96-34-96-38.static.unas.ca.charter.com (96.34.96.38) 8.419 ms 9.542 ms 9.934 ms
5 96-34-96-5.static.unas.ca.charter.com (96.34.96.5) 12.242 ms 13.799 ms 11.535 ms
6 96-34-100-8.static.unas.ca.charter.com (96.34.100.8) 13.710 ms 13.680 ms 15.467 ms
7 bbr01rvsdca-tge-0-0-0-6.rvsd.ca.charter.com (96.34.2.28) 13.973 ms 21.248 ms 12.155 ms
8 te-3-2.car1.lasvegas1.level3.net (4.71.176.25) 20.008 ms 18.782 ms 20.264 ms
9 ae-11-11.car2.lasvegas1.level3.net (4.69.133.114) 18.418 ms 18.215 ms 17.557 ms
10 ae-2-2.car1.saltlakecity1.level3.net (4.69.133.118) 43.047 ms 42.300 ms 41.415 ms
11 ae-11-11.car2.saltlakecity1.level3.net (4.69.133.122) 179.928 ms 207.523 ms 204.604 ms
12 ae-5-5.ebr1.denver1.level3.net (4.69.133.126) 41.959 ms 52.746 ms 53.555 ms
13 ae-2.ebr2.dallas1.level3.net (4.69.132.106) 60.196 ms 57.915 ms 70.061 ms
14 ae-31-80.car1.dallas1.level3.net (4.69.145.131) 63.144 ms 54.243 ms 53.816 ms
15 cwie-llc.car1.dallas1.level3.net (4.59.113.70) 53.581 ms 54.148 ms 53.243 ms
16 226.254.210.207.hypernia.com (207.210.254.226) 53.585 ms 55.105 ms 55.732 ms

hope thes can in some way be helpful, i know how to run these but reading them is a different story....

**...bigdog...** · 12-20-09, 03:30 PM

yeah....looks like something's up at the salt lake city level3 router. Not on our end, or even on the ends that our ISP can control. Likely, it's affecting a lot of people, and I bet it's only temporary.