Author Topic: ATTENTION: NEED INFORMATION (Read 5792 times)

Skuzzy · « **on:** February 24, 2009, 08:00:47 PM »

We are working with AT&T to solve the recent and some long term issues there have been with routing problems to/from our game servers.

We have good information from Comcast and Sprint clients. What I need now is information from other ISP's.

In this thread, it would be appreciated if we could get some traceroutes or Ping Plots from ISP's other than Comcast or Sprint. It would also be helpful for you to add a comment about the quality of the connection to the servers. Discos, loss of UDP, or if nothing at all is wrong. Yes, we need good traceroutes or Ping Plots as well.

Please run the traceroute/tracert/Ping Plot to 206.16.60.38 Only one traceroute/tracert/Ping Plot is needed from each person.

AT&T will be reviewing this data tomorrow. Please keep this thread free of discussion other than the commentary with the traceroute/Ping Plot.

Thank you.

Skuzzy · « **Reply #1 on:** February 24, 2009, 08:06:15 PM »

I have a good connection from home. Here is my tracert

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms x.x.x.x
2 25 ms 24 ms 23 ms L100.DSL-04.DLLSTX.verizon-gni.net [71.97.0.1]
3 23 ms 23 ms 23 ms P1-3.LCR-01.DLLSTX.verizon-gni.net [130.81.34.56]
4 23 ms 23 ms 23 ms 130.81.29.176
5 25 ms 25 ms 25 ms 0.ge-2-3-0.XL3.DFW7.ALTER.NET [152.63.1.18]
6 25 ms 25 ms 25 ms 0.ge-6-0-0.BR2.DFW13.ALTER.NET [152.63.96.181]
7 26 ms 25 ms 25 ms 192.205.33.169
8 27 ms 28 ms 27 ms tbr2.dlstx.ip.att.net [12.123.16.30]
9 27 ms 26 ms 26 ms cr2.dlstx.ip.att.net [12.122.18.213]
10 27 ms 25 ms 25 ms gar5.dlstx.ip.att.net [12.122.138.5]
11 26 ms 27 ms 27 ms 12.122.255.226
12 27 ms 26 ms 27 ms mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.206]
13 27 ms 26 ms 27 ms 206.16.60.38

Trace back
===
traceroute 71.97.0.1
traceroute to 71.97.0.1 (71.97.0.1), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.613 ms 0.552 ms 0.476 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.282 ms 0.314 ms 0.252 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.830 ms 1.280 ms 1.128 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 1.959 ms 1.865 ms 1.506 ms
5 tbr2.dlstx.ip.att.net (12.122.18.222) 2.006 ms 2.047 ms 1.962 ms
6 ggr2.dlstx.ip.att.net (12.123.16.29) 1.377 ms 1.301 ms 1.301 ms
7 192.205.33.170 (192.205.33.170) 1.561 ms 1.612 ms 1.689 ms
8 0.ge-2-0-0.XL4.DFW7.ALTER.NET (152.63.96.186) 1.632 ms 1.693 ms 1.865 ms
9 0.ge-3-2-0.DFW01-BB-RTR2.verizon-gni.net (152.63.2.186) 1.916 ms 1.971 ms 1.849 ms
10 P11-0.LCR-02.DLLSTX.verizon-gni.net (130.81.29.179) 3.787 ms 3.921 ms 3.847 ms
11 L100.DSL-04.DLLSTX.verizon-gni.net (71.97.0.1) 4.087 ms 3.993 ms 3.944 ms

eagl · « **Reply #2 on:** February 24, 2009, 08:38:57 PM »

This is from Wichita Falls, time warner cable with their upgraded higher speed service plan (10 down / 1 up). Just a few months ago I was seeing sub-90ms rock steady pings to HTC. I haven't seen ping times this high in 12 years, back when I was on dialup. I had better pings from Cambridge, England and Osan AB, S. Korea.

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 12 ms 11 ms 10.237.96.1
3 8 ms 10 ms 11 ms gig1-0-0.wcfltx01-rtr1.sw.rr.com [24.160.24.46]
4 49 ms 41 ms 30 ms so0-0-0.dllatxl3-rtr1.texas.rr.com [72.179.205.112]
5 130 ms 174 ms 149 ms te-9-2.car1.Dallas1.Level3.net [8.9.232.77]
6 170 ms 158 ms 83 ms ae-1-69.edge2.Dallas3.Level3.net [4.68.19.12]
7 126 ms 103 ms 172 ms 192.205.35.225
8 155 ms 193 ms 176 ms cr1.dlstx.ip.att.net [12.122.139.22]
9 151 ms 90 ms 82 ms gar5.dlstx.ip.att.net [12.122.139.5]
10 212 ms 202 ms 230 ms 12.122.255.226
11 349 ms 337 ms 391 ms mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]
12 383 ms 407 ms 349 ms 206.16.60.38

Trace complete.

Trace back
==========

traceroute 24.160.24.46
traceroute to 24.160.24.46 (24.160.24.46), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.655 ms 0.537 ms 0.475 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.306 ms 0.284 ms 0.256 ms
3 12-122-254-29.attens.net (12.122.254.29) 1.551 ms 1.130 ms 1.096 ms
4 12.122.138.242 (12.122.138.242) 2.761 ms 2.327 ms 2.774 ms
5 ggr2.dlstx.ip.att.net (12.123.16.5) 1.262 ms 1.374 ms 1.282 ms
6 * * 192.205.36.14 (192.205.36.14) 1.586 ms
7 64.124.196.102.allocated.abov e.net (64.124.196.102) 1.639 ms 1.602 ms 1.614 ms
8 ae-1-0.cr0.hou30.tbone.rr.com (66.109.6.180) 10.968 ms 6.110 ms 6.008 ms
9 66.109.6.109 (66.109.6.109) 6.357 ms 6.506 ms 7.134 ms
10 pos2-0.wcfltx01-rtr2.sw.rr.com (72.179.205.115) 35.078 ms 35.153 ms 35.173 ms
11 gig1-0-9.wcfltx01-rtr1.sw.rr.com (24.160.24.73) 20.730 ms 20.529 ms *

spacer · « **Reply #3 on:** February 24, 2009, 08:55:45 PM »

Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/24/2009 8:44:05 PM

1 27 ms 25 ms 67 ms 12 ms 15 ms 17 ms [10.100.28.1]
2 29 ms 27 ms 56 ms 21 ms 37 ms 23 ms dynamic-76-73-147-117.knology.net [76.73.147.117]
3 60 ms 24 ms 49 ms 22 ms 27 ms 20 ms ge.0-1-0.cr-Panc.FL.US.knology.net [24.214.0.9]
4 54 ms 46 ms 50 ms 32 ms 29 ms 37 ms dynamic-75-76-40-33.knology.net [75.76.40.33]
5 42 ms 39 ms 77 ms 68 ms 32 ms 37 ms bpr2-ge-6-2-0-306.atlantapaix.savvis.net [208.173.60.229]
6 -32764 ms 59 ms 58 ms 45 ms -32764 ms 36 ms pr1-so-1-2-0.AtlantaPaix.savvis.net [204.70.200.41]
7 * 43 ms 60 ms 33 ms -32764 ms 30 ms cr1-po-0-0-2-2.atlanta.savvis.net [204.70.200.126]
8 50 ms 48 ms 58 ms 52 ms 30 ms 32 ms cw-gw.attga.ip.att.net [192.205.32.117]
9 93 ms 95 ms 76 ms 55 ms 58 ms 50 ms cr1.attga.ip.att.net [12.122.141.94]
10 73 ms 72 ms 80 ms 69 ms 62 ms 52 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 67 ms 64 ms 76 ms 46 ms 53 ms 48 ms gar5.dlstx.ip.att.net [12.122.138.5]
12 78 ms 113 ms 89 ms 63 ms 51 ms 52 ms [12.122.255.226]
13 60 ms 91 ms 126 ms 52 ms 68 ms 50 ms mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
14 65 ms 68 ms 103 ms 51 ms 54 ms 54 ms [206.16.60.38]

Hi Skuzzy
My worst PL was 25 that I saw that was in hop 7, for some reason this saved data doesn't show the 20 PL but has the *
My ISP is Knology. BTW I had just been in TTues and Lost UDP.

Trace back
==========
traceroute 76.73.147.117
traceroute to 76.73.147.117 (76.73.147.117), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.656 ms 0.940 ms 0.477 ms
2 mdf1-gsr12-1-gig-2-1.dal1.attens.net (63.241.192.41) 0.288 ms 0.368 ms 0.257 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.445 ms 1.172 ms 1.121 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 1.773 ms 1.400 ms 1.335 ms
5 ggr3.dlstx.ip.att.net (12.122.138.21) 1.204 ms 1.296 ms 1.189 ms
6 * * *
7 cr2-pos-0-0-0-0.Atlanta.savvis.net (204.70.192.69) 21.169 ms 20.943 ms 20.734 ms
8 pr1-so-0-3-0.atlantapaix.savvis.net (204.70.193.238) 53.178 ms 20.974 ms 20.910 ms
9 bpr1-so-1-2-0.AtlantaPaix.savvis.net (204.70.200.42) 20.876 ms 20.920 ms 20.915 ms
10 208.173.60.230 (208.173.60.230) 21.082 ms 20.943 ms 20.911 ms
11 dynamic-75-76-40-30.knology.net (75.76.40.30) 35.330 ms 35.360 ms 35.391 ms
12 dynamic-76-73-147-117.knology.net (76.73.147.117) 36.055 ms 36.016 ms 35.475 ms

APDrone · « **Reply #4 on:** February 24, 2009, 09:25:42 PM »

From Omaha Nebraska.
Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 8 ms 10 ms ip98-168-240-1.om.om.cox.net [98.168.240.1]
3 8 ms 9 ms 10 ms 68.13.8.213
4 14 ms 9 ms 9 ms mtc1dsrj01-xe210.0.rd.om.cox.net [68.13.14.5]
5 11 ms 8 ms 8 ms mtc1dsrj02-as0.0.rd.om.cox.net [68.1.0.129]
6 21 ms 18 ms 17 ms ae-31-51.ebr1.Denver1.Level3.net [4.68.107.30]
7 43 ms 36 ms 36 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
8 38 ms 35 ms 37 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.136.138]
9 33 ms 33 ms 33 ms ae-1-69.edge2.Dallas3.Level3.net [4.68.19.12]
10 31 ms 30 ms 28 ms 192.205.35.221
11 30 ms 31 ms 31 ms cr1.dlstx.ip.att.net [12.122.139.26]
12 29 ms 30 ms 31 ms gar5.dlstx.ip.att.net [12.122.139.5]
13 28 ms 31 ms 30 ms 12.122.255.226
14 30 ms 32 ms 30 ms mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
15 29 ms 30 ms 30 ms 206.16.60.38

No connection problems here.

Trace back
==========
traceroute 68.13.8.213
traceroute to 68.13.8.213 (68.13.8.213), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.626 ms 0.562 ms 0.480 ms
2 mdf1-gsr12-1-gig-2-1.dal1.attens.net (63.241.192.41) 0.379 ms 0.281 ms 0.252 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.871 ms 1.197 ms 1.116 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 2.227 ms 1.466 ms 1.491 ms
5 ggr4.dlstx.ip.att.net (12.122.138.61) 1.269 ms 1.272 ms 1.229 ms
6 192.205.34.82 (192.205.34.82) 1.572 ms 9.076 ms 26.012 ms
7 po1-20G.ar3.DAL2.gblx.net (67.16.132.201) 1.935 ms 1.792 ms 1.852 ms
8 COX-COM-INC.TenGigabitEthernet4-1.ar3.DAL2.gblx.net (64.215.187.2) 2.239 ms 1.578 ms 1.527 ms
9 dalsbbrj02-ae0.r2.dl.cox.net (68.1.0.143) 1.771 ms 1.766 ms 1.778 ms
10 * * *
11 * * *

It appears ICMP ECHO packets will not be answered by the router in the trace back

Mustaine · « **Reply #5 on:** February 24, 2009, 09:27:23 PM »

I don't know if this extra info helps, but the more data the better I always say:

The rest doesn't matter as I don't play on this rig. This is running hard wired through a Linksys WRT300N that I play wireless through on my laptop (doesn't have pingplotter). I don't play a ton, but Friday I was rock solid, Sunday I flew a bit too and was rock solid.

I am using RoadRunner from zip code 53022 in WI.

A simple tracert:

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.3.3.7
2 8 ms 7 ms 8 ms 76.36.192.1
3 10 ms 7 ms 6 ms gig2-2.hbtswigmtn-rtr1.wi.rr.com [24.160.228.209]
4 19 ms 11 ms 8 ms srp0-0.milwwirtco-rtr1.wi.rr.com [24.160.224.81]
5 10 ms 23 ms 12 ms network-024-160-229-193.wi.rr.com [24.160.229.193]
6 42 ms 12 ms 11 ms xe-11-2-0.edge1.Chicago2.Level3.net [4.71.248.13]
7 12 ms 12 ms 14 ms vlan52.ebr2.Chicago2.Level3.n et [4.69.138.190]
8 24 ms 17 ms 16 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
9 12 ms 10 ms 14 ms ae-24-54.car4.Chicago1.Level3.net [4.68.101.104]
10 16 ms 13 ms 14 ms 192.205.33.185
11 41 ms 60 ms 45 ms cr2.cgcil.ip.att.net [12.122.132.142]
12 40 ms 40 ms 40 ms cr2.sl9mo.ip.att.net [12.122.2.22]
13 40 ms 39 ms 39 ms cr1.sl9mo.ip.att.net [12.122.2.217]
14 39 ms 37 ms 40 ms cr2.dlstx.ip.att.net [12.122.3.221]
15 40 ms 37 ms 37 ms gar5.dlstx.ip.att.net [12.122.138.5]
16 41 ms 43 ms 39 ms 12.122.255.226
17 39 ms 46 ms 39 ms mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
18 41 ms 52 ms 42 ms 206.16.60.38

<S> hope it helps
(and yes I am surprised by the packet loss at hop 5... never had a problem)

Trace back
==========

traceroute 24.160.228.209
traceroute to 24.160.228.209 (24.160.228.209), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.629 ms 0.590 ms 0.476 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.274 ms 0.281 ms 0.254 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.797 ms 1.186 ms 1.182 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 2.232 ms 1.573 ms 1.426 ms
5 tbr2.dlstx.ip.att.net (12.122.18.238) 1.937 ms 2.055 ms 1.963 ms
6 ggr2.dlstx.ip.att.net (12.123.16.29) 1.362 ms 1.361 ms 1.247 ms
7 * 192.205.36.14 (192.205.36.14) 31.714 ms 1.580 ms
8 ge-2-1-0.mpr2.dfw2.us.above.net (64.125.27.81) 17.229 ms 1.960 ms 1.896 ms
9 so-2-3-0.mpr1.ord2.us.above.net (64.125.25.137) 28.720 ms 28.710 ms 30.313 ms
10 xe-1-1-0.er2.ord7.above.net (64.125.26.254) 28.297 ms 28.319 ms 28.265 ms
11 209.249.175.222.market-touch.com (209.249.175.222) 28.288 ms 28.360 ms 28.291 ms
12 ae-1-0.cr0.chi30.tbone.rr.com (66.109.6.154) 28.606 ms * 28.614 ms
13 ae-15.chcgill3-rtr1.kc.rr.com (66.109.6.113) 28.818 ms 28.756 ms 28.692 ms
14 pos7-1-0.milwwignfl-rtr3.wi.rr.com (24.160.229.66) 30.607 ms 30.432 ms 30.517 ms
15 network-024-160-229-133.wi.rr.com (24.160.229.133) 30.486 ms 30.722 ms 30.685 ms
16 srp1-1.hbtswigmtn-rtr1.wi.rr.com (24.160.224.87) 32.513 ms * 32.419 ms

ROC · « **Reply #6 on:** February 24, 2009, 09:29:48 PM »

I'm satisfied. Extremely stable, Sacramento. About the only time I have ever experienced a connection issue is when I needed to clean out my own system.

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 12 ms 9 ms 10.15.0.1
3 15 ms 12 ms 10 ms 172.16.17.1
4 11 ms 11 ms 11 ms 66.239.40.49.ptr.us.xo.net [66.239.40.49]
5 18 ms 11 ms 13 ms p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
6 17 ms 13 ms 15 ms p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
7 17 ms 19 ms 18 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181]
8 14 ms 18 ms 15 ms 207.88.12.182.ptr.us.xo.net [207.88.12.182]
9 16 ms 16 ms 16 ms 192.205.33.57
10 81 ms 80 ms 81 ms tbr2.sffca.ip.att.net [12.123.13.70]
11 79 ms 79 ms 76 ms cr2.sffca.ip.att.net [12.122.19.77]
12 87 ms 80 ms 82 ms cr2.la2ca.ip.att.net [12.122.31.133]
13 77 ms 77 ms 81 ms cr2.dlstx.ip.att.net [12.122.28.177]
14 77 ms 78 ms 78 ms gar5.dlstx.ip.att.net [12.122.138.5]
15 78 ms 79 ms 79 ms 12.122.255.226
16 79 ms 80 ms 90 ms mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.
218]
17 79 ms 80 ms 76 ms 206.16.60.38

Trace complete.

Trace back
==========
traceroute 66.239.40.49
traceroute to 66.239.40.49 (66.239.40.49), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.612 ms 0.575 ms 0.475 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.332 ms 0.286 ms 0.253 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.832 ms 1.232 ms 1.116 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 20.734 ms 20.390 ms 20.288 ms
5 cr1.attga.ip.att.net (12.122.28.173) 20.627 ms 20.216 ms 20.222 ms
6 ggr2.attga.ip.att.net (12.122.141.93) 20.210 ms 20.145 ms 20.162 ms
7 67.111.23.25.ptr.us.xo.net (67.111.23.25) 20.146 ms 20.670 ms 20.346 ms
8 te-4-1-0.rar3.atlanta-ga.us.xo.net (207.88.12.129) 21.130 ms 20.839 ms 20.659 ms
9 ge7-0-0d0.rar1.atlanta-ga.us.xo.net (65.106.1.29) 21.094 ms 21.094 ms 21.030 ms
10 p6-0-0.RAR2.Dallas-TX.us.xo.net (65.106.0.10) 22.108 ms 22.015 ms 21.953 ms
11 p0-0-0d0.RAR1.Dallas-TX.us.xo.net (65.106.1.37) 22.149 ms 22.106 ms 22.052 ms
12 p6-0-0.RAR2.LA-CA.us.xo.net (65.106.0.14) 54.439 ms 54.544 ms 54.479 ms
13 p0-0-0d0.rar1.la-ca.us.xo.net (65.106.1.49) 54.686 ms 54.625 ms 54.548 ms
14 p6-0-0.rar2.sanjose-ca.us.xo.net (65.106.0.18) 72.781 ms 64.809 ms 64.783 ms
15 p0-0-0d0.mar2.roseville-ca.us.xo.net (65.106.5.210) 67.953 ms 67.684 ms 67.911 ms
16 207.88.80.78.ptr.us.xo.net (207.88.80.78) 213.954 ms * 68.577 ms

BluTrain · « **Reply #7 on:** February 24, 2009, 09:38:03 PM »

From Queen Creek AZ - Cox.net Haven't been in game today but connection to webpage/forums is slow - several recent disconnects (last several weeks )from various arenas SEA and MA

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 6 ms 9 ms 9 ms 192.168.1.1
2 12 ms 7 ms 7 ms 10.96.0.1
3 69 ms 70 ms 70 ms 68.2.9.25
4 791 ms 679 ms 750 ms 70.169.73.41
5 669 ms 597 ms 747 ms chnddsrj01-ge710.0.rd.ph.cox.net [68.1.0.165]
6 672 ms 751 ms 749 ms ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]

7 697 ms 698 ms 746 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]

8 721 ms 749 ms 753 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.3
0]
9 705 ms 749 ms 752 ms ae-4-99.edge1.LosAngeles1.Level3.net [4.68.20.19
9]
10 802 ms 818 ms 818 ms level3-gw.la2ca.ip.att.net [192.205.33.229]
11 851 ms 818 ms 820 ms cr2.la2ca.ip.att.net [12.122.129.14]
12 764 ms 818 ms 818 ms cr2.dlstx.ip.att.net [12.122.28.177]
13 770 ms 818 ms 819 ms gar5.dlstx.ip.att.net [12.122.138.5]
14 674 ms 1006 ms 921 ms 12.122.255.226
15 862 ms * * mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.
218]
16 749 ms 818 ms 818 ms 206.16.60.38

Trace complete.

Trace back
==========
traceroute 68.2.9.25
traceroute to 68.2.9.25 (68.2.9.25), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.614 ms 0.525 ms 0.473 ms
2 mdf1-gsr12-1-gig-2-1.dal1.attens.net (63.241.192.41) 0.272 ms 0.297 ms 0.253 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.315 ms 1.201 ms 1.130 ms
4 cr1.dlstx.ip.att.net (12.122.139.6) 1.857 ms 1.956 ms 1.425 ms
5 ggr4.dlstx.ip.att.net (12.122.139.69) 1.245 ms 1.310 ms 1.180 ms
6 192.205.34.142 (192.205.34.142) 1.678 ms 1.679 ms 1.639 ms
7 67.17.195.30 (67.17.195.30) 35.984 ms 36.096 ms 43.890 ms
8 chnddsrj01-ge710.0.rd.ph.cox.net (68.1.0.165) 47.014 ms 51.623 ms 47.149 ms
9 mcdlcorc01-pos-0-6-0-0.ph.ph.cox.net (70.169.72.1) 48.188 ms 48.163 ms 47.954 ms
10 emescorc02-pos-0-7-0-0.ph.ph.cox.net (70.169.72.63) 48.946 ms 48.791 ms 49.054 ms
11 emessysc01-te-9-4.ph.ph.cox.net (70.169.72.87) 48.794 ms * 48.879 ms

SKColt · « **Reply #8 on:** February 24, 2009, 09:46:29 PM »

ISP: COX Communications

Target Name: N/A
IP: 206.16.60.38
Date/Time: 2/24/2009 9:43:34 PM to 2/24/2009 9:45:49 PM

1 0 ms 0 ms 0 ms 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 28 ms 28 ms 24 ms 17 ms 31 ms 26 ms 15 ms 46 ms 28 ms 16 ms ip72-209-128-1.ks.ks.cox.net [72.209.128.1]
3 27 ms 13 ms 33 ms 21 ms 16 ms 37 ms 17 ms * 38 ms 25 ms ip70-183-64-33.ks.ks.cox.net [70.183.64.33]
4 23 ms 19 ms * 25 ms 27 ms 52 ms 26 ms 29 ms * 19 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
5 * * * * * * * * * * [-]
6 * * * * * * * * * * [-]
7 29 ms 26 ms 23 ms 31 ms 56 ms 28 ms 30 ms 40 ms 33 ms 40 ms mtc3dsrj01-ge-100.0.rd.ok.cox.net [68.1.0.113]
8 37 ms 31 ms 33 ms 37 ms 34 ms 35 ms 45 ms 36 ms 45 ms 47 ms so-6-0-2.edge4.Dallas1.Level3.net [4.78.232.1]
9 N/A N/A 42 ms N/A N/A N/A N/A 46 ms 43 ms 53 ms ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]
10 N/A N/A 88 ms 95 ms * * 100 ms 90 ms 83 ms 93 ms [192.205.33.209]
11 56 ms 51 ms 62 ms * 56 ms 54 ms 55 ms 83 ms * 64 ms cr2.cgcil.ip.att.net [12.122.132.138]
12 76 ms * * * 55 ms 58 ms * * 54 ms * cr2.sl9mo.ip.att.net [12.122.2.22]
13 46 ms 32 ms 29 ms 36 ms 79 ms 36 ms 35 ms 32 ms * 33 ms [12.122.255.226]
14 56 ms 33 ms 35 ms 370 ms * 36 ms 35 ms 32 ms 33 ms 46 ms mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]
15 34 ms 34 ms 29 ms 37 ms 33 ms 59 ms 35 ms 33 ms 35 ms 33 ms [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 29ms, Maximum = 59ms, Average = 36ms

Trace back
==========
traceroute 72.209.128.1
traceroute to 72.209.128.1 (72.209.128.1), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.629 ms 0.544 ms 0.477 ms
2 mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201) 192.546 ms 0.913 ms 1.643 ms
3 12-122-254-29.attens.net (12.122.254.29) 60.816 ms 1.388 ms 1.679 ms
4 12.122.138.242 (12.122.138.242) 1.920 ms 2.265 ms 1.934 ms
5 cr2.dlstx.ip.att.net (12.122.18.237) 1.694 ms 1.477 ms 1.360 ms
6 ggr4.dlstx.ip.att.net (12.122.138.61) 1.264 ms 1.324 ms 1.235 ms
7 192.205.34.142 (192.205.34.142) 1.701 ms 1.721 ms 1.723 ms
8 po1-20G.ar3.DAL2.gblx.net (67.16.132.201) 1.945 ms 1.900 ms 1.753 ms
9 COX-COM-INC.TenGigabitEthernet4-1.ar3.DAL2.gblx.net (64.215.187.2) 1.591 ms 1.614 ms 1.602 ms
10 kscydsrj01-ge610.rd.ks.cox.net (68.1.1.177) 32.395 ms wichdsrj01-so000.0.rd.ks.cox.net (68.1.1.181) 13.211 ms kscydsrj01-ge610.rd.ks.cox.net (68.1.1.177) 32.442 ms
11 * 70.183.66.73 (70.183.66.73) 19.738 ms *
12 * * *
13 * * *
14 ^C

hlbly · « **Reply #9 on:** February 24, 2009, 10:04:15 PM »

ISP centurytel.net Occasional udp loss .Seems more frequent in the last month . Nothing to sweat about . Is DSL with swich a few hundred yards away .

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 11 ms 72-160-71-1.dyn.centurytel.net [72.160.71.1]
3 11 ms 12 ms 11 ms aurrorcoro2.aurrorcoro1.centu rytel.net [209.206.179.130]
4 18 ms 17 ms 19 ms ge-6-1.car3.Seattle1.Level3.net [4.79.104.41]
5 24 ms 23 ms 22 ms ge-1-0-0-51.gar1.Seattle1.Level3.net [4.68.105.9]
6 18 ms 20 ms 20 ms 192.205.33.145
7 74 ms 71 ms 73 ms 12.122.146.50
8 73 ms 74 ms 75 ms cr2.sffca.ip.att.net [12.122.31.194]
9 77 ms 75 ms 75 ms cr2.la2ca.ip.att.net [12.122.31.133]
10 75 ms 75 ms 72 ms cr2.dlstx.ip.att.net [12.122.28.177]
11 72 ms 73 ms 74 ms gar5.dlstx.ip.att.net [12.122.138.5]
12 77 ms 72 ms 71 ms 12.122.255.226
13 75 ms 77 ms 73 ms mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]
14 73 ms 72 ms 72 ms 206.16.60.38

Trace complete.

Trace back
==========
traceroute 72.160.71.1
traceroute to 72.160.71.1 (72.160.71.1), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.828 ms 0.526 ms 0.492 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 1.359 ms 0.344 ms 0.268 ms
3 12-122-254-29.attens.net (12.122.254.29) 1.562 ms 1.128 ms 1.093 ms
4 12.123.18.26 (12.123.18.26) 2.241 ms 2.087 ms 1.963 ms
5 cr1.dlstx.ip.att.net (12.122.18.145) 2.220 ms 1.516 ms 1.460 ms
6 ggr3.dlstx.ip.att.net (12.122.139.21) 1.304 ms 1.386 ms 1.220 ms
7 192.205.35.222 (192.205.35.222) 1.565 ms 1.561 ms 1.553 ms
8 vlan69.csw1.Dallas1.Level3.ne t (4.68.19.62) 8.356 ms vlan89.csw3.Dallas1.Level3.ne t (4.68.19.190) 2.113 ms vlan69.csw1.Dallas1.Level3.ne t (4.68.19.62) 2.129 ms
9 ae-72-72.ebr2.Dallas1.Level3.net (4.69.136.141) 2.834 ms ae-92-92.ebr2.Dallas1.Level3.net (4.69.136.149) 11.508 ms 4.753 ms
10 ae-2.ebr1.Denver1.Level3.net (4.69.132.105) 20.661 ms 22.529 ms 18.173 ms
11 ae-1-100.ebr2.Denver1.Level3.net (4.69.132.38) 20.969 ms 21.058 ms 17.980 ms
12 ae-2.ebr2.Seattle1.Level3.net (4.69.132.53) 67.092 ms 58.988 ms 55.748 ms
13 ae-23-52.car3.Seattle1.Level3.net (4.68.105.36) 55.854 ms 56.192 ms 55.800 ms
14 CENTURYTEL.car3.Level3.net (4.79.104.42) 60.572 ms 60.807 ms 60.188 ms
15 * * *
16 * * *
17 * *^C

The Fugitive · « **Reply #10 on:** February 24, 2009, 10:22:57 PM »

Almost never get booted, solid connection most times.

Trace back
==========
traceroute 96.34.80.22
traceroute to 96.34.80.22 (96.34.80.22), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.632 ms 0.595 ms 0.478 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.275 ms 0.281 ms 0.273 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.754 ms 1.141 ms 1.174 ms
4 * * *
5 * * *
6 * * *

NOTE: I cannot get out of AT&T's network for any 96.x.x.x IP address.

thndregg · « **Reply #11 on:** February 24, 2009, 10:30:38 PM »

From Nyssa, Oregon. Quest DSL.

Trace back
==========
traceroute 67.41.38.189
traceroute to 67.41.38.189 (67.41.38.189), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.637 ms 0.557 ms 0.474 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.297 ms 0.281 ms 0.255 ms
3 12-122-254-29.attens.net (12.122.254.29) 1.485 ms 1.120 ms 1.086 ms
4 tbr2.dlstx.ip.att.net (12.123.16.110) 2.169 ms 1.799 ms 1.969 ms
5 cr2.dlstx.ip.att.net (12.122.18.205) 2.066 ms 1.987 ms 1.435 ms
6 ggr7.dlstx.ip.att.net (12.122.87.57) 47.950 ms 1.415 ms 1.274 ms
7 * 192.205.35.54 (192.205.35.54) 1.537 ms 1.586 ms
8 boi-core-01.inet.qwest.net (205.171.5.241) 60.274 ms 60.215 ms 60.166 ms
9 bois-agw1.inet.qwest.net (67.41.38.189) 60.527 ms 60.591 ms 60.508 ms

Sled · « **Reply #12 on:** February 24, 2009, 10:37:14 PM »

From Anchorage, pretty standard, about what I normally get.

I have noticed a few more Lost UDP's than I normaly get. usualy during FSO.

Keep in mind this is not off my normal gaming computer, but they do share the conection through the router.

Trace back
==========
traceroute 209.163.55.137
traceroute to 209.163.55.137 (209.163.55.137), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.681 ms 0.525 ms 0.493 ms
2 mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205) 0.306 ms 0.293 ms 0.251 ms
3 12-122-254-29.attens.net (12.122.254.29) 1.475 ms 1.122 ms 1.118 ms
4 * * *
5 * * *
6 * * *
7 ^C

Banshee7 · « **Reply #13 on:** February 24, 2009, 10:57:57 PM »

First time using this so inform me if it's not right (I used Fugitive's post to guide me

)

AT&T DSL, usually keep about a ping of 60. Pretty stable connection but I have been getting a few more "Lost UDP" then discos.

Live near Dyersburg, Tennessee

Trace back
==========
traceroute 65.14.152.254
traceroute to 65.14.152.254 (65.14.152.254), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.612 ms 0.536 ms 0.473 ms
2 mdf1-gsr12-1-gig-2-1.dal1.attens.net (63.241.192.41) 0.269 ms 0.287 ms 0.252 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.416 ms 1.170 ms 1.199 ms
4 cr2.dlstx.ip.att.net (12.122.138.6) 20.116 ms 19.464 ms 19.462 ms
5 cr2.nsvtn.ip.att.net (12.122.28.65) 19.527 ms 19.485 ms 19.412 ms
6 gar5.nsvtn.ip.att.net (12.123.129.97) 19.267 ms 19.210 ms 19.174 ms
7 65.83.238.158 (65.83.238.158) 19.227 ms 19.315 ms 19.194 ms
8 65.83.238.103 (65.83.238.103) 19.418 ms 19.479 ms 19.389 ms
9 ixc00mem-pos-7-0-0.bellsouth.net (65.83.239.23) 25.156 ms 25.223 ms 25.167 ms
10 205.152.246.135 (205.152.246.135) 25.224 ms 25.260 ms 25.191 ms
11 * * *
12 * * *
13 * *^C

steely07 · « **Reply #14 on:** February 24, 2009, 11:02:41 PM »

Coming from TPG in Sydney Australia, never get disco'd, never see beacon, slower than i'd thought however

Trace back
==========
traceroute 220.245.178.199
traceroute to 220.245.178.199 (220.245.178.199), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.665 ms 0.522 ms 0.476 ms
2 mdf1-gsr12-1-gig-1-0.dal1.attens.net (63.241.192.249) 0.321 ms 0.307 ms 0.255 ms
3 12-122-254-29.attens.net (12.122.254.29) 1.282 ms 1.115 ms 1.094 ms
4 12.123.18.26 (12.123.18.26) 2.067 ms 2.004 ms 1.938 ms
5 ggr6.dlstx.ip.att.net (12.122.87.197) 1.341 ms 1.420 ms 1.313 ms
6 192.205.35.58 (192.205.35.58) 9.933 ms 1.761 ms 13.485 ms
7 if-3-0-0-1120.core1.DTX-Dallas.as6453.net (216.6.53.25) 1.734 ms 1.764 ms if-1-0-0-40.core1.DTX-Dallas.as6453.net (66.198.1.9) 1.912 ms
8 if-0-0-0-937.mcore5.LAA-LosAngeles.as6453.net (216.6.53.62) 34.412 ms 34.504 ms 34.494 ms
9 if-13-0-0-935.core3.SQN-SanJose.as6453.net (66.198.97.5) 44.768 ms 44.702 ms 44.561 ms
10 ix-4-1-0.core3.SQN-SanJose.as6453.net (216.6.33.58) 197.898 ms 197.559 ms 197.846 ms
11 syd-nxg-ibo-iri-1-port-channel-4.tpgi.com.au (202.7.162.38) 205.901 ms 205.669 ms 205.571 ms
12 syd-nxg-men-csw1-vlan-1.tpgi.com.au (220.245.178.199) 194.371 ms * 194.593 ms

Aces High Bulletin Board

Author Topic: ATTENTION: NEED INFORMATION (Read 5792 times)

Skuzzy

ATTENTION: NEED INFORMATION

Skuzzy

Re: ATTENTION: NEED INFORMATION

eagl

Re: ATTENTION: NEED INFORMATION

spacer

Re: ATTENTION: NEED INFORMATION

APDrone

Re: ATTENTION: NEED INFORMATION

Mustaine

Re: ATTENTION: NEED INFORMATION

ROC

Re: ATTENTION: NEED INFORMATION

BluTrain

Re: ATTENTION: NEED INFORMATION

SKColt

Re: ATTENTION: NEED INFORMATION

hlbly

Re: ATTENTION: NEED INFORMATION

The Fugitive

Re: ATTENTION: NEED INFORMATION

thndregg

Re: ATTENTION: NEED INFORMATION

Sled

Re: ATTENTION: NEED INFORMATION

Banshee7

Re: ATTENTION: NEED INFORMATION

steely07

Re: ATTENTION: NEED INFORMATION